💡 [REVEALED] The Root Cause Behind Disappearing Credits [0] (Policy Expiration + Sync Bug)

[Aditya_Pagare]

ALERT ;

Hey everyone,
I was scrolling through forum and find out some users aren’t updated about the POLICY CHANGE AND THE INTERNAL BUG !!

Here is the exact technical breakdown of what is happening to our Ultra and Pro accounts:

1. The June 18th Policy Purge (Legacy & Promo Credits)

In late May, Google quietly restructured how subscriptions handle AI overages. They removed bundled “monthly AI credits” from baseline plans, shifting instead to a “compute-based model quota.”

• The Hard Deadline: Any promotional credits, rolled-over balances, or legacy credits were assigned a hard expiration date of June 18, 2026.

• The Result: Once midnight hit, the system automatically wiped all unspent legacy credit balances to 0 across the entire Google developer ecosystem.

2. The IDE “Ghost Consumption” Bug

For those seeing credits vanish after the 18th while away from your desks, the Antigravity IDE is suffering from a massive background synchronization flaw:

• Silent Indexing: When left open or minimized, the IDE continues executing heavy background tasks (repository semantic indexing, codebase embeddings, and agentic planning cycles).

• Delayed Ledger Sync: The IDE extension panel delays syncing remaining quota logs. The credit burn happens silently while you work, but the visual deduction lags by hours—making it look like a sudden drop to zero when you return.

---

How to Audit Your Account and Stop the Bleed

Step 1: Check the Official Cloud Ledger

Do not rely on the IDE extension display. Check your absolute truth ledger on the web:

1. Go directly to your Google One AI Credits Activity Page.

2. Look closely at the transaction line items.

3. If it says "Expired,"it was wiped by the June 18th policy. If it shows an"Activity UUID," the IDE silently burned them on background processes.

Step 2: Fix Your Local IDE Settings Immediatey

If you have paid top-up credits you want to protect, change these settings to stop the background drain:

• Add an Ignore File: Create an .antigravityignore file in your root project directory. Add your heavy folders (like node_modules, dist, or build assets) so the AI agent stops constantly scanning them.

• Turn Off Fallback Billing: Run /config or open settings in your IDE terminal. Toggle Use G1 Credits to OFF. This stops the IDE from using your paid wallet as a fallback buffer when your standard compute quota locks up.

• Hard Close the Editor: Do not just minimize the application. Use Cmd + Q (Mac) or File > Exit (Windows) to fully kill the background daemon processes.

If your web ledger shows a paid top-up vanished without any activity logs, file a ticket through the Google One Support Portal for a manual database restoration. The team here cannot fix backend sync errors on individual accounts.