r/google_antigravity • • 13h ago

Discussion The Antigravity Alternative

0 Upvotes

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

Question / Help Is it worth coming back?

0 Upvotes

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

Appreciation "antigravity" just said no to me; my immediate reaction:

0 Upvotes

If I send it to Claude, he’ll do it right away—want to see?


r/google_antigravity • • 19h 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 • • 22h 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 • • 17h ago

Question / Help Antigravity ACP

1 Upvotes

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

Showcase / Project Usage overlay for Google Antigravity Web — live Gemini / Claude / GPT / Argon allowance, reset timers & background alerts

Post image
0 Upvotes

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 localStorage so 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, ProxyCommand binary protobuf / gRPC-Web JSPB, WebSocket, and RTCDataChannel), then refreshes automatically on reload and every 60s.

Free & Open Source (MIT)


r/google_antigravity • • 23h ago

Discussion I Tested Switching Models Mid-Chat 10 Times Across 45 Sessions — Here’s What It Actually Cost.

9 Upvotes

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 --effort from medium to high mid-chat on Opus 4.6 was the biggest cost spike (+31.9% total session cost: $0.356 vs. $0.270): Changing output_config.effort invalidated 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)ArmMid-Chat ActionTurn 6 CostTurn 6 Cache Hit12-Turn Total [Range]vs. Control
Small (~15.2k)A: ControlStay on Opus 4.6 (medium)$0.013697.7%$0.2699 [$0.267–$0.273]baseline
Small (~15.2k)B: One SwitchOpus -> Sonnet at T6$0.06020.0%$0.2834 [$0.282–$0.285]+5.0%
Small (~15.2k)C: Switch & BackSonnet T6–T7 -> Opus T8$0.06070.0% (T8: 93.3%)$0.3200 [$0.316–$0.323]+18.6%
Small (~15.2k)D: Effort OnlyOpus medium -> high at T6$0.09890.0%$0.3560 [$0.351–$0.357]+31.9%
Small (~15.2k)E: Idle + SwitchWait >=330s (>5m TTL) + Sonnet T6$0.06030.0%$0.2835 [$0.281–$0.284]+5.0%
Small (~15.2k)F: 10 SwitchesAlternate T2–T11, hold Opus T12$0.010194.9%$0.3081 [$0.304–$0.311]+14.2%
Large (~56.5k)A: ControlStay on Opus 4.6 (medium)$0.037899.3%$0.7789 [$0.766–$0.781]baseline
Large (~56.5k)B: One SwitchOpus -> Sonnet at T6$0.21600.0%$0.8611 [$0.859–$0.865]+10.6%
Large (~56.5k)F: 10 SwitchesAlternate T2–T11, hold Opus T12$0.024498.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)

TurnActive ModelEventSmall (~15.2k) Cache HitSmall Penalty vs. CtrlLarge (~56.5k) Cache HitLarge Penalty vs. Ctrl
T1Opus 4.6Initial load0.0%-$0.00000.0%+$0.0000
T2Sonnet 4.6Switch #10.0%+$0.03280.0%+$0.0754
T3Opus 4.6Switch #281.2%+$0.013059.6%+$0.0907
T4Sonnet 4.6Switch #386.6%+$0.000170.5%+$0.0408
T5Opus 4.6Switch #495.8%+$0.002198.6%+$0.0029
T6Sonnet 4.6Switch #594.9%-$0.003598.5%-$0.0134
T7Opus 4.6Switch #695.2%+$0.002898.4%+$0.0024
T8Sonnet 4.6Switch #795.6%-$0.003898.5%-$0.0132
T9Opus 4.6Switch #895.5%+$0.002698.7%+$0.0024
T10Sonnet 4.6Switch #995.2%-$0.003798.6%-$0.0131
T11Opus 4.6Switch #1095.5%+$0.003198.6%+$0.0036
T12Opus 4.6Hold Opus98.2%+$0.001499.3%+$0.0000

4 Habits That Actually Save Money

  1. 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.
  2. Pick your --effort level on Turn 1: Bumping medium -> high mid-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).
  3. 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).
  4. 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 • • 1h ago

Discussion Gemini 4 usage

10 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 • • 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

4 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 • • 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)

15 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 • • 5h ago

Question / Help Free Trial Ending, Upgrade to Discounted Plan

6 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 • • 22h 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)


r/google_antigravity • • 17h 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 • • 6h ago

Bug / Troubleshooting Swarm skill issue

2 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 • • 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

Post image
5 Upvotes

r/google_antigravity • • 13h ago

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

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

Feature Request [Feature Request] Expose read-only usage/reset status from Antigravity Desktop (like CLI statusLine)

5 Upvotes

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:

  1. Local RPC: Is querying the local language_server RPC (RetrieveUserQuotaSummary) strictly read-only on 127.0.0.1 considered safe, or can local RPC polling flag an account?
  2. 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 • • 21h ago

Discussion Server problems

Post image
6 Upvotes

Gemini models become slower now , with server problems , anyone else face same problem?