A large diff from an agent is easy to produce and slow to review, especially when you are hunting for one identifier across a dozen files. This week /diff gets search with match counts and n/N navigation, and the rest of the diff viewer gets better at folding and highlighting. Around that, plugins, permissions and the status line get smaller but practical changes.
The period is Week 43, October 20-24, 2026, covering versions 1.4.3 to 1.4.7: 5 releases and 72 changelog entries. Below are the changes that matter for daily work, grouped by what they touch.
Search a whole diff instead of scrolling it
What it is. Version 1.4.3 adds / search to the /diff file list and the file view. Matches are highlighted as you type, so you see the result before you commit to the query.
How it works. The search prompt shows how many matches the whole diff contains and how many each file contains. Press Enter to jump to the first match. After that, n and N step through matches one at a time across every file, not just the one you are looking at. In the file view header you see match A/B, which tells you where you are in the sequence.
What it is good for. The per-file counts let you check a rename or a changed call across the whole change set. You can see which files contain it and skip the ones that do not, without opening each file.
The artifact viewer gets the same stepping. n and N there now move one match at a time, including several matches on the same line. Before, they jumped from line to line, so a second match on the same line was easy to miss.
Changes for everyday work
Folding in Commit Tree and Per Turn. Both views in /diff now have a whole-file toggle on f and hunk folding on Ctrl+O. Folding lets you collapse hunks you have already reviewed and keep the rest on screen. Combined with the new search, a long diff becomes something you can work through in order.
One diff per file in Per Turn. If the agent edited the same file several times within one turn, Per Turn now shows a single combined diff for that file. You review the net result of the turn instead of each intermediate edit.
Word-level highlighting. Since 1.4.6, /diff highlights the exact words that changed inside each modified line, in every color scheme. A one-token change in a long line is no longer something you have to find by eye.
Auto mode on Windows 11 24H2 and later. Version 1.4.4 makes Auto mode available to personal Google Account users on Windows 11 version 24H2 or later. Conditions:
- Windows 11 version 24H2 or later.
- A personal Google Account.
- Select it with
--mode auto,Agent Modein/config,Shift+Tab, or Remote Control Settings.
Agent remains the default, so nothing changes until you pick Auto.
Configure plugin MCP servers at any time. Installed plugins in /plugin now have a Configure MCP servers... row (1.4.6). You can set or change MCP server variables without disabling and re-enabling the plugin. Plugins with missing values show ⚠ needs setup, and each server shows ✓ configured or the variables it still needs. Saving restarts an enabled plugin’s servers, so the new values apply immediately.
The status line says what the agent is waiting on. Instead of a generic working label, the in-progress status line now names the wait, for example initializing MCP servers or retrying an unavailable model. Retries come with a live countdown, such as Model unavailable (attempt 2/10), retrying in 12s. In practice, that lets you tell a retry loop from a stalled session at a glance.
Technical notes
Hooks. Hook commands now receive lastUserInput in their stdin JSON (1.4.7). A hook can therefore screen your latest message before the agent acts on it.
Plugin validation. agy plugin validate became much stricter across 1.4.3, 1.4.4 and 1.4.6. It now has --help and checks hooks, sidecars, component lists, MCP configs, context providers and skills entries.
Permissions and subagents. Allowing an action for the conversation now applies to the main agent and all its subagents (1.4.6), so you are not asked again for the same action. In Auto mode, subagents and custom agents get the same separate-agent command review as the main agent (1.4.3), so safe commands run without prompts.
Context compaction. Compaction, including /compact, now keeps images, PDFs and other attached files in the summary (1.4.6). The agent can still see them after compaction.
MCP. tools/call requests now carry the antigravity.google/root_conversation_id key in _meta (1.4.4). Servers receive the top-level conversation ID even when the call comes from a nested subagent. On-demand MCP tools now return results up to 10 KB directly (1.4.7). Before, anything over 4 KB was saved to a file for the agent to read.
Scheduling. Recurring cron schedules from the schedule tool now fire at a consistent per-schedule offset to avoid traffic spikes (1.4.5). The agent can request exact timing when you need it.
CPU use. Headless -p runs use much less CPU (1.4.7). They skip the conversation search index, transcript rendering, and custom status line and window title commands. Idle CPU use roughly halves in 1.4.5, because screen refreshes pause while nothing changes.
Models and authentication. Gemini 4 Argon now appears in /model and --model when you connect with a GEMINI_API_KEY (1.4.3). Skills, rules, custom agents, plugins, plugin MCP servers and hooks now load when you sign in with Application Default Credentials (AGY_ADC_AUTH), as of 1.4.7.
What to take away
If you live in the terminal. Open /diff on your next real change and try /, Enter, then n/N. Then try Ctrl+O to fold reviewed hunks and f for the whole file in Commit Tree or Per Turn. If you run scripted -p sessions, the lower CPU use is worth a quick comparison on your own jobs. Windows 11 24H2+ users on a personal Google Account can try Shift+Tab to switch to Auto mode.
If you run parallel sessions. Check how the shared permission behaves: one allowed action now covers the main agent and its subagents. That means fewer repeated prompts, and it also means you should look at what you allow. The new status line makes it easier to see which session is waiting on an MCP server or retrying a model. After a /compact, attachments stay visible to the agent, so you do not need to re-attach them.
If you administer integrations and company deployments. Run agy plugin validate over your plugins again, since the checks are stricter and now cover hooks, MCP configs and skills entries. In /plugin, look for ⚠ needs setup on installed plugins and fill the gaps through Configure MCP servers.... If you write hooks, lastUserInput opens up message screening. MCP server authors can read antigravity.google/root_conversation_id in _meta to correlate calls from nested subagents. If you authenticate with AGY_ADC_AUTH, confirm that skills, rules, plugins and hooks now load as expected.
Sources: the Antigravity CLI changelog, versions 1.4.3 to 1.4.7 (October 20-24, 2026), and the Antigravity CLI documentation. Check the changelog for the current state of each feature, as details may change in later releases.
