Permission modes
In the desktop app, the permission control in the composer sets how far Work and Code may go on their own when editing files, running commands or reaching the internet. Three presets are offered, and the default is Approve for me.
- Ask for approval: reads and edits files in the workspace, and always asks before editing external files or using the internet.
- Approve for me (default): the same boundary, but an automatic reviewer answers the approval prompts it is allowed to, and you are asked only about actions it detects as potentially unsafe.
- Full access: no restrictions on the internet or on files anywhere on your computer, and no approval cards for tools and file changes.
If you were on Ask for approval before the 1.1.57 update, ZeroTwo moved you to Approve for me. Switch back in the permission picker whenever you like.
If your settings match none of the presets, the control reads Custom. Keys 1, 2 and 3 pick a preset while the menu is open. Choose a mode below to compare how each one is set up.
Enable modes
Open Settings > General > Permissions. The default mode is always available. The Auto-review switch controls whether Approve for me appears in the composer, and the Full access switch does the same for Full access. Switching them off only hides the option; it does not select anything.
How permissions work
Two things combine. The sandbox limits which files and network a run can reach, and approvals decide when it stops to ask. Changing the reviewer does not widen the sandbox, so Approve for me has the same boundary as Ask for approval but reviews requests that cross it automatically. Auto-review can make mistakes.
Full access is not a switch for everything. Connectors always ask for approval, following the approval setting you chose for each one, and a request marked for strict review still stops. Deny rules and a Business workspace's approval policy also still apply.
The operating-system sandbox exists only on macOS. On Windows and Linux there is no OS sandbox, so approvals are the safeguard there. The exception is Windows with the Windows Subsystem for Linux agent environment, where commands run sandboxed inside your WSL distribution (see the Windows app).
The picker is a desktop feature. On the web, iOS and Android there is no permission control, because runs execute in a cloud sandbox: commands, file changes, Library changes and Site publishes just run, and only connector cards ask. Local scheduled tasks also run with Full access.
Never ask for approval
An approval card for a tool can offer Never ask for approval. It stops approval cards for tools and file changes in the desktop app, and connectors still ask. To turn approvals back on, switch it off on the Permissions page in Customize.
When a run is blocked
A stop now says why. If a model provider's safety system halts a run, the reply says so and includes the provider's reason when one is sent. A goal that is blocked shows the reason in its banner, and a schedule that is missing a connector permission names the connector and links to where you allow it.
See sandboxing and automatic review for background.