The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 21, 03:37 UTC
| 1 | # Permission modes |
| 2 | |
| 3 | Permission modes control when an agent needs your approval to act. Choose a mode in the message |
| 4 | composer; it applies to that thread. A new thread names its mode under the composer. In a thread |
| 5 | on your default mode, open the model picker and choose **Permissions** at its bottom, or press |
| 6 | `mod+shift+a`. A thread on another mode shows the mode next to the model. |
| 7 | |
| 8 | Set the default for new threads in **Settings → Threads → New threads → Permissions**. |
| 9 | Projects can override the environment default. New threads use this setting rather than the |
| 10 | mode of the thread you were viewing. The initial default is **Full access**; existing threads |
| 11 | and modes you choose in a draft keep their permissions. |
| 12 | |
| 13 | | Mode | Behavior | |
| 14 | | --------------------- | ------------------------------------------------------------------------------------- | |
| 15 | | **Supervised** | Requests approval for commands and file changes. | |
| 16 | | **Auto-accept edits** | Approves file edits automatically; other actions can still require approval. | |
| 17 | | **Auto** | Uses the provider's automatic review to approve routine actions and ask about others. | |
| 18 | | **Full access** | Allows commands and edits without approval prompts. | |
| 19 | |
| 20 | An administrator can cap the modes available on a machine with a |
| 21 | [managed policy](./managed-policy.md#permission-modes); modes above the cap show who manages them. |
| 22 | |
| 23 | Approve or reject requests in the conversation to let the agent continue. Permission modes do |
| 24 | not prevent the agent from asking questions about the task. Subagent approval requests appear in |
| 25 | the parent conversation with the subagent's name, so you can respond without switching threads. |
| 26 | |
| 27 | ## Provider differences |
| 28 | |
| 29 | Providers enforce permissions differently. Some read-only actions can proceed in **Supervised**. |
| 30 | **Auto** uses automatic review on Codex, Claude, Cursor, Grok, Antigravity, and fx; providers without |
| 31 | an equivalent, including OpenCode, fall back to asking. On Grok and Antigravity, actions their review |
| 32 | does not approve come to you for approval. On fx, prompts it still sends also come to you. |
| 33 | |
| 34 | Antigravity offers **Auto** only when your Antigravity sign-in provides its Auto mode; some accounts, |
| 35 | including some personal Google accounts, do not. Without it, an Antigravity thread already set to |
| 36 | **Auto** runs in **Supervised**. |
| 37 | |
| 38 | Muse Code offers only **Supervised** and **Full access**. A Muse thread already set to another mode |
| 39 | runs in **Supervised**. |
| 40 | |
| 41 | T3 Code offers no **Auto-accept edits** for fx, and **Full access** only with fx 0.0.14 or later. An fx |
| 42 | thread set to a mode its fx lacks runs in **Supervised**. |
| 43 | |
| 44 | Grok offers no **Auto-accept edits**. A Grok thread already set to it runs in **Supervised**. Grok |
| 45 | file-change approvals offer **Allow all edits this session**. Its command approvals have no |
| 46 | session-wide choice, because Grok would remember that command for the whole project. |
| 47 | |
| 48 | ACP Registry agents run their own tools in their own mode; T3 Code answers their approval requests |
| 49 | by the permission mode. See [ACP Registry permissions](./providers-acp.md#permissions-and-terminals). |
| 50 | |
| 51 | Claude can still ask in **Full access** when its settings disable bypass permissions or require |
| 52 | approval for an action. Dangerous-removal safety checks in bypass mode reject the command with |
| 53 | the original warning. Claude can use a safe rewrite when the warning supplies one; otherwise it |
| 54 | continues without the removal and tells you what it skipped. |
| 55 | While a Claude approval is pending, type a text reply to decline that request and give feedback |
| 56 | directly to the agent that asked, including a subagent. Other pending requests stay unanswered. |
| 57 | |
| 58 | Antigravity can still send native approval requests in **Full access**. It only offers remembered |
| 59 | approvals for actions that support them. |
| 60 | |
| 61 | Kiro offers only **Supervised** and **Full access**. In **Supervised** Kiro also asks you to |
| 62 | review a turn's file changes. See [Kiro permissions](./providers-kiro.md#permission-modes). |
| 63 | |
| 64 | See the [provider guides](./install.md#providers) for setup and provider-specific limits. |