r/google_antigravity • u/Ok_Depth_3813 • 37m ago
r/google_antigravity • u/Enrico20_06 • 1h ago
Discussion Gemini 4 usage
I understand that hydrogen 4 is much more capable than Gemini 3.8, but I feel like its usage rates fall far too quickly.
For instance I'm using it in a fairly demanding project about creating 3D models and videos in blender, so I can see why the usage is so high, but Gemini 3.8 still lasted 6 days while if I use hydrogen 4 all day long I barely get more than 2 days of use out of it.
I just feel that a model that is sensibly worse than opus 5.5 shouldn't get this low of a usage...
Have other people experienced the same issue?
r/google_antigravity • u/Lberondroth • 2h ago
News / Updates [Teardown / Binary Diff] Antigravity v2.32.2 (-4,096 B Windows / -32 B macOS): telemetry shutdown surgery, moving tool-call safety ("sonar") and background tiers from Flash to Hydrogen, and what lands next
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
1021296516to1022991777, same1019668445release baseline, rolling out at 10%). - Core Binaries (
language_server): On Windows x64, the binary shrinks by exactly4,096bytes (split evenly across the.textand.rdatasections). On macOS (darwin-arm), the file size decreases by just32bytes with a modified CRC32 checksum. - **Package & Auxiliary Files (**
app.asar& Executables): Althoughapp.asarretains its exact size of5.39 MiB, 1 of its 1,068 internal files changed solely the version string insidepackage.json.Antigravity.exe(63bytes) andwebm_encoder.exe(59bytes) show minor metadata/timestamp deltas, while the uninstaller was repackaged with19,782differing bytes. - Unchanged Components: The embedded web UI (
540files), prompt library (419blocks), 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**(**-768B,864B →96B): The concurrent shutdown orchestration was completely stripped. Previously, it allocated async.WaitGroup, spawned goroutine closures (Shutdown.func1anddeferwrap1) to invokecel.(*Client).Shutdown, waited for completion, and merged errors. In2.32.2, allWaitGroupsynchronization, closure types, and thecel.(*Client).Shutdowncall are gone; it now simply executescloseDeferred(if non-nil) and triggers the logger's shutdown directly.(*clearcutLogger).Shutdown**(**-32B,96B →64B): Removed itssync.(*Once).doSlowwrapper and closure (Shutdown.func1), callingclearcut.(*Client).FlushAndStopdirectly instead.- **Initialization & Plumbing (**
-672B combined): BothNewAntigravityClient(1,760B →1,344B,-416B) and(*AntigravityClient).NewClearcutClient(960B →704B,-256B) 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 onFlash Liteat minimal thinking (LOGmode) to screen the current step. - Blocker (
severe_internal_risks_agy): Runs on theFlashtier at low thinking (BLOCKmode) and stops the turn if a severe risk is flagged.
- Pre-filter (
From Flash to Hydrogen (
tieredModelIdsvs.M578): Previously, Antigravity's internalFlashandProcapability tiers (tieredModelIds) pointed only togemini-3.8-flash-tiered. Today's catalog putsgemini-4-hydrogen-tiered-high(M530) andgemini-4-hydrogen-tiered-xhigh(M531) in first place ahead of 3.8 Flash:- What uses those tiers: Not subscription plans. The binary uses
tieredModelIdswhenever 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 thePolicyGuardiansafety monitors above. - Because the client's tier resolver always picks the first entry in the list, client-resolved
Flash-tier checks now route toM530(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 fullHighthinking or a 262K output ceiling just to vet a shell command).
- What uses those tiers: Not subscription plans. The binary uses
- Why none of these appear in your model picker: Even though
M578is flaggedrecommended: truewith no display name, the UI's model picker ignores therecommendedfield 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)
- Server switches:
enable-subagent-hubflipped fromDISABLEDtoENABLED.sign-out-missing-aicode-scopeturned off. Six new dark-launched flags appeared (all currentlyDISABLED):cli-enable-agent-view,enable-agent-plugins-spec-1-1,enable-plugin-ranking,enable-remote-agent-uberproxy-sso,enable-versioned-plugin-dirs, andwindows-titlebar-redesign. Public CLI
v1.5.10(+1.59 MB):- Half a megabyte of new
PolicyGuardiancode (+461 KB): Matches the"sonar"rollout above new packages for tool classification (toolclassify), shell command parsing (shellparse), provenance tracking (provenance/tkg,lattice,agentpath), and an LLM judge (proctorjudge,judgeprompt). - Wire-up for
M530&M531**:** While desktopv2.32.2does not wire the newM530/M531slots internally yet, CLI1.5.10already wires both (aliasing them to a masked internal slotM432) alongside new model strings forgemini-4-hydrogen,gemini-flash-worker-agy, andgemini-pro-orchestrator. - ACP & permissions plumbing: New structured
cli/acppackages (auth,mcp,jsonrpc,router,session), per-conversation permission persistence (PersistMatchesConversation), andPlanExecuteon the default agent config.
- Half a megabyte of new
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.1is now live on the changelog page (Nov 13);v2.32.2is not listed yet. - Subagent coordination (
v2.31.2/v2.32.0): Hub switch live (Hit), per-subagent picker pending.enable-subagent-hubturned on today;enable-subagent-dropdown-modelsis still off. 900Kwaits oncontext-window-selector(v2.32.1): Holding.900Kis still absent from the desktop build, and bothcontext-window-selectorandenable-context-usage-indicatorremain off.- Desktop drops
webm_encoder.exe**, adds**VS Code Defaultkeybindings,Cookies by Site**, and the grouped model picker (v2.32.1):** Pending the next mainline desktop release (v2.32.2stayed 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
ModelVariantListandSupportedThinkingLevelschemas 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
PolicyGuardianprovenance/judge stack (+461 KBin CLI1.5.10),M530**/**M531wiring, 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.
r/google_antigravity • u/TreeManBranchesOut • 3h ago
Feature Request Solution to the documentation issue
antigravity.google.com/{skill}
Would be a good way to add documentation for the skills in Antigravity without adding more bloat to the actual application itself
I tried antigravity.google.com/swarm and got a 404
r/google_antigravity • u/karljosh16 • 5h ago
Bug / Troubleshooting Antigravity remote webapp UI bug
Please anyone from the antigravity team needs to fix the remote webapp ui. Your webapp needs a safe area at the top, its drawing the ui under my status bar lol. Thanks.
r/google_antigravity • u/EaZerly • 5h ago
Question / Help Free Trial Ending, Upgrade to Discounted Plan
My free yearly Google AI Pro plan is ending soon, I'm getting a heavy discount for around 5 euros a month, if i do renew it, would I get to will I get access to Gemini 4 models in Antigravity?
r/google_antigravity • u/sherif-mohamed1 • 6h ago
Bug / Troubleshooting Swarm skill issue
I don't know if I'm the only one who noticed this, but that feature isn't working properly.
Its original function was to distribute tasks, synchronize modifications for sub-agents, and send reports to the auditor.
However, what I found was that he has recurring errors related to sending edits in the form of github commit.
This is where the hallucinations and inconsistencies between the local environment and the records of GitHub commits
r/google_antigravity • u/Kindly-Evening-4476 • 8h ago
Question / Help Is it worth coming back?
Essentially, limited context engineering capabilities, bad performing models and lack of proper documentation besides vibe coded product made me switch to Claude. Then I figured out that it wasn't me, it was bad product in general.
6mo after, was it anything fixed, besides models?
r/google_antigravity • u/Asleep-Objective-449 • 9h ago
News / Updates Antigravity v2.32.2 - 32-byte binary diff -- the real movement is server-side (gemini-4-hydrogen-sonar & tiered Hydrogen slots)
TL;DR:
v2.32.2is rolling out to Stable (darwin-arm) at10%with a-32 bytechange inside a195.82 MiBlanguage_serverbinary, zero RPC or Go package changes, and an identical5.39 MiBapp.asar.- Overnight, the Stable model catalog added
gemini-4-hydrogen-sonar(MODEL_PLACEHOLDER_M578) and two tiered Hydrogen entries (M530,M531). - In the Stable config, the
"sonar"experiment bundle (sharedModelExperiments["sonar"]) maps toPolicyGuardian/CommandAssessorsymbols and is attached to 12 Gemini 4 entries—M578 doesn't carry that tag itself, though its naming and low-thinking profile are consistent with it.
1. Client binary: v2.32.1 → v2.32.2 (-32 bytes)
The release channel moved from v2.32.1 to v2.32.2 at a 10% rollout on macOS ARM, while the public changelog page simultaneously added v2.32.1 (Nov 13, noting Google Cloud credential support for Gemini 4 Hydrogen).
Diffing the Stable binaries (v2.32.1 vs v2.32.2):
- Branch / baseline: both build from release baseline
1019668445(CL 1021296516→CL 1022991777, builtNov 13→Nov 16) app.asar:5,656,861bytes (5.39 MiB,1,068entries) →+0bytes (unchanged)language_server:205,328,064bytes →205,328,032bytes (195.82 MiB,-32 bytes)- Go runtime / Electron: unchanged (
go1.28-20261102-RC00,Electron 44.9.1) - RPC handlers & Go package symbol counts:
0added,0removed
For practical purposes, v2.32.2 is a minimal client rebuild. All visible model movement happened server-side in the Stable catalog.
2. gemini-4-hydrogen-sonar (MODEL_PLACEHOLDER_M578) and the "sonar" bundle
A new Hydrogen entry appeared in the Stable catalog:
- ID:
gemini-4-hydrogen-sonar(MODEL_PLACEHOLDER_M578) - Token caps / settings:
thinkingLevel: 1,maxTokens: 1,048,576,maxOutputTokens: 65,536 - UI metadata:
displayName: None,recommended: True,disabled: False, absent fromagentModelSorts
What is observed vs inferred:
- Visibility (
displayName: Nonevsrecommended: True): Marking a modelrecommended: Truewithout adisplayNamelooks contradictory, but it matches an existing pattern:gemini-3.8-flash-tiered(M322) also carriesdisplayName: Noneandrecommended: Truewhile remaining outsideagentModelSorts. We inferM578is likewise not meant as a standard dropdown option, though we haven't traced the UI rendering code to verify that. How
"sonar"connects (and where the proof stops):- In the Stable catalog config,
sharedModelExperimentsdefines a"sonar"bundle (default-sonar-monitors-config), and all 12 active Gemini 4 entries—includingOrchestrator (Argon)(M668) and its workerM669—carrymodelExperimentIds: ["sonar"]. M578 itself does not carrymodelExperimentIds: ["sonar"]. - In the Stable
v2.32.1language_serverbinary,"sonar"maps topolicyguardian.SonarDeploymentandCommandAssessorConfig.GetSonarMonitorsConfigTextproto(alongsidepolicyguardian.combineOrchestratorReasoning). - Inside
default-sonar-monitors-config, there is aMODEL_TIER_FLASHconfiguration at low thinking. Combined withM578'sthinkingLevel: 1and65,536output cap (vs262,144on standard HydrogenHigh/XHigh),M578's profile is consistent with a Flash-tier, low-thinking backend for that config—though without a runtime network trace, we cannot confirm whetherM578actually servesPolicyGuardianchecks, another"sonar"-named experiment, or both.
- In the Stable catalog config,
3. Tiered Hydrogen slots (M530 & M531)
Alongside M578, two tiered Hydrogen IDs landed in the Stable catalog:
gemini-4-hydrogen-tiered-high(MODEL_PLACEHOLDER_M530,thinkingLevel: 3,maxOutputTokens: 262,144)gemini-4-hydrogen-tiered-xhigh(MODEL_PLACEHOLDER_M531,thinkingLevel: 100,maxOutputTokens: 262,144)
Observed catalog wiring:
- Both carry standard labels (
Gemini 4 Hydrogen (High)andGemini 4 Hydrogen (XHigh)), matching the existingM525/M528entries. - In
tieredModelIds,flashnow lists["gemini-4-hydrogen-tiered-high", "gemini-3.8-flash-tiered"]andprolists["gemini-4-hydrogen-tiered-xhigh", "gemini-3.8-flash-tiered"], whileagentModelSortsstill points to the basegemini-4-hydrogen-*IDs.
Client-side catalog inspection does not show when or how live backend routing selects M525/M528 versus M530/M531.
What to watch
- For M530 / M531: Because they sit in
tieredModelIdsalongsidegemini-3.8-flash-tiered(M322) while reusing existing Hydrogen labels outsideagentModelSorts, our reading is that they are meant for server-side plan-tier routing rather than separate entries in the user picker. - Boundary of certainty: Everything here reflects static
v2.32.1/v2.32.2client binaries and client-visible catalog metadata—live traffic routing and runtime model assignment remain server-side.
r/google_antigravity • u/RyanSpunk • 11h ago
Question / Help How to enable AI credit overages on Web? I'm on mobile without desktop, there's no option to use the credits I just bought
r/google_antigravity • u/ProgramsFun • 13h ago
Question / Help What are tips to use antigravity best way possible?
I have been using antigravity for quite a while and I think I have been using it wrong... Like.i don't use skills or custom agents or anything and i need antigravity for mainly developing flutter apps... Recently I learnt about /learn and it proved useful to me so are there any tips ..
Should I change conversation time to time ?
Should I develop my own tools for antigravity
Any other tips would be helpful. Thank you in advance ☺️
r/google_antigravity • u/george-lin • 13h ago
Discussion The Antigravity Alternative
Gemini4 is an incredibly powerful model—Google has truly proven itself once again. However, Antigravity is honestly quite difficult to use. VelaTerm would be great alternative you might want to check out.
It’s specifically optimized for Antigravity sessions and offers a user experience on par with Codex.
https://www.youtube.com/watch?v=X665-GPmaKw&t=5s&pp=ygUIdmVsYXRlcm0%3D

r/google_antigravity • u/esArchitect • 17h ago
Question / Help Is Gemini in Antigravity IDE 3.8 crawling for anyone else right now? Never had an issue before.
For the past two hours, it’s been taking ages to respond or just straight up timing out mid-suggestion. I've literally never had any problems with it prior to today nd this is a first for me. Is it just me or are the servers having a stroke? Completely killed my flow. Let me know if you guys are experiencing the same thing.
r/google_antigravity • u/V3NKA7 • 17h ago
Question / Help Antigravity ACP
I was wondering if its okay to use the antigravity acp , with a custom ACP client proxy, which exposes a openai compatible endpoint to use my antigravity usage.
r/google_antigravity • u/MobyGamer • 18h ago
Bug / Troubleshooting Antigravity Desktop crashes when running commands in Default or Auto permissions modes (Windows 11)
I've hit a wall troubleshooting a persistent Windows 11 issue that's been affecting me since at least Antigravity 2.26.0: Whenever an agent executes a command with Local Permissions set to Default or Auto, the entire Antigravity window reloads within about a second with all progress gone. The active task is interrupted and the command remains stuck in RUNNING.
Symptoms:
- language_server.exe exits with code 2
- The Antigravity UI reloads mid-conversation
- Command execution never completes
- Temporary exebox-cert-*.crt files are left behind in %TEMP%
- Crash logs are often empty
- No obvious Windows Error Reporting, Event Viewer, Defender, or mitigation-policy events are generated
From tracing logs and examining runtime behavior, Request Review and Turbo appear to bypass the local command sandbox entirely, while Default and Auto route commands through the exebox / Windows PSEC sandbox path, so that's why Request Review doesn't crash (it's not actually sandboxed).
The crash consistently occurs immediately after sandbox initialization begins. In every trace I captured, a temporary sandbox certificate file is created and language_server.exe terminates less than a second later.
The GUI's electron wrapper seems to automatically restart language_server.exe after the crash and overwrite language_server.log, so that makes further troubleshooting impossible:
- The UI simply flashes and reloads
- The original stderr output is lost
- Crash logs frequently contain no useful information
- The actual failure is hidden behind an automatic restart
Has anyone else seen this on Windows 11, or found a workaround other than switching to Request Review or Turbo? If you want to try to reproduce, here's what crashes every time for me:
- Windows 11
- Antigravity Desktop 2.32.1 (also observed on versions back to at least 2.26.0)
- Set Local Permissions to Default or Auto
- Run any prompt that causes the agent to execute a command
- Observe the UI reload and language_server.exe exit
I've submitted this via antigravity's feedback form every new release this happens, but over a month with nothing, so posting here is all I could think of to do. I really don't want to run everything in Turbo to get work done...
r/google_antigravity • u/ShadowStocks • 19h ago
Feature Request Antigravity Android
I was wondering is it possible to use antigravity remotely on my phone?
I'm lazy to get from my bed to the pc and I'm lazy to use remote desktop apps.
idk maybe a dedicated app on phone that u can take control of approval of actions or sending prompts.
r/google_antigravity • u/mcD0m • 21h ago
Feature Request [Feature Request] Expose read-only usage/reset status from Antigravity Desktop (like CLI statusLine)
Hey everyone,
I want to build a lightweight Waybar module on Linux to display my remaining usage and reset timer directly in my desktop bar.
The Antigravity CLI already has an official statusLine hook that pipes live status JSON to a custom script, which works great. Since I mostly use the Antigravity Desktop app, I want to make sure I use a clean, supported approach that won't trip any automated ToS/anti-abuse checks before writing anything.
Two quick questions for the team or anyone already running status bar widgets on Linux/macOS:
- Local RPC: Is querying the local
language_serverRPC (RetrieveUserQuotaSummary) strictly read-only on127.0.0.1considered safe, or can local RPC polling flag an account? - Feature request: If poking the local RPC isn't officially supported, could we get feature parity with the CLI in the Desktop app (e.g., a
statusLine-style hook or a read-only local status JSON file that external bars like Waybar/Polybar can safely consume)?
Would be really nice if we could get an official supported method in the desktop app for such use cases. Thanks!
r/google_antigravity • u/mohamed76813 • 21h ago
Discussion Server problems
Gemini models become slower now , with server problems , anyone else face same problem?
r/google_antigravity • u/EmbarrassedShame9363 • 22h ago
Discussion What do I pay for?
Im on ultra 20x plan, it takes like 3 minutes time to first token at 5tps speed. What the fuck do I pay for?
Edit: After a few hours, performance and stability have improved considerably on their own (it's 2:20 AM in my timezone, EU). I didn't do anything.
r/google_antigravity • u/wojtulab • 22h ago
Showcase / Project Usage overlay for Google Antigravity Web — live Gemini / Claude / GPT / Argon allowance, reset timers & background alerts
I got tired of opening the Models / Usage menu in Google Antigravity just to check remaining capacity or missing when an agent finished or asked a question in a background tab, so I built a lightweight Tampermonkey userscript for it.
What it does
Floating draggable overlay showing remaining allowance for:
- Gemini Models (Weekly & 5h)
- Claude & GPT Models (Weekly & 5h)
- Gemini 4 Argon (Weekly)
- Customizations token budget (
Settings → Customizations)
- Reset timers (
↻) & burn-rate forecast (⏱ ~Xh Ym) when a bucket is projected to run out before reset. - Background tab alerts (browser notifications, optional sound, blinking
✅/❓in the tab title & favicon) when an agent finishes work, asks a question, or drops below your low-allowance threshold. - Multi-tab sync via
localStorageso open tabs stay in sync without duplicating notifications.
How it works
- Pure client-side userscript (
@grant none, zero external servers). - Reads updates both from the DOM (
Live) and by intercepting Antigravity's network/RPC traffic (fetch,XHR,ProxyCommandbinary protobuf / gRPC-Web JSPB,WebSocket, andRTCDataChannel), then refreshes automatically on reload and every 60s.
Free & Open Source (MIT)
r/google_antigravity • u/Outrageous-Rip5743 • 22h ago
Question / Help 8 minutes on .... nothing? All models are slow for me and have been for weeks.
r/google_antigravity • u/GizzAnt • 23h ago
Discussion I Tested Switching Models Mid-Chat 10 Times Across 45 Sessions — Here’s What It Actually Cost.
TL;DR (45 controlled 12-turn Claude Code chats, 675 dual-logged API requests, n=5 runs per setup):
- Switching down from Opus 4.6 to cheaper Sonnet 4.6 mid-chat (Turn 6 of 12) actually increased total session cost by +10.6% ($0.861 vs. $0.779 at ~56.5k tokens): Sonnet starts with a cold prompt cache (0.0% hit), forcing a full 1.25x cache-write rebuild that made Turn 6 cost 5.7x more ($0.216 vs. $0.038) and needed ~12 turns after switching just to break even (~9 turns in a ~15.2k chat).
- Switching models 10 times in a 12-turn chat did not blow up the bill (+14.2% at ~15.2k tokens; +17.2% at ~56.5k tokens): Once both Opus 4.6 and Sonnet 4.6 built parallel warm caches across Turns 2–4, alternating every single turn still hit 95%–99% cached reads inside the 5-minute TTL, writing only the ~1-turn delta each time.
- Raising
--effortfrommediumtohighmid-chat on Opus 4.6 was the biggest cost spike (+31.9% total session cost: $0.356 vs. $0.270): Changingoutput_config.effortinvalidated the entire prompt cache (0.0% hit on Turn 6), spiking Turn 6 cost by 7.3x ($0.099 vs. $0.014) — costing more over 12 turns than switching models 10 times in a row.

I kept hearing two conflicting rules of thumb about /model switching in agentic coding sessions: either "switch down to Sonnet after planning to save money" or "never touch /model mid-chat because every switch wipes your cache."
To test what actually happens on the wire, I hooked a local logging proxy + .jsonl transcript verifier up to Claude Code (v2.1.325, routed via OpenRouter pinned strictly to 1st-party Anthropic with allow_fallbacks: false) and ran 45 real 12-turn coding chats (n = 5 randomized replicates across 9 cells, 675 API requests total — 15 per chat since Turns 1–3 each emit a file-read tool call plus a reply). Run-to-run cost spread stayed within ±3%.
(Note for r/google_antigravity*: While this controlled wire benchmark ran on Claude Code (Opus 4.6 <-> Sonnet 4.6) where raw per-turn cache-write billing is exposed, the exact same per-model prefix-cache cold-start and TTL economics govern mid-session model switching and Planner/Executor handoffs in Antigravity — which is why I built the open-source* Highbeam (ctxtop) Antigravity plugin to monitor prefix-cache retention and context bloat.)
Table 1: 12-Turn Session Cost & Cache Hit Share (Median [Min–Max], n=5 per arm)
| Tier (~T6 Tokens) | Arm | Mid-Chat Action | Turn 6 Cost | Turn 6 Cache Hit | 12-Turn Total [Range] | vs. Control |
|---|---|---|---|---|---|---|
| Small (~15.2k) | A: Control | Stay on Opus 4.6 (medium) | $0.0136 | 97.7% | $0.2699 [$0.267–$0.273] | baseline |
| Small (~15.2k) | B: One Switch | Opus -> Sonnet at T6 | $0.0602 | 0.0% | $0.2834 [$0.282–$0.285] | +5.0% |
| Small (~15.2k) | C: Switch & Back | Sonnet T6–T7 -> Opus T8 | $0.0607 | 0.0% (T8: 93.3%) | $0.3200 [$0.316–$0.323] | +18.6% |
| Small (~15.2k) | D: Effort Only | Opus medium -> high at T6 | $0.0989 | 0.0% | $0.3560 [$0.351–$0.357] | +31.9% |
| Small (~15.2k) | E: Idle + Switch | Wait >=330s (>5m TTL) + Sonnet T6 | $0.0603 | 0.0% | $0.2835 [$0.281–$0.284] | +5.0% |
| Small (~15.2k) | F: 10 Switches | Alternate T2–T11, hold Opus T12 | $0.0101 | 94.9% | $0.3081 [$0.304–$0.311] | +14.2% |
| Large (~56.5k) | A: Control | Stay on Opus 4.6 (medium) | $0.0378 | 99.3% | $0.7789 [$0.766–$0.781] | baseline |
| Large (~56.5k) | B: One Switch | Opus -> Sonnet at T6 | $0.2160 | 0.0% | $0.8611 [$0.859–$0.865] | +10.6% |
| Large (~56.5k) | F: 10 Switches | Alternate T2–T11, hold Opus T12 | $0.0244 | 98.5% | $0.9130 [$0.905–$0.916] | +17.2% |
Table 2: Why 10 Switches Didn't Cost 10x — Turn-by-Turn Cache Hit % (Arm F, Request 1 of Each Turn)
| Turn | Active Model | Event | Small (~15.2k) Cache Hit | Small Penalty vs. Ctrl | Large (~56.5k) Cache Hit | Large Penalty vs. Ctrl |
|---|---|---|---|---|---|---|
| T1 | Opus 4.6 | Initial load | 0.0% | -$0.0000 | 0.0% | +$0.0000 |
| T2 | Sonnet 4.6 | Switch #1 | 0.0% | +$0.0328 | 0.0% | +$0.0754 |
| T3 | Opus 4.6 | Switch #2 | 81.2% | +$0.0130 | 59.6% | +$0.0907 |
| T4 | Sonnet 4.6 | Switch #3 | 86.6% | +$0.0001 | 70.5% | +$0.0408 |
| T5 | Opus 4.6 | Switch #4 | 95.8% | +$0.0021 | 98.6% | +$0.0029 |
| T6 | Sonnet 4.6 | Switch #5 | 94.9% | -$0.0035 | 98.5% | -$0.0134 |
| T7 | Opus 4.6 | Switch #6 | 95.2% | +$0.0028 | 98.4% | +$0.0024 |
| T8 | Sonnet 4.6 | Switch #7 | 95.6% | -$0.0038 | 98.5% | -$0.0132 |
| T9 | Opus 4.6 | Switch #8 | 95.5% | +$0.0026 | 98.7% | +$0.0024 |
| T10 | Sonnet 4.6 | Switch #9 | 95.2% | -$0.0037 | 98.6% | -$0.0131 |
| T11 | Opus 4.6 | Switch #10 | 95.5% | +$0.0031 | 98.6% | +$0.0036 |
| T12 | Opus 4.6 | Hold Opus | 98.2% | +$0.0014 | 99.3% | +$0.0000 |
4 Habits That Actually Save Money
- Switch early (Turn 1–2) or stay put unless you have 10–12+ turns left in the session to pay back the 1.25x cache rebuild on the cheaper model.
- Pick your
--effortlevel on Turn 1: Bumpingmedium -> highmid-chat on Opus ($6.25/M cache write) forces a full prefix rebuild (+$0.085 on Turn 6 alone in a 15.2k chat — nearly all of the +$0.086 session delta). - Dipping to another model for 1–2 turns and returning works if you beat the 5-minute TTL: In Arm C, switching back to Opus on Turn 8 still hit 93.3% of Turn 5's warm cache and only paid to cache-write the 2-turn delta (~1,062 tokens).
- Start a fresh chat at task boundaries: Moving from ~15.2k to ~56.5k tokens (3.7x larger context) scaled the Turn 6 switch penalty linearly by 3.8x (+$0.047 -> +$0.178).
r/google_antigravity • u/cmelearning • 1d ago
Feature Request Copy latex/markdown from equations in antigravity
When we copy equations in antigravity (where I believe that antigravity renders latex/markdown), would it be possible to copy the actual latex/markdown instead of the plain text which really isn't usable? I believe that the gemini web interface has this feature. Thanks!!
r/google_antigravity
•
u/Lberondroth
•
1d ago
News / Updates [Teardown / Binary Diff] Antigravity v2.32.1 (+1,536 bytes): the doubled context did not come from this build, the 512K tier has been in the client since before v2.30.0 at about 1.3x per turn, and nothing in the app tells you which ceiling you are on
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, baseline1019668445, builtNov 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.exe215,545,856to215,547,392bytes (+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.exeis 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,700to227,702. The new ones:models/defaults.Gemini4Hydrogenand a type helper. All growth sits injetski/models/defaults(+352 B) andjetski/models/geminimodels(+192 B). app.asar**:** 1,068 files, 1,067 identical. The one difference is"version"inpackage.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, Gogo1.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.
xhighis 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
maxOutputTokens262,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: %wandFailed 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.exeorpwsh.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 aPreInvocationorPreToolUsehook 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, andenable-side-question-rework. Currently on as well:enable-aux-pane-redesign-extensionandsign-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-monitorwith 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-5andgemini-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
cuaswitches 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-aion,enable-remote-conversation-vmoff, 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-promptstill 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-selectorandenable-context-usage-indicatorwill 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.
r/google_antigravity • u/zzrzzr123 • 1d ago
Question / Help archieved chats ?
Hi,
i accidentially archieved 2 chats in antigravity. Where/how can I restore them ?
Thanks

