Antigravity CLI auto mode (agy --mode=auto) approves file edits inside your workspace, runs terminal commands in the OS sandbox, and checks any command that has to leave the sandbox, so only risky or irreversible ones stop and ask (Choose an execution mode). Since CLI v1.5.7 (November 12, 2026) it is also the starting mode wherever it is available, headless -p runs included (Changelog).

Applies to: Antigravity CLI v1.5.8 (changelog dated November 13, 2026). Last checked: November 16, 2026.

On this page

What auto mode approves, and what still asks

The CLI has four execution modes. Here is how the three that touch approvals treat the same actions, from Google’s execution modes page and permissions page:

Action default accept-edits auto
Create or edit a file in the workspace Shows a diff and waits for you Approved Approved, including queued subagent writes
Terminal command Checked against toolPermission (request-review asks) Checked against toolPermission Runs inside the terminal sandbox without asking
Command that must run outside the sandbox Asks, unless a command(...) rule covers it Checked against toolPermission Evaluated automatically: safe, reversible commands run, risky or irreversible ones ask
Files outside the workspace, web page reads, unconfigured MCP tools Ask Ask Ask

The fourth mode, plan, adds the /plan prefix to your prompts: the agent reads the code with read-only tools and shows an outline for approval before it writes anything (Choose an execution mode).

Google gives build, test, lint and format commands in the workspace as examples of safe, reversible commands that auto mode runs without asking (Choose an execution mode). Inside the sandbox, commands can write to the workspace, temp directories and common build caches, files such as ~/.ssh and .env are blocked, and network access is limited to domains you approved (Terminal sandbox).

Auto became the default in v1.5.7

The v1.5.7 entry in the changelog (November 12, 2026) changed the default Agent Mode from Default to Auto. Sessions with no saved mode, “including headless -p runs”, now start in Auto wherever Auto is available, and in Default elsewhere. The same release made a Tool Permission setting of strict take precedence over Auto and accept-edits, so file edits still ask under strict.

On November 16, 2026, the execution modes page and the CLI reference still describe default as the mode agy starts in. The changelog entry is the newer statement. If you upgraded from 1.5.6 or earlier and never picked a mode, your sessions changed behaviour on update.

Warning

If a script or CI job runs agy -p on a machine where auto mode is available, v1.5.7 and later approve workspace edits and sandboxed commands in that run without asking (Changelog). Pin the mode you want before you rely on the old prompts.

Who gets auto mode

Condition What the docs say
CLI version v1.3.5+ on macOS and Linux, v1.4.4+ on Windows (Choose an execution mode)
Terminal sandbox Required. On Windows it needs Windows 11 24H2 or later with the August 2026 update; on Windows 10, earlier Windows 11 builds, and Linux hosts or containers that block unprivileged user namespaces, auto is not offered from v1.4.4 (Choose an execution mode)
Account Not available for business or enterprise accounts, including Antigravity in Gemini Enterprise (Choose an execution mode)
Pay-as-you-go Google Cloud Since v1.5.6 (November 11, 2026), accounts that sign in with Application Default Credentials (AGY_ADC_AUTH) get the same permission settings as other pay-as-you-go accounts, which makes Auto available to them; Gemini Enterprise accounts still are not offered it (Changelog)

When auto is not available, it is missing from Shift+Tab cycling and /config, and --mode=auto or "agentMode": "auto" runs the CLI in default mode. In headless mode, --mode=auto prints a warning and continues in default (Choose an execution mode).

Turn auto mode on, off, or pin a mode

For one session, pass the flag (Choose an execution mode):

# Launch directly in auto mode
agy --mode=auto

During a session, press Shift+Tab to cycle default > accept-edits > auto > plan > default. The status bar shows auto, and the prompt reads Auto mode: edits & safe commands auto-approved (shift+tab to cycle) (Choose an execution mode).

To change the mode every session starts in, open /config, select Agent Mode and pick a mode; the CLI writes it to ~/.gemini/antigravity-cli/settings.json. Or set agentMode in that file yourself, as in Google’s example (Choose an execution mode):

{
    "agentMode": "accept-edits"
}

To go back to the pre-1.5.7 behaviour, choose Default for Agent Mode in /config, which saves "agentMode": "" to settings.json (Changelog). The --mode flag only takes accept-edits, auto or plan (CLI reference), so the saved setting is the way to keep headless runs in default.

Auto mode is not --dangerously-skip-permissions

The CLI reference lists no --yolo flag. The flag that approves everything is --dangerously-skip-permissions, which sets toolPermission to always-proceed (CLI reference, Headless mode):

Auto mode --dangerously-skip-permissions
Workspace edits Approved Approved
Commands Sandbox by default; commands outside it are evaluated, risky ones ask Run without prompting unless an ask or deny rule matches
Web requests and MCP tools Ask unless allowed Run without prompting unless an ask or deny rule matches
Precedence Overridden by strict and always-proceed Takes precedence over auto mode

Warning

Google’s headless docs say --dangerously-skip-permissions “approves all tool calls, including file writes and command execution” and advise: “Prefer scoped permissions.allow rules unless you fully trust the prompt and environment” (Headless mode).

The documented alternatives: allow rules for the exact commands and paths a job needs, accept-edits when you want to approve every shell command yourself, toolPermission: "proceed-in-sandbox" with the sandbox on (sandboxed commands run, everything outside asks), and auto mode (CLI reference, Permissions). This is Google’s scoped-rule example for headless runs (Headless mode):

{
  "permissions": {
    "allow": [
      "command(git)",
      "command(regex:npm run (build|lint|test))",
      "write_file(src/)"
    ]
  }
}

Claude Code has a flag with the same name; see claude --dangerously-skip-permissions if you use both tools.

Your rules still win

Explicit allow, ask and deny rules from /permissions, plus strict and always-proceed, take precedence in every execution mode, and conflicting rules resolve as Deny > Ask > Allow (Choose an execution mode, Permissions). So a deny on command(rm -rf) or command(sudo) holds in auto mode too. Google’s example list of deny rules for ~/.gemini/antigravity-cli/settings.json includes command(rm -rf), command(regex:curl .*), command(sudo), write_file(.git/) and write_file(/home/user/.ssh) (Permissions).

Two recent releases changed auto mode and the rules around it (Changelog):

  • v1.5.6 (November 11, 2026): auto mode asks less often on safe reads outside the sandbox, such as GitHub API reads, fetches into an existing clone and single-file downloads; reading ~/.ssh/config, known_hosts or public keys is no longer treated as reading secrets, while private keys still are and sending any .ssh file elsewhere is still blocked.
  • v1.5.8 (November 13, 2026): fixed a sandbox network-proxy issue where percent-encoded slashes, backslashes or .. in a URL path could get around path-based network rules; made always-allow rules on Windows cmd and PowerShell require an exact match; and made mcp(server/tool) deny and ask rules apply to MCP tools marked eager in mcp_config.json.

If you came from Gemini CLI, Migrate Gemini CLI to Antigravity CLI covers what moves where, and the Gemini CLI policy engine guide covers the rule format you used there. For the wider product, including the App’s Default, Auto and Turbo presets, see the Google Antigravity review.