| 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. |
| 5 | |
| 6 | Set the default for new threads in **Settings → General → New threads → Permissions**. |
| 7 | Projects can override the environment default. New threads use this setting rather than the |
| 8 | mode of the thread you were viewing. The initial default is **Full access**; existing threads |
| 9 | and modes you choose in a draft keep their permissions. |
| 10 | |
| 11 | | Mode | Behavior | |
| 12 | | --------------------- | ------------------------------------------------------------------------------------- | |
| 13 | | **Supervised** | Requests approval for commands and file changes. | |
| 14 | | **Auto-accept edits** | Approves file edits automatically; other actions can still require approval. | |
| 15 | | **Auto** | Uses the provider's automatic review to approve routine actions and ask about others. | |
| 16 | | **Full access** | Allows commands and edits without approval prompts. | |
| 17 | |
| 18 | Approve or reject requests in the conversation to let the agent continue. Permission modes do |
| 19 | not prevent the agent from asking questions about the task. |
| 20 | |
| 21 | ## Provider differences |
| 22 | |
| 23 | Providers enforce permissions differently. Some read-only actions can proceed in **Supervised**. |
| 24 | **Auto** uses automatic review on Codex, Claude, Cursor, and Grok; providers without an equivalent, |
| 25 | including OpenCode and Antigravity, fall back to asking. On Grok, commands its review blocks come |
| 26 | to you for approval. |
| 27 | |
| 28 | Muse Code offers only **Supervised** and **Full access**. A Muse thread already set to another mode |
| 29 | runs in **Supervised**. |
| 30 | |
| 31 | Grok offers no **Auto-accept edits**. A Grok thread already set to it runs in **Supervised**. Grok |
| 32 | file-change approvals offer **Allow all edits this session**. Its command approvals have no |
| 33 | session-wide choice, because Grok would remember that command for the whole project. |
| 34 | |
| 35 | ACP Registry agents run their own tools in their own mode; T3 Code answers their approval requests |
| 36 | by the permission mode. See [ACP Registry permissions](./providers-acp.md#permissions-and-terminals). |
| 37 | |
| 38 | Antigravity can still send native approval requests in **Full access**. It only offers remembered |
| 39 | approvals for actions that support them. |
| 40 | |
| 41 | See the [provider guides](./install.md#providers) for setup and provider-specific limits. |