Google Antigravity CLI 1.3.1

Changelog: Enhanced /diff navigation and position indicators, Windows plugin lifecycle management, and subagent and task status fixes

Enhances /diff file view navigation with preserved cursor positions, cross-file n/N change traversal, and a change A/B · file X/Y header indicator, while fixing /rewind on compacted messages, Windows /plugin MCP server lifecycle handling, relative paths in Markdown custom agents, subagent error states, and background task tracking.

Improvements(2)

• Improved navigation in the /diff file view: ←/→ now open the next or previous file at its first change with the hunk header and leading context in view, each file remembers its cursor and scroll position when you switch files or go back to the file list, n/N continue into the next or previous file's changes instead of stopping at the last change in the current file, and the key-hint footer drops the generic scroll and page hints and wraps onto extra lines instead of being cut off on narrow terminals.
• Improved the /diff file view header to show where you are: it now ends with a right-aligned change A/B · file X/Y position, counting the block of added or removed lines under the cursor and the file's place in the file list (file X/Y is left out when only one file changed, and the position is hidden on narrow terminals).

Fixes(10)

• Fixed /rewind in very long conversations listing older messages as (empty message) and failing with an error when you picked one: messages that were cleared to save space now show their original text, dimmed and labeled cleared to save space, can't rewind here, and can no longer be selected.
• Fixed installing, reinstalling, and uninstalling plugins with /plugin on Windows failing while one of the plugin's MCP servers was running: the CLI now stops the plugin's MCP servers before replacing or deleting its folder and restarts them afterwards, and if another Antigravity process such as another agy session, the Antigravity Hub, or the remote-control daemon still holds the plugin open, it tells you to close it and retry. Plugin manifests, mcp_config.json, and hooks.json files saved with a UTF-8 byte-order mark now load, and installing from a marketplace no longer overwrites an existing plugin folder that came from a different source.
• Fixed markdown custom agents ignoring skills:, plugins:, rules:, agents:, and hooks: entries written as paths relative to the agent's own file when the agent ran as a subagent or as the main agent; such entries now resolve against the agent's directory, so an agent that lists agents: [child.md] can invoke child.
• Fixed subagents that stopped on an error, such as running out of quota or model capacity, being shown as Done in /agents and the list of running agents; they now show Error: with the reason, and the error clears once the subagent makes further progress.
• Fixed /tasks, the active task list, and the status line's task count showing only background shell commands; timers and recurring jobs the agent schedules, and other tools running in the background, now appear there too and are shown as completed or failed without a made-up exit code.
• Fixed messages sent with Queued Messages set to Send Immediately in /config being silently queued until the end of the turn whenever the agent had already written or updated an artifact, such as a task list or plan, during that turn; they now reach the agent right away.
• Fixed terminal notifications not firing when the agent stops to ask you a question; with Notifications turned on in /config, the CLI now alerts you for pending questions just as it does for tool permission prompts.
• Fixed restarting an MCP server from /mcp sometimes leaving it stopped, with an error such as Failed to stop existing instances for reload: ... signal: killed, when the old server process took too long to exit; the server now always starts again.
• Fixed the sign-in error for accounts that need to verify their identity or appeal a Terms of Service block sometimes showing only Verify your account to continue. with no link; the verification or appeal link now always appears, and the CLI no longer suggests logging out and back in when that would not help.
• Fixed GEMINI_API_KEY sessions failing a turn as if you had cancelled it when the connection to the Gemini API was dropped internally; the CLI now retries the request instead.

<h3 class="