Primary navigation

Sandbox

How sandboxing behaves on each ZeroTwo client

ZeroTwo keeps agent work contained in two different ways. Tasks that run on your computer in the desktop app use an operating-system sandbox, available on macOS only. Tasks that run in the cloud use a managed cloud sandbox. In the desktop app, approvals decide when a local run has to stop and ask before going past a limit.

What the sandbox does

On macOS, commands the agent launches locally, including git, package managers and test runners, run under the system's Seatbelt sandbox. The agent can read files, but it can write only inside the project folders you gave it, and the project's .git and other metadata folders are protected from writes. Outbound network access is blocked for sandboxed commands.

Why it matters

Work inside the limits runs without prompts, so you are not asked to approve every command. The limits are enforced by the operating system rather than by the agent's own judgment.

Platform support

  • macOS: the Seatbelt sandbox is built in.
  • Windows and Linux: the desktop app has no operating-system sandbox. Every local command that would need one stops for your approval, or runs freely if the task uses Full access. Treat approvals as the only safeguard on these systems.
  • Cloud tasks: work runs inside a cloud sandbox instead of on your computer. On the web there is no permission picker. Cloud runs do not ask about commands or file changes, and the cloud sandbox is the boundary; connectors still ask.

How permissions work

The permission control in the composer, available in the desktop app, offers three presets.

  • Ask for approval: the agent edits the workspace and asks before going outside it, including for network access.
  • Approve for me: the default. The same boundary, but a reviewing model decides requests instead of you; see automatic review. Settings calls this Auto-review.
  • Full access: no sandbox limits and no approval cards for tools and file changes. Connectors still ask.

Plan mode makes a task read-only for its turn, whatever the preset. Local scheduled tasks always run with Full access because nothing is there to answer approval prompts.

Configure defaults

Open Settings > General > Permissions to choose which presets appear in the composer: the Auto-review switch controls Approve for me, and the Full access switch controls Full access. Choosing the always option on an approval card saves a permission rule for that kind of action. Each connector tool can also be set to Always allow, Needs approval or Blocked under Customize.

For cloud tasks, internet access is set per environment under Settings > Coding > Code Cloud. The modes are off, Package managers (the default), Custom domains only and All (unrestricted). See Permissions for the full preset descriptions.