Weekly Codex limit exhausted immediately after purchasing Plus; usage attribution is unclear

Codex App version

Codex Desktop build unavailable from the About dialog; codex-cli 0.144.4 is installed locally.

Subscription

ChatGPT Plus (€23/month) with purchased flexible-usage credits.

Platform

Darwin 25.5.0 arm64 (Apple Silicon)

What issue are you seeing?

I purchased or reactivated ChatGPT Plus, but the Codex desktop app immediately showed the weekly limit as fully exhausted.

The official Usage & billing page currently shows:

• Plan: Plus (€23/month)
• Weekly usage: 0% left
• Reset date: 25 July 2026 (about 6d 8h remaining when captured)
• Rate-limit resets: none available
• Current purchased-credit balance: €187.68

A third-party local usage display (OpenUsage/CodexBar) simultaneously reports Limit reached and estimates Extra Usage at $188.12 / 4.7K credits. Earlier during the same day it displayed very large aggregate estimates (about 449.9M tokens today, 277.7M yesterday, and 1.9B over 30 days), but the official Codex UI does not provide enough per-session attribution to reconcile those values or explain why a newly purchased Plus weekly allowance was already at zero.

At the time the limit appeared, no visible task was running that seemed sufficient to explain a complete new weekly allowance being consumed. I need to understand whether this is stale quota state, account/plan entitlement drift, a background agent loop, duplicated subagent accounting, or expected billing behavior.

I am not claiming that the third-party dollar/token estimates are authoritative. The official facts are the Plus plan, 0% weekly remaining, 25 July reset, no reset available, and €187.68 credit balance.

Steps to reproduce

1. Purchase or reactivate ChatGPT Plus.
2. Open Codex Desktop and use a repository project with one long-lived orchestration thread and a small number of implementation subthreads/worktrees.
3. Open Codex Settings → Usage & billing.
4. Observe that Weekly usage reports 0% left / Limit reached immediately after the plan purchase, with the reset almost a full week away.
5. Observe that no per-thread/session/token breakdown is available to explain the exhaustion.

Affected orchestration session ID: 019f7223-6394-7ae3-ba57-47110d24ff0f

Captured: 18 July 2026, Europe/Paris.

I can provide private account and billing identifiers to OpenAI Support, but I am intentionally not posting them publicly.

Expected behavior

A newly purchased Plus entitlement should either provide the documented included Codex allowance or clearly explain why the allowance is already exhausted. The Usage page should show auditable attribution by session, model, and time window; distinguish included usage from purchased-credit usage; and identify any background or subagent consumption. If the quota state is stale or attached to a previous entitlement period, it should refresh automatically.

Additional information

Potentially related issues:

• #33276 — background loop drained weekly limit
• #31696 — alternating quota states
• #30349 — Plus account quota mismatch

This report differs because the official billing page itself shows the newly purchased Plus plan and 0% weekly remaining at the same time.

I have three screenshots available: the Codex limit card, the official Usage & billing page, and the draft public post describing the immediate reset/limit problem.

<img width="926" height="795" alt="Image" src="https://github.com/user-attachments/assets/15ca55f9-0bc7-4bc6-a464-ed146eb6237d" />

<img width="1440" height="1032" alt="Image" src="https://github.com/user-attachments/assets/f3b0149c-7a4d-4d4c-9efb-905dd69d8987" />