Claude quota issue and Gemini sometimes are terrible

I just completed a three-day waiting period after exhausting my weekly Claude quota, expecting a full reset today. Instead, the system is now telling me I must wait until February 3rd.

I am currently in the middle of a critical partial refactor. Over the past few days, I was forced to use Gemini, but I no longer trust it with my codebase for several reasons:

  • Destructive Actions: It has previously wiped my entire codebase.

  • Ignoring Instructions: It consistently ignores lint warnings and violates the “Root Cause First” principle I’ve explicitly documented in my gemini.md file.

  • Technical Debt: In just a few days of using Gemini, my project has accumulated over 1,600 static analysis issues.

  • Unwanted Scope Creep: It added Web support that I never requested.

  • Obscured Logic: It uses “clever” workarounds to mask issues rather than solving them, leading to business logic bugs that are now nearly impossible to trace.

I understand the high cost of providing Claude models and that I may have been inefficient with my tokens previously. However, I don’t understand how I can be hit with a consecutive weekly limit immediately after the first one expired.

I primarily use the Antigravity IDE and the Gemini web app. I have used the Gemini-cli a few times for a “Mini Program,” but I have never used reverse proxies or account switching. My project is now completely stalled because I cannot safely proceed with Gemini and have no Claude access.

Can someone explain why the quota didn’t reset as expected?

Please read here: