Docs / Agents

Antigravity

Updated

TL;DR — For the Antigravity CLI, `tokenade install` writes a PreToolUse hook to `~/.gemini/config/hooks.json`, rules to `~/.gemini/GEMINI.md`, and wraps `~/.gemini/config/mcp_config.json`. Gemini CLI support ended in 1.1.19.

Tokenade supports Google Antigravity: its command-line agent (agy) is wired through a hook, and the MCP servers of the Antigravity app are wrapped. Gemini CLI is no longer supported: support ended in version 1.1.19, and tokenade uninstall still removes what older versions wrote for it.

Antigravity CLI: what install writes

The Antigravity CLI and the Antigravity editor share the ~/.gemini/ folder (%USERPROFILE%\.gemini\ on Windows, with the dot on every OS). The hook is only installed when ~/.gemini/config/ exists, the CLI's own folder, so a machine with only the editor is not touched.

FileWhat Tokenade adds
~/.gemini/config/hooks.jsonA tokenade entry with one PreToolUse hook
~/.gemini/GEMINI.mdA short Tokenade rules section, the global file Antigravity loads
~/.gemini/config/mcp_config.jsonThird-party MCP servers rewritten to start behind tokenade mcp-wrap

Before a shell command runs, the hook rewrites the command so it goes through tokenade wrap, and its output comes back compacted. The rewrite does not approve the command for you: Antigravity still asks you first, as it would without Tokenade. The rest of hooks.json is left as it is.

What Antigravity gets

From the compatibility matrix: command output, web search, MCP results, code search, re-read dedup, documents and media, and secret redaction are covered. Context optimisation is partial.

Antigravity editor

The Antigravity editor has no shell hook. It gets:

  • MCP optimisation: servers in ~/.gemini/config/mcp_config.json run behind tokenade mcp-wrap. See Wrap MCP servers.
  • The rules section in ~/.gemini/GEMINI.md, so the agent knows the tokenade commands (map, skeleton, query, semantic, read, search) and can call them from its terminal.

Gemini CLI

Gemini CLI support was removed in 1.1.19. If an older version of Tokenade wired it, tokenade uninstall still removes those hook entries from ~/.gemini/settings.json and reverts the older LLM proxy setting it may have written. ~/.gemini/GEMINI.md is kept, because Antigravity reads it too.

Qwen Code, a fork of Gemini CLI, is still supported. See Other agents.

Verify

tokenade healthcheck # checks every agent's hooks are installed and valid
tokenade hooks tail # recent hook fires
tokenade gain # savings ledger

You can also open ~/.gemini/config/hooks.json and look for the tokenade key.

Remove

tokenade uninstall --dry-run
tokenade uninstall

Uninstall removes the tokenade key from ~/.gemini/config/hooks.json, restores your MCP servers, and strips the Tokenade section from ~/.gemini/GEMINI.md. To restore only the MCP servers: tokenade unwrap-mcps. See Upgrade and uninstall.