Google Antigravity CLI 1.2.2

Changelog: Plugin MCP namespacing, conversation memory leak fixes, oversized file guardrails, and unsandboxed rule migration warnings

Enhances startup migration diagnostics for unsandboxed permission rules, speeds up /resume with stale caches, automatically namespaces plugin MCP servers to avoid collision, resolves step-cache goroutine leaks, and fixes critical issues with Gemini API thinking block retention, oversized binary file loading, artifact reviews, and database cleanup.

Improvements(2)

• Improved the startup warning for deprecated unsandboxed permission rules across CLI, shared, and project configuration files to list each affected file path, up to five offending rules, and step-by-step instructions for migrating them to command rules.
• Improved /resume startup responsiveness when opening a large conversation history with a cold or stale summary cache.

Fixes(7)

• Fixed MCP servers bundled inside plugins colliding with each other or with user-configured servers in mcp_config.json when they shared the same server name by automatically namespacing plugin MCP servers as _.
• Fixed a memory leak where opening or scanning conversations left background step-cache eviction goroutines running for the rest of the session, significantly reducing memory usage after opening /resume or switching conversations.
• Fixed view_file attempting to parse non-UTF-8 binary files as text or loading files larger than 100 MB into the model context; unsupported binary formats and oversized files are now rejected with a clear error before overflowing the context window.
• Fixed Gemini API (GEMINI_API_KEY) sessions dropping model thinking blocks from prior turns on subsequent user messages and failing to propagate thought signatures on text and thought parts.
• Fixed artifact review failing to trigger when a directory name above .gemini/ matched a skipped path component such as scratch, prevented conversation forks and snapshot reverts from copying internal .system_generated/subagents and .system_generated/worktrees directories, and cleaned up subagent metadata records when deleting a conversation.
• Fixed deleted conversations being recreated as empty, schema-less SQLite database files when background queries reconnected after deletion.
• Fixed conversations launched without a workspace folder inheriting workspace paths and customizations from other open sessions.

<h3 class="