Plus workspace shows 1,000 credits and 100% weekly usage remaining, but Codex and Work are blocked as out of credits #38892

Summary

My ChatGPT Plus workspace shows 1,000 credits and 100% weekly usage remaining in the Usage page, but both Codex and Work are hard-blocked by the backend as if the workspace had zero credits.

This is not just a stale warning banner: execution is blocked in both products.

Subscription

ChatGPT Plus

Environment

• macOS unified ChatGPT app
• ChatGPT web in browser
• Same account and same workspace on both surfaces
• Reproduced on August 16, 2026 (Europe/Sofia)

Because the same failure also occurs in the browser, this does not appear to be a local macOS installation/cache issue.

Usage state shown by the product

The Usage page shows:

Usage

Usage is shared across Codex, Work, Workspace Agents, and ChatGPT for Excel. It doesn’t include Chat conversations.

Weekly usage limit
100% remaining

Usage limit resets
No usage limit resets available at this time.

Credits
1,000 credits

Actual behavior

Codex is blocked with:

You’re out of Codex and Work usage
Your workspace is out of credits. Add credits to continue using Codex and Work.

Work is also blocked with:

You’re out of Work usage for now
Your workspace is out of credits. Add credits to continue using Work.

So the same workspace simultaneously reports:

• Weekly usage: 100% remaining
• Credits: 1,000
• Codex execution entitlement: 0 / blocked
• Work execution entitlement: 0 / blocked

Steps to reproduce

1. Sign in to the Plus workspace.
2. Open Usage and verify Weekly usage limit: 100% remaining and Credits: 1,000 credits.
3. Open Codex and attempt to start work.
4. Codex reports that the workspace is out of credits and blocks execution.
5. Open Work in the browser and attempt to use it.
6. Work reports the same out-of-credits condition and blocks execution.
7. Restarting/reopening the macOS app does not change the result.

Expected behavior

If the Usage page shows 1,000 available credits and 100% weekly usage remaining for the same Plus workspace, Codex and Work should be usable and should draw from the available shared agentic usage/credit pool.

If another backend entitlement or ledger is actually authoritative, the Usage page should not display the credits as available. The displayed balance and the execution gate need to be consistent.

Impact

This completely blocks paid Codex/Work usage despite a visible purchased credit balance, stopping active development work. It also creates a risk that users purchase additional credits unnecessarily even though the product already shows an available balance.

Suspected area

This looks like an entitlement / credit-ledger synchronization problem between the Usage surface and the Codex/Work execution gate, rather than a client-side UI issue.

Related reports

• Showing "You’re out of Codex messages" either I have credits #19417 — Plus/macOS shows available credits while warning says out of Codex messages
• You’re out of Codex messages dialog appears with available credits #18587 — Plus/macOS out-of-messages warning despite credits
• Adding credits still show "You're out of codex messages" popup above the chat #21161 — credits added but out-of-Codex warning remains
• Codex blocked with “workspace is out of credits” despite remaining 5h/7d usage limits in VS Code and Codex Desktop #27598 — Codex blocked as workspace out of credits despite remaining usage limits
• Codex and Work analytics can show contradictory quota pools and zero credits while the global usage gate remains blocked #35047 — contradictory quota/credit pools and execution gating

The difference in this report is that the credit balance itself is explicitly positive (1,000), weekly usage is 100% remaining, and both Codex and Work are actually blocked across macOS and web.