Google Antigravity

Notes

In /boost mode the orchestrator inspects workspace context automatically before planning. General automatic context gathering outside /boost is not described.

Examples

• /boost Add pagination to the orders API

Sources

• https://antigravity.google/docs/boost

Notes

Agents can autonomously plan and execute tasks across the editor, terminal, and browser, modifying the codebase and reporting progress through artifacts.

Examples

• An agent implementing a feature and producing a walkthrough artifact

Sources

• https://developers.googleblog.com/en/build-with-google-antigravity-our-new-agentic-development-platform/

Notes

Antigravity supports MCP servers, configured in Settings (Antigravity 2.0), the MCP Store (IDE), or mcp_config.json at global (~/.gemini/config/) or workspace (.agents/) level for the CLI.

Examples

• Connecting a database MCP server to the agent

Sources

• https://antigravity.google/docs/mcp/

Notes

Besides its own desktop IDE and CLI, Antigravity offers extensions for VS Code, Visual Studio, JetBrains, Zed, and Xcode with agent side panels, inline diffs, and interactive implementation plans.

Examples

• Using the Antigravity extension in a JetBrains IDE

Sources

• https://antigravity.google/docs/ide/extensions/

Notes

The free Individual plan includes Claude Sonnet 4.6 and Claude Opus 4.6 as agent models, alongside Gemini models.

Examples

• Switching the agent to Claude Opus 4.6

Sources

• https://antigravity.google/pricing

Notes

The window depends on the selected model; Antigravity compacts context automatically, sizing summaries from the model's full context window.

Examples

• Long session continuing after automatic compaction

Sources

• https://antigravity.google/docs/changelog

Notes

Not documented: the full official documentation (https://antigravity.google/llms.txt) was searched on 2026-09-30 without finding this capability. This does not mean the tool lacks it. An optional Chrome DevTools skills package covers debugging and performance, but console error capture is not described.

Sources

• https://antigravity.google/docs/build-with-google

Notes

Not documented: the full official documentation (https://antigravity.google/llms.txt) was searched on 2026-09-30 without finding this capability. This does not mean the tool lacks it. The /browser subagent can inspect DOM elements itself, but selecting elements for the agent is not described.

Sources

• https://antigravity.google/docs/slash-commands

Notes

The browser agent can open, read, and actuate a local Chrome browser to test development websites, capture screenshots, and record actions. This runs in Chrome rather than as a preview panel inside the editor.

Examples

• The agent opening the local dev server in Chrome to verify a change

Sources

• https://antigravity.google/docs/ide/browser/

Notes

Workspace rules can be placed in AGENTS.md or GEMINI.md files (at the root or any subdirectory) or in .agents/rules/*.md files.

Examples

• Adding an AGENTS.md at the repository root

Sources

• https://antigravity.google/docs/rules/

Notes

Rules support activation modes: always_on, glob (file patterns), model_decision (loaded when the task matches the description), and manual.

Examples

• A rule that only activates for *.tsx files

Sources

• https://antigravity.google/docs/rules/

Notes

Rules are cumulative across global (~/.gemini/AGENTS.md, ~/.gemini/GEMINI.md, ~/.gemini/config/rules/) and workspace scopes, with more specific directory-level rules taking precedence.

Examples

• A global rule for personal preferences plus a directory-level AGENTS.md

Sources

• https://antigravity.google/docs/rules/

Notes

The agent uses an Implementation Plan artifact to architect changes before executing them; you can trigger planning with /plan and comment on the plan.

Examples

• Reviewing and commenting on an implementation plan before the agent starts

Sources

• https://antigravity.google/docs/implementation-plan/