When explicitly setting the active model to Gemini 4 Argon (/model gemini-4-argon), prompt executions appear to route through or deduct usage from the standard Gemini model quota pool rather than the dedicated Argon weekly quota pool.
The dedicated Argon weekly limit remains completely untouched at 100%, while the standard Gemini quota drains significantly faster than normal.
Environment / Setup
- OS:
Windows WSL - CLI Version:
1.5.0 - Account Tier:
Google AI Pro
Steps to Reproduce
- Launch
agyin any working repository. - Select or switch to Argon via
/model(e.g.,gemini-4-argon/gemini-4-argon-medium). - Verify the model using
/btw "What model are you?"(it correctly reports Argon). - Run several regular agentic development tasks / prompts.
- Check quota status via
/usage.
Expected Behavior
- Prompt usage while on Argon should consume and decrease the dedicated Gemini 4 Argon Weekly Limit.
- Standard Gemini quotas (e.g., 5-hour / Flash baseline) should not be impacted or drained by Argon prompts.
Observed Behavior
- Argon Weekly Limit: Remains completely frozen at 100%.
- Standard Gemini Quota: Depletes at an accelerated rate, rapidly exhausting the general session/window limits.
- Model Identity: Running
/btw "What model are you?"returns that it is Argon, indicating the session metadata or system prompt recognizes Argon, but billing/token routing at the backend or proxy level appears misrouted to the standard Gemini quota pool.