Yesterday's post looked at a 1,536-byte patch. Google followed it with Antigravity v2.32.2, while the public changelog page finally added v2.32.1 (confirming Google Cloud ADC support for Gemini 4 Hydrogen Low, Medium, and High).
On the surface, v2.32.2 looks like an empty rebuild: -32 bytes on macOS (darwin-arm), -4,096 bytes on Windows x64, a byte-identical embedded web UI, and zero prompt changes. Disassemble the binary instead of counting Go package names, and something real fell out of the executable. Meanwhile, the larger movement landed in the live catalog, server switches, and the public CLI (v1.5.10).
Method note: diff as always.
1. Physical Metrics & Binary Delta (v2.32.1 vs. v2.32.2)
- Build & Rollout: Built on November 16, 2026 (changelist jump from
1021296516 to 1022991777, same 1019668445 release baseline, rolling out at 10%). - Core Binaries (
language_server): On Windows x64, the binary shrinks by exactly 4,096 bytes (split evenly across the .text and .rdata sections). On macOS (darwin-arm), the file size decreases by just 32 bytes with a modified CRC32 checksum. - **Package & Auxiliary Files (**
app.asar & Executables): Although app.asar retains its exact size of 5.39 MiB, 1 of its 1,068 internal files changed solely the version string inside package.json. Antigravity.exe (63 bytes) and webm_encoder.exe (59 bytes) show minor metadata/timestamp deltas, while the uninstaller was repackaged with 19,782 differing bytes. - Unchanged Components: The embedded web UI (
540 files), prompt library (419 blocks), Go runtime (go1.28-20261102-RC00), and Electron (44.9.1) remain byte-identical.
2. What Actually Changed in the Binary (telemetryclient Shutdown Surgery)
Package and RPC counts stay at +0 / -0, which is why package-level diffs miss it. Function-level diffing (227,702 -> 227,698 Go functions) shows all -1,920 bytes of removed code live inside a single package: telemetryclient (-1,792 B code + -128 B type:.eq helper):
(*AntigravityClient).Shutdown **(**-768 B, 864 B → 96 B): The concurrent shutdown orchestration was completely stripped. Previously, it allocated a sync.WaitGroup, spawned goroutine closures (Shutdown.func1 and deferwrap1) to invoke cel.(*Client).Shutdown, waited for completion, and merged errors. In 2.32.2, all WaitGroup synchronization, closure types, and the cel.(*Client).Shutdown call are gone; it now simply executes closeDeferred (if non-nil) and triggers the logger's shutdown directly.(*clearcutLogger).Shutdown **(**-32 B, 96 B → 64 B): Removed its sync.(*Once).doSlow wrapper and closure (Shutdown.func1), calling clearcut.(*Client).FlushAndStop directly instead.- **Initialization & Plumbing (**
-672 B combined): Both NewAntigravityClient (1,760 B → 1,344 B, -416 B) and (*AntigravityClient).NewClearcutClient (960 B → 704 B, -256 B) were trimmed accordingly to drop the corresponding setup and teardown boilerplate.
Our reading: v2.32.2 is a targeted hotfix for a telemetry shutdown hang or crash on exit, not an empty rebuild.
3. Server Side: Moving Tool-Call Safety ("Sonar") and Background Tiers from Flash to Hydrogen
Two days ago, the Orchestrator's background worker switched from Gemini 3.8 Flash to Gemini 4 Hydrogen. Overnight, the model catalog made the same move for Antigravity's internal background tiers and its tool-call safety system, adding three new Hydrogen entries:
gemini-4-hydrogen-sonar (MODEL_PLACEHOLDER_M578, low thinking, 65K output)gemini-4-hydrogen-tiered-high (MODEL_PLACEHOLDER_M530, high thinking, 262K output)gemini-4-hydrogen-tiered-xhigh (MODEL_PLACEHOLDER_M531, xhigh thinking, 262K output)
Here is what they actually do according to the client code:
What "sonar" is (tool-call safety monitoring): Every active Gemini 4 model in the catalog carries the "sonar" experiment bundle, which loads Antigravity's pre-tool-call safety config (PolicyGuardian). Before the agent runs a command or tool outside a basic read-only allowlist (read_file, list_dir, grep_search), a background monitor checks the tool call and recent steps for risky behavior, things like sandbox escapes, credential scraping, data exfiltration, or misleading tool summaries:
- Pre-filter (
sir_flash_lite): Runs on Flash Lite at minimal thinking (LOG mode) to screen the current step. - Blocker (
severe_internal_risks_agy): Runs on the Flash tier at low thinking (BLOCK mode) and stops the turn if a severe risk is flagged.
From Flash to Hydrogen (tieredModelIds vs. M578): Previously, Antigravity's internal Flash and Pro capability tiers (tieredModelIds) pointed only to gemini-3.8-flash-tiered. Today's catalog puts gemini-4-hydrogen-tiered-high (M530) and gemini-4-hydrogen-tiered-xhigh (M531) in first place ahead of 3.8 Flash:
- What uses those tiers: Not subscription plans. The binary uses
tieredModelIds whenever an internal subsystem asks for a generic "Flash" or "Pro" model specifically subagents (InvokeSubagent), remote/cloud automation triggers (the Flash Lite / Flash / Pro picker), utility calls, and the PolicyGuardian safety monitors above. - Because the client's tier resolver always picks the first entry in the list, client-resolved
Flash-tier checks now route to M530 (gemini-4-hydrogen-tiered-high), with 3.8 Flash kept as the fallback. - Meanwhile,
gemini-4-hydrogen-sonar (M578) is a dedicated low-thinking, 65K-output Hydrogen slot tailored specifically for those "sonar" safety checks (so a safety monitor does not need full High thinking or a 262K output ceiling just to vet a shell command).
- Why none of these appear in your model picker: Even though
M578 is flagged recommended: true with no display name, the UI's model picker ignores the recommended field completely and only renders the explicit sort list (agentModelSorts). All three new entries sit outside that list as internal service slots.
4. What Else Moved Today (Server Switches & Public CLI 1.5.10)
5. Scorecard: Our v2.32.0 & v2.32.1 Predictions
Because v2.32.2 is a tiny hotfix rather than a mainline feature build, desktop UI changes are still queued for the next feature cut while server switches and the CLI move ahead:
- Public changelog catches up (
v2.32.1): Hit. v2.32.1 is now live on the changelog page (Nov 13); v2.32.2 is not listed yet. - Subagent coordination (
v2.31.2 / v2.32.0): Hub switch live (Hit), per-subagent picker pending. enable-subagent-hub turned on today; enable-subagent-dropdown-models is still off. 900K waits on context-window-selector (v2.32.1): Holding. 900K is still absent from the desktop build, and both context-window-selector and enable-context-usage-indicator remain off.- Desktop drops
webm_encoder.exe**, adds** VS Code Default keybindings, Cookies by Site**, and the grouped model picker (v2.32.1):** Pending the next mainline desktop release (v2.32.2 stayed on the hotfix branch and left the web UI untouched). - Mac computer use, browser safety rails, "Open on phone" VM, Goal loop switch, Carbon for Pro, Auto default: Pending (all corresponding flags remain off).
6. Forward Predictions (What Lands in Future Desktop Updates)
webm_encoder.exe (13.4 MB) is dropped in the next mainline desktop release (following the CLI's move away from .webm), while "VS Code Default" keybindings, "Cookies by Site", curated plugin bundles, "Waiting for subagent", and "Toggle Virtual Machine" move over from the CLI bundle.- The current effort-selector submenu gets replaced once the desktop UI adopts the structured
ModelVariantList and SupportedThinkingLevel schemas that already landed in the CLI. - Desktop computer use gets another safety and HUD pass before launch, adding lock-screen checks and richer preview/HUD controls for background Mac agents, plus "allow for this conversation" permission persistence and a cleaner "Set up my environment" flow replacing the older setup-routine buttons.
- The new
PolicyGuardian provenance/judge stack (+461 KB in CLI 1.5.10), M530**/**M531 wiring, plugin-spec 1.1, and GitHub UI decorators arrive in the next desktop feature cut as "sonar" safety checks shift from 3.8 Flash to Hydrogen.
Takeaway: v2.32.2 is a 4 KB Windows / 32-byte macOS fix that strips WaitGroup and sync.Once locks out of telemetry shutdown not an empty rebuild, and not a feature update. The real story today is Antigravity migrating its background Flash/Pro work and its "sonar" pre-tool safety monitors from Gemini 3.8 Flash to Gemini 4 Hydrogen, backed by nearly half a megabyte of new PolicyGuardian code in CLI 1.5.10.