Repository navigation
google-antigravity CCA client never sends G1/Ultra paidTier (agy does) → false 429 RESOURCE_EXHAUSTED #11963
Description
Activity
- addedagentAgent runtime planning and orchestrationAgent runtime planning and orchestrationduplicateThis issue or pull request already existsThis issue or pull request already existsprovidersLLM provider-specific issuesLLM provider-specific issues
on Sep 13, 2026 same problem
Reacted by AlexNegrescu26@roboomp duplicate of what? is it fixed? in what PR?
Duplicate of #11689 — the origin issue for the
google-antigravityfalse 429RESOURCE_EXHAUSTEDcluster on Gemini 3.8 Flash (same symptom as #11699, #11704, #11794, #11809, #11850, #11883).Not fixed yet. No merged commit on
mainaddresses it, and the follow-ups (#11809, #11883) confirm it still reproduces. Candidate fixes are in review — #11742, #11849, #11884, #11918 — but none has landed. Track #11689 (or watch those PRs) for the fix.On the specific diagnosis in this report:
paidTieris already read fromloadCodeAssist(packages/ai/src/registry/oauth/google-antigravity.ts), and the darwin/arm64 User-Agent is a deliberate, documented pin (packages/catalog/CHANGELOG.md), so those two points aren't the confirmed root cause. The maintainer will pick the fix from the PRs above.same problem boss, i think google closed that api to circumvent this
Reacted by murat and Malachi SoordNobody talks about this because nobody uses Gemini
Still waiting for a fix, or google close the door?
Nobody talks about this because nobody uses Gemini
Lol maybe this is the case. Otherwise, the fix could be implemented in two hours :)
(Seeing so many pr for that but no action for some reason)Reacted by Alex MushketTriage result: already fixed in v18.2.1
Triaged in the post-release sweep: this report matches the fix that shipped in v18.2.1 (2026-09-15). Summary of the analysis:
Reported The google-antigravity CCA client never sent the G1/Ultra paidTier marker that the agyCLI sends, producing false 429RESOURCE_EXHAUSTED.Fix The flagged literal no longer leaves this client: the system-prompt block was renamed from <system-conventions>to<conventions>in v18.2.1, removing the exact byte sequence Google's gateway rule matches.Shipped in v18.2.1 — commit 10fb0ac325Where it lives in code
Path Role packages/coding-agent/src/prompts/system/system-prompt.mdprompt block now opens <conventions>(lines 1-4) instead of<system-conventions>Fix evidence
- The trigger was the literal opening tag
<system-conventions>hardcoded in the system prompt (packages/coding-agent/src/prompts/system/system-prompt.md, advisor prompt); Google Cloud Code Assist's gateway flagged exactly that sequence and answered with a false 429. - Commit
10fb0ac325("refactor(coding-agent/prompts): renamed system-conventions tags to conventions in prompts", 2026-09-14) is an ancestor of thev18.2.1tag: the prompt now opens with<conventions>(seesystem-prompt.mdlines 1-4), so the flagged literal no longer leaves this client. - If you still see a false 429 on
v18.2.1+, comment with the model and a wire capture — that would indicate a second trigger on Google's side.
@AgileInnov8tor — asking for your acceptance on this triage: can you confirm the problem is resolved for you on
v18.2.1or newer? If it still reproduces, please comment with the output ofomp --versionplus details, and the issue stays open for investigation. If confirmed (or after maintainer review), it can be closed as completed.Automated post-release triage sweep. Analysis is grounded in the v18.2.1 tree; nothing was changed beyond this comment.
- The trigger was the literal opening tag
@danilouchoa its resolved ty :)
Reacted by Danilo Uchôa
Summary
google-antigravityin OMP talks to Cloud Code Assist (daily-cloudcode-pa.googleapis.com) but never opts the request into Google One / AI Ultra credits. The official Antigravity CLI (agy) on the same login does, and Gemini 3.8 Flash works there.OMP then surfaces Google's generic:
omp usagestill shows ~1% of the Antigravity Google 5h/weekly bars. Session JSONL shows 0 input / 0 output tokens on the failing turns. This is not an empty Ultra subscription.Related (symptom cluster, different proposed causes): #11689 (closed), #11699, #11704, #11794, #11809, #11883.
Environment
@oh-my-pi/pi-coding-agent)google-antigravity/ APIgoogle-gemini-cligoogle-antigravity/gemini-3.8-flash(requestModelId:gemini-3.8-flash-low)agy1.2.2 (antigravity-cli)Contrast that isolates the bug
agy1.2.2google-antigravitygemini-3.8-flash-low/medium/highrequestModelId: gemini-3.8-flash-low)https://daily-cloudcode-pa.googleapis.com~/.gemini/antigravity-cli/settings.json→useG1Credits: trueuseG1Credits/paidTier/enabledCreditTypesanywhere in@oh-my-piagybinary strings (CCA proto):paid_tier/paidTier(LoadCodeAssistResponse.GetPaidTier)credit_type/enabled_credit_typesGetUseG1Credits/SetUseG1Credits/RefreshG1Creditsjson:"useG1Credits,omitempty"OMP catalog UA (Linux host, still hardcoded darwin):
from
packages/@oh-my-pi/pi-cataloggetAntigravityUserAgent()(PI_AI_ANTIGRAVITY_OSdefault"darwin", version from macOS arm64 hub manifest). Comment ingetGeminiCliUserAgenteven says UA is built to unlock higher rate limits — quota is client-keyed.Expected
OMP's CCA client should send the same G1/Ultra credit selection the official CLI sends (
paid_tier/enabled_credit_types/ equivalent ofuseG1Credits: true) so Antigravity Ultra is actually consumed.Actual
OMP never sends those fields. Google answers 429 RESOURCE_EXHAUSTED (generic quota string). OMP classifies it as rate-limit, falls back (here:
xai-oauth/grok-4.6), and may circuit-breakgemini-3.8-flashinmodel-health.jsoneven though the dashboard bar is ~1%.Ask
paidTier/enabledCreditTypes(or the current CCA equivalent) ongoogle-antigravitystreams, matchingagy.RESOURCE_EXHAUSTEDas account Ultra exhaustion when usage bars are near-empty.os_type=darwinon Linux.Happy to attach redacted session JSONL (
stopReason: error,errorStatus: 429,usage: 0) if useful.