Auto-approve
The Auto button in the composer answers approvals immediately, but it does not disable the approval machinery underneath.
What it does
The Auto button in the composer bar answers every permission prompt immediately as it arrives. The approval machinery underneath is untouched: the engine still asks, the request is still recorded and published through the normal event stream, and the resulting change still lands in the normal diff. The only thing removed is the waiting.
Migrate the auth module to the new session store.
Properties
| Property | Behavior |
|---|---|
| Persistence | Answers once, never always: nothing persists after you turn it off |
| Default | Off, and never remembered between windows: a new window always starts with Auto off |
| The floor | Absolute refusals from the command safety classifier still apply; Auto cannot override them |
| Plan / Explore | Does not broaden either: a command that Plan mode's budget would deny stays denied with Auto on |
| Pre-approval diff | Skipped, since there's no waiting period during which to show it |
| Post-write diff | Still shown, in the normal repository-state view, after the change lands |
Auto-approve is the one control that removes the thing standing between the agent and your files. It's presented loudly when on for exactly that reason: glance at the composer bar before stepping away from the keyboard mid-run.
Auto being on does not turn a Plan-mode turn into a Build-mode turn. A Plan turn that deleted a directory because Auto happened to be on would not be a bug in Auto: Plan's own tool restrictions already prevent that regardless of how approvals are answered.