Antigravity CLI
Connect Google's Antigravity CLI (agy) to Nowledge Mem — migrate the Gemini CLI extension, wire MCP, and keep session capture working.
For your agent
Give this line to your agent. It should use the universal install skill first; this page remains the behavior and troubleshooting reference:
Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for Antigravity CLI. Verify with nmem status and the Context Bundle or Working Memory check, then summarize what changed.Gemini CLI is being retired
Google has replaced Gemini CLI with Antigravity CLI (agy). Gemini CLI stopped serving individual-tier accounts (Google AI Pro, Ultra, and free Code Assist) on June 18, 2026. Antigravity CLI shares the same agent harness as the Antigravity desktop platform and reuses your existing ~/.gemini home directory, so most Gemini CLI setups carry over.
Antigravity CLI is Google's official successor to Gemini CLI. The migration story is good: it reads the same ~/.gemini home, honors both GEMINI.md and AGENTS.md, and can import installed Gemini CLI extensions as Antigravity plugins — including the Nowledge Mem extension.
Before You Start
- Nowledge Mem running locally (installation) or a reachable remote Mem server
- Antigravity CLI installed:
# macOS / Linux
curl -fsSL https://antigravity.google/cli/install.sh | bash
# Windows (PowerShell)
irm https://antigravity.google/cli/install.ps1 | iexnmemin yourPATH(see installation or use the desktop app's Settings → Preferences → Developer Tools → Install CLI)
On first launch, agy signs you in with your Google account and offers to import your existing Gemini CLI configuration (MCP servers, allow-listed commands, keybindings, theme). Accepting that prompt is the fastest starting point.
One-Minute Setup
Install Nowledge Mem for Gemini CLI first
If you have not already, install the Nowledge Mem extension for Gemini CLI — see Gemini CLI. The Antigravity path builds on top of it.
Import the extension into Antigravity
agy plugin import geminiThis converts installed Gemini CLI extensions — including Nowledge Mem — into Antigravity plugins.
Run nmem status once
For the default same-machine setup, this should point to http://127.0.0.1:14242 (default).
Open a new agy session
The imported plugin loads its context files, commands, and bundled MCP tools automatically, the same way it did under Gemini CLI.
MCP Configuration
Antigravity CLI keeps MCP servers in a dedicated mcp_config.json (workspace path: .agents/mcp_config.json). If you configure the Mem MCP server manually, note one format difference: remote server definitions use serverUrl instead of url.
Generate the right block for your setup:
nmem config mcp show --host gemini-cliThen place it in .agents/mcp_config.json, renaming url to serverUrl for remote servers. This keeps Antigravity's MCP tools and nmem pointed at the same Mem server.
Import Older Sessions
Session capture uses the same local history under ~/.gemini, so the existing Gemini CLI import path applies:
# Preview
nmem t sync --from gemini-cli --all-projects --limit 20
# Import
nmem t sync --from gemini-cli --all-projects --applyUse -p /path/to/project when you only want one project.
Customize Safely
Both context files work in Antigravity CLI:
- project
GEMINI.mdorAGENTS.md - optional
~/.gemini/GEMINI.mdfor personal defaults
Do not edit the installed plugin files directly. Full map: Customize Integration Behavior.
Your First Success State
You know Antigravity CLI is wired correctly when:
agy plugin import geminicompletes and the Nowledge Mem plugin appears in a new sessionnmem statusreturns successfully- Context Bundle or Working Memory appears at the start of a fresh session when there is context to show
save-threadimports a real session, and long sessions are saved before compression as well as at session end
Known Boundaries
- The import path (
agy plugin import gemini) is Google's official migration channel and the supported way to run the Nowledge Mem extension under Antigravity today. - Session capture currently reads the shared
~/.geminihistory through the Gemini CLI connector. If Google moves Antigravity session storage, capture behavior may change; checknmem t sync --from gemini-cli --limit 5after upgradingagy.