Hi Google Antigravity Team,
I am encountering an account-specific issue in Google Antigravity.
Only the model claude-opus-4-6-thinking fails on Account B with HTTP 503 MODEL_CAPACITY_EXHAUSTED. Other models work normally on the same account. Under the same network, same device, and same Antigravity client, Account A can use claude-opus-4-6-thinking successfully.
This suggests the issue is not caused by my network, local client, or general Claude access, but may be related to account-specific model routing, backend capacity allocation, or quota state for claude-opus-4-6-thinking.
Error details:
Trajectory ID: 8f632bd1-a26d-4beb-823e-fa05a652…
TraceID: 0xb2b9254a087bc…
Model: claude-opus-4-6-thinking
Error: HTTP 503 Service Unavailable
Reason: MODEL_CAPACITY_EXHAUSTED
Message: No capacity available for model claude-opus-4-6-thinking on the server
Domain: cloudcode-pa.googleapis.com
Date: Mon, 18 May 2026 11:09:17 GMT
What I have tested:
- Same network and same device.
- Account A can use claude-opus-4-6-thinking normally.
- Account B fails only on claude-opus-4-6-thinking.
- Other models work normally on Account B.
- Restarting / switching projects does not resolve the issue.
Could you please investigate whether Account B is incorrectly routed to an unavailable capacity pool, or whether the backend state for this account needs to be reset?
Thank you.