Markdownkeyboard_arrow_down

content_copyCopy Markdown

open_in_newView Markdown

Antigravity CLI Features

Plugins

How Plugins Work
Plugins are namespaced bundles that can contain skills, agents, rules, MCP servers, and hooks as a single deployable unit.

When you install a plugin, the CLI stages the files in your home directory under ~/.gemini/antigravity-cli/plugins/\<plugin_name\>/. The Antigravity Agent automatically discovers and loads these staged customizations.

~/.gemini/antigravity-cli/
├── plugins/
│   └── <plugin_name>/
│       ├── plugin.json         # Required marker file
│       ├── mcp_config.json     # Optional MCP server definitions
│       ├── hooks.json          # Optional event hooks definition
│       ├── skills/             # Optional skills
│       ├── agents/             # Optional subagents
│       └── rules/              # Optional rules
└── import_manifest.json        # Tracking manifest

Accessing Plugin Components
Once staged and loaded, you can interact with the plugin components inside the CLI using slash commands.

Terminal Sandbox

The Terminal Sandbox is a lightweight security isolation mechanism that protects your host system from potentially destructive file manipulations or unauthorized outbound network requests when the agent executes local shell commands.

Rather than running heavy virtual machines or containers, the CLI leverages native operating system features (nsjail on Linux, sandbox-exec on macOS, and AppContainer on Windows) to enforce strict containment boundaries with zero startup overhead.

Configuration
You can configure the sandbox behavior in your settings.json file (located at ~/.gemini/antigravity-cli/settings.json):

{
    "enableTerminalSandbox": true
}

• enableTerminalSandbox (boolean, default: false): Enables general execution containment barriers on all local agent processes.

Interactive Approvals
When the agent proposes a terminal command that requires your confirmation, the CLI prompt adapts dynamically based on your settings:

• When the Sandbox is Enabled: The confirmation prompt will include a specific option to Yes, and run without sandbox restrictions if you need to temporarily bypass the containment boundary for a single trusted command.
• When the Sandbox is Disabled: The prompt will include an option to Yes, and run in sandbox if you want to force a specific, potentially risky command to execute within the safety boundary.

CLI Slash Commands Reference

The Antigravity CLI supports a variety of slash commands typed directly into the prompt box to manage conversations, configure settings, and inspect agent capabilities.

Core Slash Commands

Advanced Customization via settings.json

For power users, several slash commands support deep customization via your ~/.gemini/antigravity-cli/settings.json configuration:

• Fine-Grained Permissions: Instead of global levels, define specific allowed/denied commands:

  "permissions": {
    "allow": ["command(git)", "command(npm test)"],
    "deny": ["command(rm -rf)"]
  }

• Custom Status Line & Window Titles: You can pipe live agent metadata (JSON format containing CWD, active model, token usage, state, etc.) directly into your own custom shell scripts to generate dynamic status bars or terminal window titles.

Subagents in Antigravity CLI

Antigravity CLI features an asynchronous subagents framework that allows the main agent to delegate parallel work, perform background research, and run system tests without blocking your active conversation.

What are Subagents?
Subagents are independent, concurrent agent sessions designed to tackle specific background tasks in parallel with the main conversation.

• Purpose: The main agent automatically spawns subagents to perform background operations such as looking up documentation, running builds, or validating a fix.
• Capabilities: Subagents have full access to tools such as code search, file editing, terminal commands, and web searches to complete their assigned tasks.
  • The main agent decides what tools and permissions subagents get, including whether they can use MCP tools and if they can write files.

Managing Agents: The /agents Panel

Antigravity CLI provides an interactive terminal UI to view, manage, and approve actions for running subagents.

• Access: Type /agents in the prompt to open the subagents panel.
• Overview: The panel shows a list of active and completed subagents, including surface-level details such as their status (running, done, killed, etc.) and the current step they are executing.

Tool Confirmations & Approvals
When a subagent wants to execute a tool that requires user permissions (such as running a local command or writing a file), it will surface the request. You can manage approvals in two ways:

1. Detail View Approvals
   The Subagent Detail View features an interaction section containing all pending approvals, where you can selectively approve or deny requests.

2. Fast Path Alerts
   To keep you in your flow, Antigravity CLI displays a Fast Path Alert directly above your prompt box when a subagent requests permission.

Last updated Oct 08, 2026