agy --sandbox

Forces sandbox isolation for terminal commands, including in print mode.

agy --sandbox confines every local execution command the agent launches to OS-level containment: nsjail (Linux, kernel namespaces/cgroups), sandbox-exec (macOS, policy profiles), or AppContainer (Windows). Since 1.0.6 the flag is also correctly enforced in non-interactive print mode (-p/--print), not just interactively. The same setting can be persisted via enableTerminalSandbox in settings.json (default: false).

✅ WHEN TO USE IT?

Run untrusted or generated code in isolation

Launch agy --sandbox in a new or unfamiliar repo

Force sandbox isolation in scripts/CI as well

agy --sandbox -p "<prompt>"

⛔ WHEN NOT TO?

The agent needs full access to system resources outside the workspace

The sandbox deliberately restricts filesystem visibility and network access for terminal commands.

Better: Start agy without --sandbox, or confirm 'run without sandbox restrictions' per command

SOURCES

Antigravity CLI CHANGELOG (GitHub) ↗ raw.githubusercontent.com
Antigravity CLI Doku: Sandbox ↗ antigravity.google