Possible overcounting of Codex weekly usage

Possible overcounting of Codex weekly usage

My weekly Codex allowance went from 0% to 100% between September 10, 2026, 17:07:59 CEST and September 11, 2026, approximately 02:00 CEST — less than nine hours.

Environment

• ChatGPT self-serve Business workspace Premium PLAN
• Codex CLI 0.154.0 on Windows
• GPT-5.6 Sol
• Standard service tier; Fast mode was not enabled
• 11 user sessions and 8 subagent sessions

Local Codex telemetry

• 306,015,436 input tokens
• 300,207,488 cached input tokens
• 733,962 output tokens
• 2,499 token-count events
• Server meter progression: 0% → 19% → 30% → 50% → 99% → 100%

At the published GPT-5.6 Sol rates, this is approximately 3,950 credits. Please audit the server-side usage ledger for this weekly window and verify:

1. Whether cached input was charged at the cached-input rate.
2. Whether concurrent sessions or subagents were double-counted.
3. Whether repeated context during internal tool loops is intentionally charged for every model invocation.
4. The exact request-level credit calculation that exhausted the weekly allowance.

My comparable workload in Claude Code using Sonnet normally exhausts its weekly allowance after approximately three days, including four or five concurrent sessions. Exhausting Codex in less than nine hours is therefore unexpectedly high.

I can provide sanitized aggregates and session IDs, but cannot share raw session transcripts because they contain confidential code and business data.

The issue names no repository files, tests, or entry points. Start by determining whether Codex CLI contains the usage-metering path or whether the reported ledger is server-side; reproduce the meter progression if possible and compare request-level accounting, cached-input treatment, and concurrent-session handling against the documented behavior.