Bug Report: Antigravity IDE Quota Tracking Frozen at 0% with Ghost Credit Balance (50 Credits)

Hello Antigravity Team,

I am a student software engineer currently using the Antigravity IDE for internal product building and project development. While working in the IDE today, I noticed a severe backend synchronization failure regarding the quota management and model billing logic.

While I see many developers on the forum reporting accidental 7-day cooldown locks, my account has experienced the exact opposite edge case: a completely open authorization loop.

The Issue

My workspace session has entered a state where model usage tracking is completely frozen at 0% across all models (including Claude and Gemini). Furthermore, my account interface displays a fixed baseline of exactly 50 AI credits, despite the fact that I have never purchased any credits. Viewing the credits page on the browser confirms that there are no transactions history.

Behavior Observed

  • Main IDE Workspace Only: This behavior occurs strictly inside the main Antigravity IDE workspace. The companion vibe coding tool does not seem to share this specific state.

  • Unmetered Processing: When issuing multi-file prompts, indexing directories, or requesting heavy code-generation steps, the 50-credit balance does not decrement, and the usage meter remains at 0%.

  • No Enforced Cooldowns: The system completely fails to process standard rate-limiting thresholds or trigger required usage locks.

  • Zero Error Logs: The client runs completely smoothly. No console errors, connection dropouts, or authorization warnings are thrown during these sessions.

Steps where this occurred:

  1. Opened my current development directory inside the Antigravity IDE.

  2. Interacted with both Gemini and Claude models for multi-file code editing.

  3. Observed that the credit baseline (50) and the tracking percentage (0%) remained permanently static despite ongoing compute effort.

I have stopped prompting the models for my projects to avoid consuming unmetered server resources (for ethical and legal reasons), but it appears the backend token-counting mechanism for specific user sessions is completely desynced. I have attached an image of prompting Claude Opus 4.6 (on 12 June 2026) showing that credits were used, but the account balance wasn’t deducted. One thing to note is that the built-in ‘provide feedback’ feature in the Antigravity IDE doesn’t work, showing a generic ‘an error occured’ message.

Let me know if there are specific client logs or session IDs I can securely provide to help your team pin down this billing/quota loop.

Best regards, Abdurrahman Zawia

Title: Bug Report: New Account Initialization Triggering Immediate 7-Day Quota Lockout on First Login

Product: Google Antigravity IDE (Public Preview)

Description:

I launched the Antigravity IDE for the very first time today. Immediately upon my first login and profile sync, the backend model quota management system locked my account out, completely emptying the baseline tracking meters and triggering an erroneous 7-day cooldown after just a single prompt was written and executed.

Behavior Observed / Steps to Reproduce:

  1. Installed and opened the Antigravity IDE for the first time.

  2. Completed the standard initial authentication handshake with my Google account.

  3. Navigated directly to Settings → Models to check available allocations .

  4. Observed that all Gemini models (Flash and Pro variants) are marked with yellow warning triangles, displaying a countdown text reading “Refreshes in 6 days, 15 hours”.

  5. Observed that Claude (Sonnet/Opus) and GPT-OSS models have entirely empty progress bars displaying “Refreshes in 7 days, 0 hours”.

  6. Attempted to resolve the state by clicking the UI Refresh button, signing out/signing back in, and restarting the IDE. The frozen 7-day lockout state persists entirely.

Environment Contex t:

  • OS: Windows 10/

    11 Home/ Pro

  • IDE Version: Antigravity 2.0 / Latest Public Preview br anch

  • Account Type: First-time user initialization

Attachment: