Weekly limits dropping too quickly

[Bobushka]

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.422.71525 (2210)

What subscription do you have?

PRO

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

The weekly limit dropped by 4% in the new chat on an empty project after the first prompt "Hi" and 8k tokens used. and this is not the only case: this behavior started yesterday and my weekly limit dropped in 2 hours of normal work from 100% to 22%.

What steps can reproduce the bug?

019dd844-21c2-79c2-9567-8677bc103bee
258k
5.5 high

What is the expected behavior?

Typically, this amount of work takes up 2-3% of the weekly limit, even on a new model.

Additional information

No response

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Quotas draining like crazy: burnt 100% of my 5h limit in 10 min on Business #20153
• Repeated Codex CLI startup appears to trigger large token usage without submitted task prompts #19996
• Sending feedback from the CLI used up 6% of my 5hr limit #19989
• Codex Desktop: Enabling Memories causes disproportionate quota usage #18699
• Usage fully consumed after a single message only For 2 weeks #18696

Powered by Codex Action

[Bobushka]

It's funny that even when I'm not doing any work at all, just with the app open, the weekly limit decreases by 1% every 6 hours. Is this normal?

[Bobushka]

This is not a UX issue or misunderstanding.

This is a billing / metering failure affecting a paid PRO subscription.

Key facts:

• Empty project (no repo, no files, no agents)
• First prompt "Hi" → -4% weekly limit (~8k tokens)
• Idle drain: -1% every ~6 hours with no interaction
• Started suddenly (date: 2026/04/28)

This makes the product unusable:

• Usage decreases without user actions
• Costs are not predictable or controllable
• Remaining quota is being consumed passively

This should be treated as:

• Billing bug
• Severity: High
• Impact: Paid users losing quota without usage

Please confirm:

1. Is this expected behavior?
2. If not — is this a known incident?
3. Is usage being incorrectly metered in idle sessions?

Request:

• Escalation to engineering
• Status update or incident acknowledgment