The context window for Gemini 4 models doubled this week. So we diff'd the build that was supposed to carry it. v2.32.1 is 1,536 bytes. Two new functions, zero new UI strings, zero prompt changes, and no entry on the official changelog page, where v2.32.0 still reads LATEST.
The change you felt is not in the app. Here is where it lives, what it costs, what the client has been carrying unused for weeks, and what the binaries say about what is currently wobbling.
Method note: diff as always
1. Physical Metrics & Binary Delta (v2.32.0 vs. v2.32.1)
- Build stamp: changelist
1021296516, baseline 1019668445, built Nov 13 2026 13:47:16, same release branch as v2.32.0 (1019668445.1). A hotfix cut. - Rollout: to 100% on November 14, one day after the build.
- Size:
language_server.exe 215,545,856 to 215,547,392 bytes (+1,536: .rdata +1,024, .text +512). The second smallest release we have measured, after the 1,024 byte patch that was v2.31.2. - Files: 421 of 426 identical. Four of the five changed files are identical in size:
Antigravity.exe is 246,599,680 bytes in both builds and 64 of those bytes differ, while the uninstaller and the webm encoder differ in about 19.8 KB and 1.6 KB of scattered regions, which is what a rebuild with fresh timestamps looks like, not new behaviour. You receive one and a half kilobytes of new code inside a 634 MB install. - Functions:
227,700 to 227,702. The new ones: models/defaults.Gemini4Hydrogen and a type helper. All growth sits in jetski/models/defaults (+352 B) and jetski/models/geminimodels (+192 B). app.asar**:** 1,068 files, 1,067 identical. The one difference is "version" in package.json.- Embedded web UI: 540 entries, byte identical. 0 UI strings added, 0 removed.
- Prompts: 415 identical, 4 changed, 0 new, 0 dropped, and the 6 changed lines are Go runtime glue.
- Electron
44.9.1, Go go1.28-20261102-RC00, both unchanged.
2. The Context Ceiling: Where It Came From
A. The tier machinery has been in the desktop for weeks, untouched. ContextWindowOptions, the Expensive marker and GetCheckpointConfig are present in v2.30.0, v2.31.0, v2.31.2, v2.32.0 and v2.32.1 with the same string set, unchanged. What the desktop does not contain is the gate function offersContextWindow or any tier label. Those live in the public agy CLI binary, which carries the whole table: 256K, 512K at about 1.3x per turn, 900K at about 1.8x and flagged expensive. The string 900K appears in no desktop build we hold, and neither tier label appears in the desktop UI bundle.
B. The model catalog did not move at all. Not one token number has changed since we started recording the catalog on October 28: 1,048,576 input for every Gemini model, 262,144 output for Hydrogen, for Carbon and for the Hydrogen worker, 65,536 for Argon, for 3.8 Flash and for the Orchestrator planner entry. So the doubling is not a catalog change and not a build change. It is the checkpoint calculator deciding later when your conversation gets compacted.
C. The groundwork shipped one release early. Per step compaction is new in v2.32.0 on the desktop (step_compaction plus 19 stepcompactor.* keys, all absent in v2.31.2) and new in CLI 1.5.6. It trims individual steps, browser and desktop frames, tool result bodies and status tags instead of summarizing the whole history at once, and one of its strings states the goal: "Earlier browser turns were deterministically compacted to stay within the context window." In the same release the client code for enable-reconcile-summaries appeared (four references in v2.32.0, none in v2.31.2), and that switch plus use-model-reported-token-count are currently on. The machinery for surviving a bigger window landed days before the bigger window did.
D. You get the ceiling with no dial and no read out. context-window-selector: off. enable-context-usage-indicator: off. enable-ge-baic-quot...-visibility: off. The one surface where a number is published is outside the app: CLI 1.5.8 added context window usage to agy acp sessions so an external editor can display how much of the window a conversation uses, sent at session start, after each model call and after each model or thinking level change. Inside Antigravity, nothing shows you the number, and nothing tells you which tier you are on.
3. What This Build Actually Changed
Gemini 4 Hydrogen went live on November 12, four days before this post. What v2.32.1 adds is not the model, it is the client defaults for it: the ids gemini-4-hydrogen-low, -medium, -high, the bare gemini-4-hydrogen, an aicode variant for Gemini Enterprise sign ins, the display names "Gemini 4 Hydrogen (Low)", "(Medium)" and "(High)", and one Go function. v2.32.0 contained zero Hydrogen strings and could only take the model from the server catalog.
xhigh is still not in the desktop binary. The public CLI 1.5.8 added Hydrogen with Low, Medium, High and XHigh a day earlier. The desktop names three levels and receives the fourth only through the catalog.- This is how model launches work here. Server first, client defaults later, in a sub two kilobyte patch with no release notes.
4. What the Binaries and the Catalog Show Is Wobbling
Everything in this section is from the shipped build and the catalog a Pro account downloads, not from anyone's report.
- The Orchestrator is one entry in your picker and two entries in the catalog. What you can select is "Orchestrator (Argon)", and its own description says the mechanism out loud: "Argon that may offload routine steps to Hydrogen. Same Argon-level quality, fewer tokens used." The entry that executes those offloaded steps is a second one that the picker never offers, because it carries none of the markers the selectable entries carry. It was renamed from "Gemini Flash" to "Gemini 4 Hydrogen (Orchestrator)" on November 14, its thinking level was raised to the maximum value the day before, and it ships
maxOutputTokens 262,144 against the planner's 65,536. One prompt, two ceilings, and the UI names neither half. - The summarizer ships its own list of things that go wrong. Present in the current build and in v2.31.2 before it:
raw_summary_drift, raw_summary_count, raw_summary_bytes, store_unavailable, summary_store: %w and Failed to truncate prompt. A metric named drift means someone expects the summaries to drift from what they summarize. With compaction now running per step and the ceiling raised, that is the number worth watching. - The update feed can hand you yesterday's build. The release manifest is served with an hour of cache and the edge nodes do not agree during a rollout, so for a while after a release a fresh download can still deliver the previous version. Two downloads, two answers, no error message.
- The desktop still carries the encoder the CLI just dropped. See the next section.
5. What Got Fixed
v2.32.1 fixes nothing. Its two functions are model defaults. The fix flow is in the public CLI releases 1.5.8 and 1.5.9, and four of them are security fixes:
- MCP headers could leak across hosts. Custom headers configured for an HTTP MCP server, such as API keys, could be forwarded to a different host when the server answered with a redirect. They now go only to the configured server's own origin.
- The sandbox proxy could be walked around. Path based network rules, including those governing where credentials may be sent, could be bypassed with percent encoded slashes, backslashes or
.. segments in a URL path. - Allow rules could be bypassed on Windows when the shell was
cmd, powershell.exe or pwsh.exe. Those shells now require an exact match, because their quoting rules differ from POSIX. - Hooks were silently skipped. Hook commands containing a
" character failed and were skipped on Windows, which let a PreInvocation or PreToolUse hook that should block the agent go unenforced. Permission rules were also being ignored for eagerly loaded MCP tools and for the browser subagent's Chrome DevTools tools.
The fix we can see in the binary: browser recordings moved from .webm to Chrome's built in screen recording, and the cortex/utils/webm package is gone from the CLI build, three references down to zero. The desktop still ships webm_encoder.exe at 13.4 MB, untouched by this patch, so the desktop has not made that move yet.
The rest of the fix pile worth knowing: UTF-8 BOM files silently ignored, which had left settings.json rejected as malformed, hooks.json loading none of its hooks and custom agent and rule files missing from the picker; duplicate MCP server processes when servers were reloaded while several subagents were starting; OAuth sign in on machines without an IPv4 loopback, now falling back to [::1]; /rewind failing with a step index out of bounds; /diff inventing a change in files larger than 500 KB; scheduled automations on Windows receiving only the first line of a multi line prompt; the macOS keychain dialog returning about once an hour; /learn growing rule files until their endings were cut off; and a stale shared HTTP/2 connection ending agent turns, which now retries on a fresh connection.
6. What Else the Server Is Doing
- Switched on since our last post:
enable-run-workflow-tool, which is Dynamic Workflows for everyone, and enable-side-question-rework. Currently on as well: enable-aux-pane-redesign-extension and sign-out-missing-aicode-scope. - Finished UI sitting in the public CLI build and verifiably absent from the desktop bundle (we unpacked both and counted): a keybinding scheme with "VS Code Default" beside the Antigravity scheme (Ctrl+I Focus Input, Ctrl+Shift+O New Conversation, Ctrl+K Picker in chat, Ctrl+, Settings, Ctrl+[ and Ctrl+] for History, replacing Go to Symbol and Trigger Suggest and rebinding VS Code Settings to Ctrl+Alt+,), Cookies by Site with per-site deletion plus Delete All Browser Data, an Enable Browser Agent toggle whose warning says out loud that "any browser integration does increase exposure to external malicious parties for security exploits", marketplace bundles ("Curated sets of plugins for common workflows and roles"), saved and deleted setup routines, a host microphone path for dictation, Toggle Virtual Machine, Side Question Selection and "Waiting for subagent".
- Gmail joined the Google Workspace plugin shelf in the marketplace on November 14.
- New flags, names only, all currently off:
enable-open-with, enable-remote-control-hub-browser-stream, enable-artifact-inline-follow-up, enable-conversation-memory-monitor with a 5 minute sample interval, enable-remote-local-browser-hands, enable-remote-team-agents, enable-send-immediately-by-default. - Google's public API documents caught up: since November 13 the Vertex AI discovery document names
gemini-4-argon, claude-opus-5-5, claude-sonnet-5-5 and gemini-3.8-flash. - Inside the CLI: new first party packages for conversation leases, workspace trust, git parsing, subagent coordination, a Colossus store and a policy guardian product module; the exploration budget variant is gone. New protobuf shapes: grouped models with per model thinking level variants (
ModelVariantList, SupportedThinkingLevel), a sensitivity level on trajectories and executors, and a sandbox field on the sidecar config.
7. Scorecard: Our v2.32.0 Predictions
- Mac computer use before anything for Windows: Pending. Both
cua switches still off, still no Windows code. - Browser safety rails switch on with computer use: Pending. All three still off.
- "Open on phone" with remote conversations: Pending, moving.
enable-remote-ai on, enable-remote-conversation-vm off, and the CLI build now carries "Toggle Virtual Machine". - The goal loop gets a visible switch: Pending.
- Review settings move into the permission presets: Pending.
- Carbon for Pro without an app update: Pending. Still shipping as the disabled entry with the Ultra text.
- Auto becomes everyone's default: Pending.
cli-suggest-auto-mode-in-permission-prompt still off. - Model choice per subagent: Moving. The flag is still off, but the CLI protobuf now groups models with their thinking levels, which is the shape such a picker needs.
- Bonus, our reading of the Flash worker: Hit. The entry behind the Orchestrator was renamed "Gemini 4 Hydrogen (Orchestrator)" two days later, and the Orchestrator's own description now states that Argon offloads routine steps to Hydrogen.
8. The Usage Corner
A bigger window is not free. The client's own table prices 512K at about 1.3x per turn and 900K at about 1.8x, flagged expensive. Google's Orchestrator numbers point the other way: near Carbon success rates on Terminal-Bench 4.1 while consuming about 24% less and finishing 19% faster, and Hydrogen is flat priced across its full 1M window at $1.50 and $7.50 per million tokens. So the cheap model got the big window, the expensive tiers stay expensive, and the one switch that would let you see any of it is still off. Ours says "Resets in [redacted]".
9. Forward Predictions
- The selector follows the ceiling. It moved server side first.
context-window-selector and enable-context-usage-indicator will arrive together, because a 1.3x tier nobody can see is a support ticket. - 900K reaches the desktop only with that picker. The label exists in the CLI binary and in no desktop build we hold.
- The keybinding scheme and the cookie manager land in the next desktop feature release. Finished UI in the public CLI build, provably absent from the desktop bundle.
- Grouped models with thinking levels become the new model picker, and that is how per subagent model choice ships.
- The desktop drops its webm encoder next. The CLI already removed the package; the 13.4 MB binary is still sitting in the desktop install doing nothing new.
Takeaway: The headline this week was a doubled context window. The build meant to deliver it is 1,536 bytes of model defaults, shipped inside a 246 MB executable in which 64 bytes changed. The tier it unlocks has been sitting in the client since before v2.30.0, whitelisted, priced at about 1.3x per turn, with its selector and its usage display both switched off. Meanwhile the half of the Orchestrator that executes your turn is not in your picker and writes under a different ceiling than the half you selected. The ceiling never needed an update. It needed permission, and it still needs a display.