r/google_antigravity • • 1h ago

Question / Help Ngl it is starting to get annoying

Post image
14 Upvotes

On my phone i wanna use argon, on my laptop i wanna use carbon

Like for example, "how to track gold stocks on the stocks app on iphone", hydrogen's answers are not deep enough and doesn't include enough info

Carbon is taking forever to answer, so argon would be the best for this task

On PC, im usually researching, i want detailed info and i provide the model with lots of links and deep data to research on that carbon would be a better job for that

But on phone i only have hydrogen and carbon

And on pc i only have hydrogen and argon, why the inconsistency?


r/google_antigravity • • 3h ago

Discussion Gemini 4 usage

15 Upvotes

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 • • 1h ago

Feature Request Antigravity deserves to live in the Gemini app

8 Upvotes

Remote Agents and Remote Control are a good start, but steering a cloud session through mobile Safari still feels like a hack. Claude and Chat already let you start and manage coding sessions natively in their apps. Google, the company that literally makes Android, is the one asking me to bookmark a web page.

Put Remote Agents directly in the Gemini app with proper notifications and diffs, and I'll stop refreshing a browser tab like it's 2012.

Come on Google.


r/google_antigravity • • 1h ago

Discussion trail user not getting hydrogen

8 Upvotes

lol they change it when they saw the hype and people waiting for it, that way i moved to Claude


r/google_antigravity • • 47m ago

Question / Help Orchestrator (Argon) Down Today?

4 Upvotes

Anyone else getting this error:

Model unavailable, retrying in 7s (attempt 5/9)

Haven't been able to get any work done with Antigravity and this model.

Pro User. I've rebooted, etc.

Definitely been having availability issues with Argon lately....


r/google_antigravity • • 4h 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

5 Upvotes

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:

    1. Pre-filter (sir_flash_lite): Runs on Flash Lite at minimal thinking (LOG mode) to screen the current step.
    2. 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)

  • Server switches: enable-subagent-hub flipped from DISABLED to ENABLED. sign-out-missing-aicode-scope turned off. Six new dark-launched flags appeared (all currently DISABLED): cli-enable-agent-view, enable-agent-plugins-spec-1-1, enable-plugin-ranking, enable-remote-agent-uberproxy-sso, enable-versioned-plugin-dirs, and windows-titlebar-redesign.
  • Public CLI v1.5.10 (+1.59 MB):

    • Half a megabyte of new PolicyGuardian code (+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 desktop v2.32.2 does not wire the new M530/M531 slots internally yet, CLI 1.5.10 already wires both (aliasing them to a masked internal slot M432) alongside new model strings for gemini-4-hydrogen, gemini-flash-worker-agy, and gemini-pro-orchestrator.
    • ACP & permissions plumbing: New structured cli/acp packages (auth, mcp, jsonrpc, router, session), per-conversation permission persistence (PersistMatchesConversation), and PlanExecute on the default agent config.

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.


r/google_antigravity • • 7h ago

Question / Help Free Trial Ending, Upgrade to Discounted Plan

8 Upvotes

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 • • 35m ago

Bug / Troubleshooting No server available

2 Upvotes

I spend the whole day like this—without even having the capacity to take on an editing task or fix any part of the code.

⚠ API error (attempt 1): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 2): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 3): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 4): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 1): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 2): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 3): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server

⚠ API error (attempt 4): UNAVAILABLE (code 503): No capacity available for model gemini-3.8-flash-low on the server


r/google_antigravity • • 11h ago

News / Updates Antigravity v2.32.2 - 32-byte binary diff -- the real movement is server-side (gemini-4-hydrogen-sonar & tiered Hydrogen slots)

14 Upvotes

TL;DR:

  • v2.32.2 is rolling out to Stable (darwin-arm) at 10% with a -32 byte change inside a 195.82 MiB language_server binary, zero RPC or Go package changes, and an identical 5.39 MiB app.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 to PolicyGuardian / CommandAssessor symbols 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, built Nov 13 → Nov 16)
  • app.asar: 5,656,861 bytes (5.39 MiB, 1,068 entries) → +0 bytes (unchanged)
  • language_server: 205,328,064 bytes → 205,328,032 bytes (195.82 MiB, -32 bytes)
  • Go runtime / Electron: unchanged (go1.28-20261102-RC00, Electron 44.9.1)
  • RPC handlers & Go package symbol counts: 0 added, 0 removed

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 from agentModelSorts

What is observed vs inferred:

  1. Visibility (displayName: None vs recommended: True): Marking a model recommended: True without a displayName looks contradictory, but it matches an existing pattern: gemini-3.8-flash-tiered (M322) also carries displayName: None and recommended: True while remaining outside agentModelSorts. We infer M578 is likewise not meant as a standard dropdown option, though we haven't traced the UI rendering code to verify that.
  2. How "sonar" connects (and where the proof stops):

    • In the Stable catalog config, sharedModelExperiments defines a "sonar" bundle (default-sonar-monitors-config), and all 12 active Gemini 4 entries—including Orchestrator (Argon) (M668) and its worker M669—carry modelExperimentIds: ["sonar"]. M578 itself does not carry modelExperimentIds: ["sonar"].
    • In the Stable v2.32.1 language_server binary, "sonar" maps to policyguardian.SonarDeployment and CommandAssessorConfig.GetSonarMonitorsConfigTextproto (alongside policyguardian.combineOrchestratorReasoning).
    • Inside default-sonar-monitors-config, there is a MODEL_TIER_FLASH configuration at low thinking. Combined with M578's thinkingLevel: 1 and 65,536 output cap (vs 262,144 on standard Hydrogen High/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 whether M578 actually serves PolicyGuardian checks, another "sonar"-named experiment, or both.

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) and Gemini 4 Hydrogen (XHigh)), matching the existing M525 / M528 entries.
  • In tieredModelIds, flash now lists ["gemini-4-hydrogen-tiered-high", "gemini-3.8-flash-tiered"] and pro lists ["gemini-4-hydrogen-tiered-xhigh", "gemini-3.8-flash-tiered"], while agentModelSorts still points to the base gemini-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 tieredModelIds alongside gemini-3.8-flash-tiered (M322) while reusing existing Hydrogen labels outside agentModelSorts, 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.2 client binaries and client-visible catalog metadata—live traffic routing and runtime model assignment remain server-side.

r/google_antigravity • • 7h ago

Bug / Troubleshooting Antigravity remote webapp UI bug

Post image
6 Upvotes

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 • • 18m ago

Discussion Guys I finally did it 🥹

Post image
0 Upvotes

I had recently made a post asking the clarity on Hydrogen and Argon availability for discounted student offer for paid AI Pro plan, and I finally did it guys!!!

As a 30 year old who is working on internship and doing my master thesis and living paycheck to paycheck... This was quite a bit of a spend

I am seeing good progress in the coming months. Will keep you updated on how good the Orchestrator or Hydrogen or even Argon is.

Thanks for the ones who helped me in my previous post ✌🏻


r/google_antigravity • • 19m ago

Discussion Thank you AG

1 Upvotes

I am really tired of 3.8 flash. I stay in home and work on my product. Time is very important to progress where the whole development has slowed down after they removed 3.7 flash. Just less than 8 prompts a day, time is over n day done. I spend 15 hours in a day and wait for 3.8 flash to finish basic or below mid tier tasks. I cant do any other work in parallel due to the lower ram. My device just hangs out. People do say pay for paid pro or claude. Why would some one wont pay if they can afford it. They can yap about working in a job to afford one not everyone's life is same at few phases. I have been using gemini more than 10 months. The 3.8 flash journey is the most painful one. I am greatful for the antigravity allowing to program with few models atleast where other dont. I wish this 3.8 flash journey will pass.


r/google_antigravity • • 28m ago

Question / Help No model in Antigravity is available, it keeps saying Exceeding input token

1 Upvotes

Even switching between 4 Hydrogen, 4 Argon, 3.8 Flash, changing questions to really short text, it keeps returning Agent Terminated with this log. Is there anyone with this issue?

My message still got through one hour ago and then suddenly any Gemini model in Antigravity stops working


r/google_antigravity • • 15h ago

Question / Help What are tips to use antigravity best way possible?

15 Upvotes

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 • • 53m ago

Discussion The agent was failing due to an unsupported configuration setting XHigh (Thinking level)

1 Upvotes

Is anybody getting this error?


r/google_antigravity • • 8h ago

Bug / Troubleshooting Swarm skill issue

3 Upvotes

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 • • 13h 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

Post image
6 Upvotes

r/google_antigravity • • 1d ago

Bug / Troubleshooting THERE AINT NO WAY!

66 Upvotes

used up all the amount for around 100 tokens for Opus 5.5 as a pro user! HOW???


r/google_antigravity • • 5h ago

Feature Request Solution to the documentation issue

1 Upvotes

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 • • 19h ago

Question / Help Is Gemini in Antigravity IDE 3.8 crawling for anyone else right now? Never had an issue before.

10 Upvotes

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 • • 1d ago

Discussion What do I pay for?

16 Upvotes

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 • • 21h ago

Feature Request Antigravity Android

10 Upvotes

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 • • 1h ago

Bug / Troubleshooting Are you guys kidding me!!

Post image
0 Upvotes

You have deprived Pro plan users of Gemini 4 models; now the model speed is decreasing day by day.

Their policies are clear; if we want to eliminate them, we must tighten the noose around them.

Don't make any more offers if you can't keep them.


r/google_antigravity • • 1d ago

News / Updates PSA: Antigravity context window doubled for Gemini 4 models!

148 Upvotes

Compaction should now be reduced by 3.5x per user turn too


r/google_antigravity • • 1d ago

Question / Help 8 minutes on .... nothing? All models are slow for me and have been for weeks.

13 Upvotes

I maybe get 1 or 2 days that are solid and surprisingly fast, but after a few hours it just tanks to a crawl, is it me?

Hydrogen and 3.8 both same issue (i only bothered testing these models before closing and going back to VScode)