Approval modes and protected operations
Approvals decide which tool calls wait for your permission. Change the mode beside the composer, or store one in a role as the default for new sessions. A few protected operations always need separate confirmation, whatever the mode.
Where to change it
Section titled “Where to change it”The approval pill next to the model pill at the bottom-left of the composer shows the current mode. Open it for a three-item radio list, or press Shift+Tab to cycle. A role also stores a default that new sessions start with.
You can change it while a turn runs; it applies from the next tool call that needs approval. Requests already waiting keep their state.
The three modes
Section titled “The three modes”| Mode | Behavior |
|---|---|
| Supervised | Commands, edits, writes, and MCP calls all wait for Allow. |
| Auto-accept edits | File edits and writes pass automatically; commands and MCP still ask. This is the Worker default. |
| Full | Ordinary tools pass automatically. This is the Orchestrator default, but its tool policy still cannot edit code. |
The mode only decides whether an approval prompt appears; it does not broaden capability. The tool policy still decides whether a role may write files, run commands, or only read.
Respond to an approval
Section titled “Respond to an approval”When a request is waiting, the session status becomes Waiting for approval and the approval bar appears above the composer. It shows the kind (command / file edit / file write / MCP tool), title, and expandable details; one request is shown at a time with a count for the rest.
Deny stops this call; Allow for session permits subsequent requests of the same kind in this session; Allow permits just this one. Buttons disable while submitting. If other workspaces are waiting too, a banner near the top says “N operations are waiting for your confirmation”. Review and resolve handles them grouped by session without changing the session you are viewing.