migrate-to-antigravity

Featured

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.

AI & Automation 324 stars 30 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
84
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Migrating Claude Code → Antigravity CLI Run `agy-migrate` (dry-run) → read the report → `agy-migrate --apply`. `agy-migrate --uninstall --apply` reverses everything. The tool treats the Claude Code config dir as **read-only**. The single exception is an `AGENTS.md` symlink placed beside an existing `CLAUDE.md`, and only under `--include-repos`. --- ## Where the two products keep things **Claude Code** — `~/.claude/` plus `~/.claude.json`, relocatable together via `CLAUDE_CONFIG_DIR`. Two things surprise people: there is usually no `~/.claude/CLAUDE.md`, and **auto-memory is per project**, under `~/.claude/projects/<encoded-cwd>/memory/`. The encoding maps `/`, `_` and `.` all to `-`, so it can only be matched forward (re-encode a known path), never decoded. **Claude Desktop / Cowork is a separate universe.** It has its own `~/Library/Application Support/Claude/claude_desktop_config.json` (MCP) and `Claude Extensions/` (`.mcpb`), and its Cowork skills are server-synced into `local-agent-mode-sessions/skills-plugin/`, so no local original exists to migrate. Only `claude_desktop_config.json`'s `mcpServers` is portable, and the tool picks it up. The bundled `claude-code/<version>/claude.app` inside the desktop app is the ordinary CLI and does read `~/.claude`. **Antigravity** — rooted at `~/.gemini/`, not `~/.antigravity`: | Path | Shared by | | --- | --- | | `~/.gemini/config/` — `mcp_config.json`, `skills/`, `plugins/`, `skills.json`, `projects/` | CLI **and** both de...

Details

Author
yuting0624
Repository
yuting0624/antigravity-for-claude-code
Created
2 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Anthropic · AI Model Context Protocol · AI

Bundled in these plugins

antigravity

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

antigravity

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.

324 Updated today
yuting0624
AI & Automation Listed

migrate

Migrate settings between AI coding tools (Claude Code, Codex CLI, Cursor, Grok Build) — rules, MCP servers, skills, subagents, hooks, permissions. Use when the user asks to import or migrate settings from another AI tool, or runs /migrate [source].

2 Updated 2 weeks ago
chakki-the-potato
AI & Automation Listed

codex-claude-migration

Audit, back up, move, restore, or attach complete Codex Desktop, Codex CLI, and Claude Code workspaces while preserving conversations, archived sessions, project membership, projectless sessions, thread-linked goals, real project roots, settings, skills, agents, AppData, and rollback evidence. Use for AI workspace migration to another disk or computer, portable-drive setup, disaster recovery, sidebar repair after a move, or verified cleanup of retained source backups.

0 Updated 1 months ago
wanghao198822