{"slug": "antigravity-is-dead-long-live-antigravity", "title": "Antigravity is Dead Long Live Antigravity.", "summary": "At Google I/O 2026, Google rebranded Antigravity from a cursor competitor into a full agent-first development platform powered by Gemini 3.5 Flash, releasing Antigravity 2.0 alongside a new CLI and SDK while discontinuing Gemini CLI. The update caused user data migration issues, with chat histories stranded in a backup directory at `~/.gemini/antigravity-backup`, which can be restored by running an `rsync` command while excluding `mcp_config.json`. Additionally, the new 2.0 installer conflicts with the older IDE version at the OS level, requiring users to choose between the two platforms.", "body_md": "Google just dropped Antigravity 2.0 at I/O 2026—and in the same breath, it killed Gemini CLI, stranded a lot of chat histories in a backup directory, and shipped three new surfaces sharing the same brand. If you opened the app this morning and panicked because your conversations are gone, keep reading. We'll fix it.\nOn May 18, 2026, Google rebranded Antigravity from a \"cursor competitor\" into a full agent-first development platform powered by Gemini 3.5 Flash. The brand now spans four products:\nThe flagship. Runs multiple agents in parallel, ships dynamic subagents for parallelized workflows, schedules tasks in the background, and integrates natively with AI Studio, Firebase, and Android. Export a project from AI Studio on your phone and open it locally, full context intact. Voice command support is in too — you can talk to your agents instead of typing.\nRebuilt from scratch in Go. Same agent harness as the desktop, terminal-native, and noticeably faster than its predecessor. If you live in Gemini CLI today, this is your migration target — and you have until June 18 to switch.\n# Verify your install once you migrate\nantigravity --version\nantigravity agent new \"refactor the auth module\"\nFor building custom agents on top of Google's coding infrastructure, optimized for Gemini models. You define the behaviors; you host wherever it fits — Google Cloud, your own infra, your choice. Custom agent templates are available in AI Studio for enterprise use cases.\nStill maintained. Still the VS Code fork from November 2025. This is the one most of us got hooked on — and it's the one with the migration trap (more on that below).\nIf you updated to 2.0 and your conversations are gone, your data is not lost — the migration stranded it in a backup folder.\nAntigravity 2.0 uses three directories under ~/.gemini/\n:\nAfter the update, the standalone app's antigravity/\ndir frequently ends up missing brain entries, scratch space, and conversation files. The antigravity-backup/\nnext to it has the full set. We just need to put the right one in front of the app.\nmacOS / Linux\n# Dry-run first — see exactly what would change\nrsync -avhn --exclude='mcp_config.json' \\\n~/.gemini/antigravity-backup/ \\\n~/.gemini/antigravity/\n# Looks right? Run it for real (drop the -n flag)\nrsync -avh --exclude='mcp_config.json' \\\n~/.gemini/antigravity-backup/ \\\n~/.gemini/antigravity/\nWhy exclude mcp_config.json\n? It's usually a symlink pointing at your local MCP server configuration — overwrite it and you break your active MCP connections.\nWindows (PowerShell)\n$src = \"$env:USERPROFILE\\.gemini\\antigravity-backup\"\n$dest = \"$env:USERPROFILE\\.gemini\\antigravity\"\n# Robocopy mirror, excluding mcp_config.json\nrobocopy $src $dest /E /XF mcp_config.json\nAfter running:\nantigravity-backup/\nis untouched — you can re-run the sync or copy specific files manually. For peace of mind, snapshot antigravity-backup/\nto an external location before you start poking at it.The good news: the IDE and the standalone 2.0 app keep their data in separate directories (antigravity-ide/\nvs antigravity/\n), so your IDE history doesn't get clobbered when 2.0 installs alongside it.\nThe bad news: the installers conflict at the OS level. Install both and the IDE binary refuses to launch — dependencies are coupled. Uninstalling 2.0 doesn't fully heal the IDE either; you have to reinstall the IDE cleanly, which wipes your IDE settings.\nIf you want to stay on the IDE only:\n~/.gemini/antigravity-ide\nbefore touching anything else.// settings.json\n{\n\"update.mode\": \"manual\"\n}\n~/.gemini/antigravity\nand ~/.gemini/antigravity-ide\nweeklyrsync\nfrom ~/.gemini/antigravity-backup\n(exclude mcp_config.json\n)update.mode\nto manual\nif you depend on the IDEAntigravity 2.0 + CLI + SDK shipped at I/O 2026. Gemini CLI dies June 18, 2026. Lost your chat history? Your data is sitting in ~/.gemini/antigravity-backup\n— rsync\nit into ~/.gemini/antigravity\n(excluding mcp_config.json\n), restart the app. Want the old IDE only? Uninstall 2.0, install 1.23.2 from the releases page, set updates to manual. Pick one — don't run 2.0 and the IDE side by side.\nThe king is dead. Long live the king. Migrate carefully.", "url": "https://wpnews.pro/news/antigravity-is-dead-long-live-antigravity", "canonical_source": "https://dev.to/turingsoracle/antigravity-is-dead-long-live-antigravity-186m", "published_at": "2026-05-20 00:14:21+00:00", "updated_at": "2026-05-20 01:01:19.532718+00:00", "lang": "en", "topics": ["artificial-intelligence", "developer-tools", "products", "cloud-computing", "enterprise-software"], "entities": ["Google", "Antigravity", "Gemini CLI", "Gemini 3.5 Flash", "AI Studio", "Firebase", "Android", "Google Cloud"], "alternates": {"html": "https://wpnews.pro/news/antigravity-is-dead-long-live-antigravity", "markdown": "https://wpnews.pro/news/antigravity-is-dead-long-live-antigravity.md", "text": "https://wpnews.pro/news/antigravity-is-dead-long-live-antigravity.txt", "jsonld": "https://wpnews.pro/news/antigravity-is-dead-long-live-antigravity.jsonld"}}