Skip to content

Latest commit

 

History

History
31 lines (22 loc) · 1.72 KB

File metadata and controls

31 lines (22 loc) · 1.72 KB

Permission modes

Permission modes control when an agent needs your approval to act. Choose a mode in the message composer; it applies to that thread.

New threads start in Full access unless you choose another mode before sending. A thread created from another thread inherits its mode.

Mode Behavior
Supervised Requests approval for commands and file changes.
Auto-accept edits Approves file edits automatically; other actions can still require approval.
Auto Uses the provider's automatic review to approve routine actions and ask about others.
Full access Allows commands and edits without approval prompts.

Approve or reject requests in the conversation to let the agent continue. Permission modes do not prevent the agent from asking questions about the task.

Provider differences

Providers enforce permissions differently. Some read-only actions can proceed in Supervised. Auto uses automatic review on Codex, Claude, and Cursor; providers without an equivalent, including OpenCode and Antigravity, fall back to asking.

For Grok, Always allow this session remembers the matching command or tool input. Other actions still require approval.

Antigravity can still send native approval requests in Full access. It only offers remembered approvals for actions that support them.

See the provider guides for setup and provider-specific limits.