Command reference ยท Antigravity CLI
/permissions
Opens the interactive tool permissions manager.
/permissions (Configurations category) opens the interactive permissions manager. First, a scope picker chooses between Project (active project only), Shared (shared across products), and Global (all sessions). Then the rule viewer shows three tabs: allowlist, denylist, and asklist, switchable with โ/โ or Tab. a adds a rule, e (or Ctrl+G) edits the selected rule, d (or Backspace) deletes it.
Rules follow the pattern action(target), e.g. command(git) for a prefix match on commands, or mcp(server/tool) or mcp(server/*) for individual or all tools of an MCP server. In case of conflicts, deny > ask > allow strictly applies. Actions not explicitly configured default to ask, except for read/write access within the active workspace, which is automatically allowed; a granted write_file permission implicitly also includes read_file for the same path. Since version 1.0.13, command matching defaults to an exact prefix match instead of regex; anyone needing actual regex patterns must prefix the rule with regex:.
โ WHEN TO USE IT?
Allow certain commands to run automatically
Open /permissions, choose scope Project, and add command(git) in the allowlist tab
Block a single MCP tool specifically
Open /permissions and add mcp(server/tool) in the denylist tab
โ WHEN NOT TO?
Wanting to bypass permissions entirely for just a single startup
/permissions manages permanent rules in settings.json, not a one-time skip for just one startup.
Better: Use agy --dangerously-skip-permissions at startup (with caution)
Expecting an actual regex pattern in a rule
Since version 1.0.13, command(...) is evaluated by default as an exact prefix match, not as regex.
Better: Prefix the rule with regex:, e.g. regex:command(npm run (build|test))
SOURCES
- Antigravity CLI docs: command reference โ antigravity.google
- Antigravity CLI docs: /permissions โ antigravity.google
- Antigravity docs: MCP โ antigravity.google
MORE COMMANDS ยท Antigravity CLI