Google Antigravity
Connect Google Antigravity to Nowledge Mem with the native plugin contributed by abn — startup context, MCP tools, skills, and automatic transcript capture.
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 Google Antigravity. Install the nowledge-co/nowledge-mem-google-antigravity plugin, restart Antigravity, verify with nmem status and the Context Bundle or Working Memory check, then run a short session and confirm nmem t list --source antigravity shows the captured thread.Google Antigravity now has a dedicated Nowledge Mem plugin. The connector started as a community contribution from abn and is now maintained at nowledge-co/nowledge-mem-google-antigravity.
Use this page for Google Antigravity 2.0. If you are migrating the older agy CLI from Gemini CLI, keep the Antigravity CLI guide nearby for that one migration path.
Before You Start
- Google Antigravity 2.0 installed
- Nowledge Mem running locally, or a reachable remote Mem server
nmeminstalled on the same machine as Antigravity
Check the Mem connection first:
nmem statusFor the default desktop setup, it should point to http://127.0.0.1:14242.
Install
Global plugin
Install the plugin into the Antigravity global plugin folder:
mkdir -p ~/.gemini/config/plugins
git clone --depth 1 https://github.com/nowledge-co/nowledge-mem-google-antigravity.git ~/.gemini/config/plugins/nowledge-memOn Windows PowerShell:
$null = New-Item -ItemType Directory -Force "$env:USERPROFILE\.gemini\config\plugins"
git clone --depth 1 https://github.com/nowledge-co/nowledge-mem-google-antigravity.git "$env:USERPROFILE\.gemini\config\plugins\nowledge-mem"Workspace plugin
For one workspace, place or symlink the repo under .agents/plugins/:
mkdir -p .agents/plugins
ln -s /path/to/nowledge-mem-google-antigravity .agents/plugins/nowledge-memRestart Antigravity
Restart Google Antigravity after installing or updating the plugin so rules, skills, MCP, and lifecycle hooks reload.
Remote Mem
Configure nmem once:
nmem config client set url https://your-server
nmem config client set api-key nmem_your_keyThen generate the Antigravity-shaped MCP block:
nmem config mcp show --host google-antigravityPaste the generated mcpServers.nowledge-mem block into Antigravity's MCP settings or ~/.gemini/config/mcp_config.json. Antigravity uses serverUrl, so use the google-antigravity host profile instead of copying a generic MCP snippet.
What You Get
- Context Bundle or Working Memory injected at session start through Antigravity's PreInvocation hook
- Nowledge Mem MCP tools for search, graph exploration, memory writes, threads, and Nowledge FS
- Skills for Working Memory, memory search, distillation, thread save, handoff, skill loading, and status checks
- Stop-hook transcript capture from Antigravity's local
transcript.jsonl - Offline buffering when Mem is temporarily unreachable, then retry on the next session
Thread Save And History
The plugin saves new Antigravity sessions automatically at Stop. Saved threads use the canonical source antigravity, so Google Antigravity, Antigravity CLI, and decoded trajectory fallback imports meet in the same source bucket.
For older local sessions, preview before importing:
nmem t sync --from antigravity --limit 20
nmem t sync --from antigravity --applyUse the trajectory extractor only for old cache-only sessions that do not have the documented Antigravity brain/<conversationId>/.system_generated/logs/transcript.jsonl file.
Your First Success State
You know Google Antigravity is connected when:
nmem statussucceeds from the same machine- a fresh Antigravity session receives Context Bundle or Working Memory when there is context to show
- Mem MCP tools are visible in Antigravity
- after a short session ends,
nmem t list --source antigravityshows the captured thread