Skip to content

google-antigravity CCA client never sends G1/Ultra paidTier (agy does) → false 429 RESOURCE_EXHAUSTED #11963

Description

@AgileInnov8tor

Summary

google-antigravity in 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:

Cloud Code Assist API error (429): {
  "error": {
    "code": 429,
    "message": "Resource has been exhausted (e.g. check quota).",
    "status": "RESOURCE_EXHAUSTED"
  }
}

omp usage still 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

  • OMP: 18.1.19 (@oh-my-pi/pi-coding-agent)
  • Host: Linux ARM64
  • Provider: google-antigravity / API google-gemini-cli
  • Model: google-antigravity/gemini-3.8-flash (requestModelId: gemini-3.8-flash-low)
  • Contrast client: official agy 1.2.2 (antigravity-cli)

Contrast that isolates the bug

Official agy 1.2.2 OMP google-antigravity
Same Google Antigravity OAuth / Ultra yes yes
Wire models gemini-3.8-flash-low/medium/high same (requestModelId: gemini-3.8-flash-low)
CCA yes https://daily-cloudcode-pa.googleapis.com
Result works 429 on first request, 0 tokens
G1/Ultra opt-in ~/.gemini/antigravity-cli/settings.json → useG1Credits: true no useG1Credits / paidTier / enabledCreditTypes anywhere in @oh-my-pi

agy binary strings (CCA proto):

  • paid_tier / paidTier (LoadCodeAssistResponse.GetPaidTier)
  • credit_type / enabled_credit_types
  • GetUseG1Credits / SetUseG1Credits / RefreshG1Credits
  • json:"useG1Credits,omitempty"

OMP catalog UA (Linux host, still hardcoded darwin):

antigravity/hub/2.8.0 (aidev_client; os_type=darwin; arch=arm64; cl=963137146)

from packages / @oh-my-pi/pi-catalog getAntigravityUserAgent() (PI_AI_ANTIGRAVITY_OS default "darwin", version from macOS arm64 hub manifest). Comment in getGeminiCliUserAgent even 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 of useG1Credits: 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-break gemini-3.8-flash in model-health.json even though the dashboard bar is ~1%.

Ask

  1. Emit paidTier / enabledCreditTypes (or the current CCA equivalent) on google-antigravity streams, matching agy.
  2. Do not treat bare RESOURCE_EXHAUSTED as account Ultra exhaustion when usage bars are near-empty.
  3. Stop defaulting Antigravity UA os_type=darwin on Linux.

Happy to attach redacted session JSONL (stopReason: error, errorStatus: 429, usage: 0) if useful.

Activity

  1. pasden-project commented on Sep 13, 2026

    @pasden-project

    same problem

  2. szavadsky commented on Sep 13, 2026

    @szavadsky
    Contributor

    @roboomp duplicate of what? is it fixed? in what PR?

  3. roboomp commented on Sep 13, 2026

    @roboomp
    Collaborator

    Duplicate of #11689 — the origin issue for the google-antigravity false 429 RESOURCE_EXHAUSTED cluster on Gemini 3.8 Flash (same symptom as #11699, #11704, #11794, #11809, #11850, #11883).

    Not fixed yet. No merged commit on main addresses 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: paidTier is already read from loadCodeAssist (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.

  4. negoro26 commented on Sep 13, 2026

    @negoro26

    same problem boss, i think google closed that api to circumvent this

  5. muwat0 commented on Sep 13, 2026

    @muwat0

    Nobody talks about this because nobody uses Gemini

  6. aleqcodes commented on Sep 13, 2026

    @aleqcodes

    Still waiting for a fix, or google close the door?

  7. roboomp commented on Sep 13, 2026

    @roboomp
    Collaborator

    Still waiting on a fix here. There is no evidence Google closed the API—the report's control case says official agy works with the same account and endpoint. Candidate fixes #11742, #11849, #11884, and #11918 remain open; none has merged into main yet.

  8. SuperUserA commented on Sep 13, 2026

    @SuperUserA

    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)

  9. danilouchoa commented on Sep 16, 2026

    @danilouchoa
    Contributor

    Triage 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 agy CLI sends, producing false 429 RESOURCE_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 10fb0ac325

    Where it lives in code

    Path Role
    packages/coding-agent/src/prompts/system/system-prompt.md prompt 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 the v18.2.1 tag: the prompt now opens with <conventions> (see system-prompt.md lines 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.1 or newer? If it still reproduces, please comment with the output of omp --version plus details, and the issue stays open for investigation. If confirmed (or after maintainer review), it can be closed as completed.

    cc @can1357 @roboomp

    Automated post-release triage sweep. Analysis is grounded in the v18.2.1 tree; nothing was changed beyond this comment.

  10. AgileInnov8tor commented on Sep 19, 2026

    @AgileInnov8tor
    ContributorAuthor

    @danilouchoa its resolved ty :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions