setup
Verify the Antigravity (agy) CLI is installed and authenticated and the plugin is ready to use.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/yuting0624/antigravity-for-claude-code/HEAD/commands/setup.md -o ~/.claude/commands/setup.mdsetup.md
Run the plugin's doctor and report status. Run: `agy-doctor` Then summarize for the user: - Is `agy` installed, and can it list models (i.e. authenticated)? - Are the plugin scripts executable? - What GCP project / region / default model is `agy` configured for? If anything is missing or failing, give the **exact** command to fix it (install agy, authenticate, `chmod +x` the scripts, etc.). Keep it short and actionable.
|
Cancel a running background Antigravity (agy) delegation job.
Diagnose a failing Cloud Run service — Antigravity (agy/Gemini) digests the error logs cheaply, Claude infers the root cause and proposes a fix. Read-only by default; --apply writes the fix to a branch.
Delegate a well-scoped subtask to Antigravity (agy/Gemini) under cost discipline, then verify.
Understand an audio / video / image file — Antigravity (agy/Gemini) transcribes and analyzes it, returning a timestamped digest while the full transcript goes to a file.
Migrate an existing Claude Code setup (skills, memory, CLAUDE.md, MCP, plugins, permissions) to the Antigravity CLI.
Claude-orchestrated deep research — Antigravity (agy/Gemini) does the grounded web legwork; Claude plans, verifies the citations, and synthesizes.
Fetch the output of a finished background Antigravity (agy) job, then verify it.