ask-antigravity

Antigravity plugin for Claude Code

Run Antigravity from inside Claude Code for code reviews and delegated tasks.

This plugin lets Claude Code users reach Antigravity without leaving their workflow. It adapts codex-plugin-cc to the Antigravity CLI (agy) runtime model.

[!IMPORTANT] This wraps the Antigravity CLI, not the Antigravity IDE. "Antigravity" names several Google products. This plugin drives agy, the standalone command-line binary — it does not connect to or control the Antigravity app or the Antigravity IDE, which have no programmatic interface. Having the GUI installed is neither sufficient (you still need agy on your PATH) nor required (the CLI works on its own).

What You Get

• /ask-antigravity:review — read-only Antigravity review
• /ask-antigravity:adversarial-review — steerable challenge review
• /ask-antigravity:rescue — delegate tasks to Antigravity through the ask-antigravity:antigravity-rescue subagent
• /ask-antigravity:setup — verify the local Antigravity CLI is installed and authenticated

Prerequisites

You need a working Antigravity CLI on your machine before installing this plugin. The plugin is a thin adapter — it wraps agy, it doesn't replace it.

1. Install Antigravity CLI

   curl -fsSL https://antigravity.google/cli/install.sh | bash
   # or
   brew install --cask antigravity-cli
   

   (Antigravity is not distributed via npm.) Version 1.0.7 or later is required — check with agy --version, and re-run the installer to upgrade an older install.

2. Authenticate

   Run agy interactively once and sign in with your Google account, or set ANTIGRAVITY_API_KEY in your environment.

   agy
   # complete sign-in, then exit
   

3. Verify agy works

   agy -p "what is 2+2"
   

4. Node.js 18.18 or later on PATH — the plugin's companion script runs through node.

/ask-antigravity:setup (below) prints the install command for you if agy is missing, but it never runs a remote installer on your behalf — installing and signing in are always your responsibility.

Install

Add the marketplace, install the plugin, reload:

/plugin marketplace add contrapuntal/antigravity-cli-plugin-cc
/plugin install ask-antigravity@contrapuntal
/reload-plugins

Then verify the plugin sees a working Antigravity:

/ask-antigravity:setup

After install, you should see:

• the slash commands listed below
• the ask-antigravity:antigravity-rescue subagent in /agents

Usage

/ask-antigravity:review

Runs an Antigravity review on your current work. Output is markdown organized by severity (Critical / High / Medium / Nits).

[!NOTE] Multi-file reviews can take a while. Use background mode for anything larger than ~2 files.

Use it to review:

• your current uncommitted changes
• your branch against a base branch like main

Pass --base <ref> for branch review. Also supports --wait and --background. Read-only and not steerable. To challenge a specific decision or risk area, use /ask-antigravity:adversarial-review.

/ask-antigravity:review
/ask-antigravity:review --base main
/ask-antigravity:review --background

This command never edits files.

/ask-antigravity:adversarial-review

A steerable review that challenges the chosen implementation and design. Uses the same review-target selection as /ask-antigravity:review.

Supports --base <ref>, --wait, --background, and free-form focus text after the flags.

/ask-antigravity:adversarial-review
/ask-antigravity:adversarial-review --base main challenge whether this caching design is right
/ask-antigravity:adversarial-review --background look for race conditions in the retry logic

This command never edits files.

/ask-antigravity:rescue

Hands a task to Antigravity through the ask-antigravity:antigravity-rescue subagent. Read-only by default — Antigravity analyzes and proposes; Claude or you apply the change. Pass --write to let Antigravity edit files directly.

Use it to have Antigravity:

• analyze a large diff or codebase region (Antigravity's large context window shines here)
• give a second opinion on an approach Claude proposed
• investigate a bug or run an analysis pass

/ask-antigravity:rescue investigate why the build is failing in CI
/ask-antigravity:rescue analyze the entire src/ directory for race conditions
/ask-antigravity:rescue --write fix the failing test with the smallest safe patch
/ask-antigravity:rescue --background trace every caller of this function across the repo

Or just ask:

Ask Antigravity to walk through the auth middleware and find anything that breaks under partial failure.