migrate
Migrate an existing Claude Code setup (skills, memory, CLAUDE.md, MCP, plugins, permissions) to the Antigravity CLI.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/yuting0624/antigravity-for-claude-code/HEAD/commands/migrate.md -o ~/.claude/commands/migrate.mdmigrate.md
Migrate this machine's Claude Code configuration to Antigravity (`agy`). Run the tool in **dry-run first, always**: `agy-migrate $ARGUMENTS` Then read the report back to the user, grouped by unit, and explain: - What will be **linked live** (skills stay in `~/.claude/skills`; Antigravity reads them in place via `skills.json`) versus **generated** (memory, MCP, permissions — these need a format change, so they become new files). - Anything marked `⚠`. Do not gloss over these; they are the parts that need a human decision. In particular: permissions are only ever written as a *proposal* unless `--apply-permissions` is passed, because Claude's allow-list stores whole command lines and collapsing them to `command()` prefixes always widens the grant. - Anything marked `needs-flag`, and the exact flag that would include it. Only run with `--apply` after the user has seen the dry-run and agreed. Then tell them: - the backup path the tool printed, and that `agy-migrate --uninstall --apply` reverses it; - that session history (`~/.claude/projects/*.jsonl`) is **not** migrated and cannot be — Antigravity stores conversations as protobuf blobs inside per-conversation SQLite files; - that workspace rules under `.agents/` only load when the session is bound to an agy project, which is why the tool registers repos in `~/.gemini/config/projects/`. If the user is only asking what *would* move, stop at the dry-run — do not apply. For the full compatibility matrix and the reasons behind each mapping, read `docs/MIGRATION.md` in this plugin.
Run the Antigravity CLI (Gemini) as a collaborating AI inside Claude Code, with intelligent model routing across the software development lifecycle. Claude is the conductor/orchestrator — requirements, architecture, the hard 20%, verification, and review — and routes deterministic, high-volume work (scaffolding, boilerplate, test generation, first-pass review, migrations, web/Vertex AI Search) to Antigravity (Gemini), the cheaper, faster model. Use when the user wants to "use Antigravity / agy", "vibe code / agentic engineering", "accelerate the SDLC", "delegate to Gemini", "scaffold / generate tests / migrate", "first-pass code review", "search web or internal/company data", "deep research / multi-source research report", "second-model cross-check", or "lower token cost on a big job". Claude always verifies Antigravity's output and re-checks itself if unsatisfied.
|
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.
Move an existing Claude Code setup onto the Antigravity CLI (agy) — user skills, CLAUDE.md, auto-memory, MCP servers, installed plugins, permissions and trusted workspaces. Use when the user says "migrate to Antigravity", "move my Claude Code config to agy", "bring my skills/memory/MCP over", "set up agy like my Claude Code", "agy plugin import claude found nothing", or asks what can and cannot be carried across. Also use to explain the two config layouts, or to reverse a migration.
Claude-orchestrated deep research — Antigravity (agy/Gemini) does the grounded web legwork; Claude plans, verifies the citations, and synthesizes.