ZeroTwo combines two things to keep an agent in bounds: a sandbox mode that sets what a command is technically allowed to touch, and an approval policy that decides when the agent must stop and ask you. You pick both at once with a permission preset in the composer. For the cross-surface overview see sandboxing.
Permission presets
The preset picker sits in the composer of the desktop app, for Work and Code tasks. Inside the open menu, the keys 1, 2 and 3 choose a preset.
| Preset | Approval policy | Sandbox | Effect |
|---|---|---|---|
| Ask for approval | On request | Workspace write | Reads, edits and commands inside the workspace run freely; edits outside it, network access and other escalations ask you first. |
| Approve for me (default) | On request, reviewed automatically | Workspace write | Same limits, but eligible requests go to a reviewer agent instead of to you. |
| Full access | Never ask | No sandbox | Tools and file changes run without approval cards. Connectors still ask. Use it only in a place you trust. |
Settings > General lists the presets as Default permissions, Auto-review (the same mode as Approve for me) and Full access, and has switches to hide Auto-review and Full access from the composer. Under a read-only sandbox, every write, command or network call asks. Plan mode forces read-only for its turn, so a plan cannot change anything until you approve it.
The permission picker exists only in the desktop app. In the browser, on iOS and Android, and in cloud runs, commands, file changes, Library changes and Site publishes just run, because the cloud sandbox itself is the boundary. Connectors are the exception and ask on every device. Scheduled tasks that run on your computer also use Full access, since nobody is there to approve.
Approval prompts
An approval card shows what the agent wants to do, with a preview of the command, file path or URL. The numbered choices are Yes, Yes, and don't ask again this task, a choice that saves a permanent rule, and No with room to tell the agent what to do instead. Pressing Skip declines. Approvals survive a reload and can be answered from the iOS or Android app. Calls to connector tools can need approval too, and each connector tool can be set to Always allow, Needs approval or Blocked in Customize. Connectors ask even under Full access and follow the approval setting you chose for each one, and a Business workspace's approval policy applies to its connectors. Read-only tools on many connectors no longer ask under the default modes, while writes still do. Saved rules are described in Rules.
A command that removes the filesystem root or your home folder always asks first, and is refused when approvals are off.
Automatic approval review
With Approve for me, a reviewer model screens each eligible request. It can wave through clearly low-risk actions, rejects critical-risk ones, and treats any failure of the review itself as a denial. The composer warns that Auto-review can make mistakes, so keep Ask for approval for sensitive work. The setting is available in the desktop app. Details are in Auto-review.
On the desktop, a tool card can also offer Never ask for approval, which turns approval cards off for tools and file changes. The switch for turning them back on is on the Permissions page in Customize. See Permissions.
A sub-agent that is waiting on you shows a badge in the agent roster, and a patch approval shows the full change for each file. An approval cannot be used once its tool call has ended.
OS-level sandbox
On macOS, local commands run inside a Seatbelt sandbox. Commands in it can read the disk, but writes are limited to the project workspace and ZeroTwo's own storage, and there is no general network access. Inside the workspace, .git, .agents, .zerotwo and .aws stay read-only.
On Windows and Linux the desktop app has no OS sandbox, except for Windows with the Windows Subsystem for Linux agent environment, which runs commands sandboxed in your WSL distribution. Approvals are the only safeguard there: shell commands, the JavaScript REPL and command hooks each need a per-call approval, or Full access. Explicit filesystem denials cannot be enforced on those systems.
Network access
Locally, a network call under a sandboxed preset asks for approval, and a sandboxed macOS command has no outbound network of its own. In the cloud, the environment's internet setting controls what a task can reach: off, package managers only (the default), custom domains only, or all. Set it under Settings > Coding > Code Cloud; see cloud internet access.
Version control
Work on a clean branch and commit often, so any change is easy to revert. Review the agent's output as you would a pull request.