抄作业 / 做成了什么 / Grok Bot
Forum: tighter OAuth scopes + fixed approval for mutable connector calls
标题与摘要为原文,未翻译。
- 做了什么
- Feature request: let users pick connector OAuth scopes (read vs write) and require a fixed in-code approval for mutable calls instead of Auto-review-only gating.
- 场景
- 写代码上线
- 资料完整度
- 作者与原链接有
- 做了什么有
- 来源原文摘录有
- 截图 / 媒体来源未提供
- 步骤 / 章节来源未提供
- 提示词 / 配置原文来源未提供
- 结果 / 数字来源未提供
- 风险提示有
- 相关条目有
— 表示来源没有给出,本站不补写。
- 来源原文摘录
I want to use more of the connector apps on grok bot but a lot of them request write access in the OAuth grant with no way to configure the scope. From what I understand after that grant, a write is not stopped by any fixed in-code rule but rather “Auto Review” checks the action before it runs. In the docs it says its an independent review model so whether a write stops for approval depends on that models decision. I would like two controls for the connectors: • Let me cap the OAuth scope, read-only should be the default with write, send, delete, etc.. being off unless I opt in. • I want the
展开全文
capability to enable a “fixed check” , where for each mutating call ( POST / PUT / PATCH / DELETE ) I am guaranteed to get an approval card. This check should happen in code and the review model should not have any choice in this decision. …RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗ 摘自论坛首帖,照录原文,未翻译。
- 提示词
来源没有给出可直接复制的提示词原文。
- 怎么复制
- 读原文:forum.cursor.com ↗
- 把原文里的步骤/提示词整理成一条消息交给 Bot
- 先手动跑一次,再决定频率
- 风险与限制
- 有删除、退订或取消动作:先出清单,逐项确认再执行
- 作者的结果不保证能复现,以原帖为准
- 用量预估
- 用金属计算器估一下