Support keyword: antigravity cli permissions

Antigravity CLI permissions

Permissions are the real control behind most yolo-mode questions. Review them before the CLI edits files or runs commands on your behalf.

Updated on 2026-05-27. Independent guide. Use official Google links for downloads and account actions.

Why permissions deserve their own page

Many users search for yolo mode, but the better operational keyword is permissions. Permissions determine when the agent asks before reading files, writing files, running commands, or taking broader actions. A good Antigravity CLI setup starts conservative and loosens only after the user understands the project risk.

For a new site, this page supports both safety and search intent: it catches users who do not want a philosophy post, but need a concrete checklist before enabling higher autonomy.

Permission review table

AreaRiskSafer default
File readsPrivate project files may be exposed to the active agent context.Start in a small folder and avoid secrets.
File writesIncorrect edits can touch many files.Use a disposable branch and review diffs.
Shell commandsCommands can install packages, delete files, or call network services.Require confirmation for command categories you do not trust yet.
Network accessRequests can reveal project metadata or hit paid services.Keep credentials out of the workspace and review outbound actions.
MCP toolsConnected tools can touch issue trackers, databases, or cloud resources.Enable one server at a time and test read-only actions first.

Practical workflow

  1. Open /permissions before the first real task.
  2. Ask the CLI to explain the current folder before changing anything.
  3. Use Git status and Git diff after every file-write task.
  4. Keep review prompts on for package installs, deployment commands, and cloud changes.
  5. Only use broader autonomy in a branch you can discard.

Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.

FAQ

Are permissions the same as yolo mode?

Yolo-style searches are usually about reducing confirmations. Permissions are the actual control surface to review.

Should I allow shell commands automatically?

Not at first. Require confirmation until you trust the project and understand the command category.

How does this relate to MCP?

MCP tools can create extra action surfaces, so enable and test them one at a time.

Related Antigravity CLI pages