Codex troubleshooting

Codex Usage Limit Reached: Plan, Reset and API Checks

Key facts

ScopeCodex
Last verified
DecisionCheck the signed-in account, work surface and usage dashboard before changing plans. Read the named restriction and reset time; current Pro rules differ from Plus five-hour estimates. If access disagrees with the dashboard, collect a redacted diagnostic bundle. API authentication is a separate billing path, not a way to refill subscription allowance.
Official documentation

Official error evidence (quote only; variants differ)

Official account and usage guidance

Diagnose Codex usage limits by account, plan and reset window. Compare API billing separately and collect safe evidence when the dashboard disagrees.

Last verifiedOctober 19, 2026
Quick fix

Check the signed-in account, work surface and usage dashboard before changing plans. Read the named restriction and reset time; current Pro rules differ from Plus five-hour estimates. If access disagrees with the dashboard, collect a redacted diagnostic bundle. API authentication is a separate billing path, not a way to refill subscription allowance.

What exact error is documented?

You’ve hit your usage limit.

Documented variant, not every possible message. Official source repository or documentation, checked 2026-10-19.

Match the symptom

  • You’ve hit your usage limit.
  • A completed sign-in or a visible allowance does not match what the current client can do.

First checks

Collect evidence before changing configuration

Inspect account state
codex login status
Inspect the client version
codex --version

Diagnosis 1

Are you viewing the same account and workspace?

Compare the account and workspace selected by the client with the dashboard you are reading. Personal and business access can have different restrictions. A browser tab signed into one account is not proof that the CLI uses it. Establish this before logging out, upgrading or assuming the server lost your entitlement.

  1. Run codex login status without printing credential files.
  2. Record which workspace and model the failed task used.

Diagnosis 2

Which reset rule applies to this plan?

Use the current official pricing page and dashboard together. Five-hour estimates are not a universal restriction across all plans, and message estimates depend on workload. Read the exact model or workspace restriction rather than inferring remaining capacity from a percentage belonging to another window or product surface.

  1. Check /pricing/codex for current plan distinctions.
  2. Wait until the displayed reset when an allowance is genuinely exhausted.

Diagnosis 3

Would API authentication solve a different need?

An API-key session draws from API billing at the selected model rates rather than increasing a ChatGPT allowance. Decide whether metered use fits the task and apply account spending controls first. If the dashboard and client disagree, changing payment mode can hide the symptom without explaining it; preserve evidence for official support.

  1. Compare the calculator assumptions with actual input/output usage.
  2. For login failures instead of allowance failures, use /troubleshooting/codex-login-failed.

If it still fails, send this evidence

A useful support request is reproducible and does not expose credentials.

  • Client version, operating system and work surface.
  • Exact error, timestamp and timezone, with credentials removed.
  • Account/workspace type and the displayed reset time, without private identifiers.
  • Last successful operation and a small reproducible read-only request.

Related paths

All troubleshooting guides

Related account failures

Frequently asked questions

Will reinstalling reset a usage allowance?

No. A service-side allowance belongs to the account. Reinstall only for an installation problem supported by diagnostics, and use the displayed reset or official support for an account restriction.

Should I post my authentication files for support?

No. Share the error, version, time and a redacted account-mode description. Never upload token files, API keys or an unredacted environment dump.

How do I know the fix worked?

Confirm the intended account and run one small read-only request. Check the resulting usage state before resuming the larger task.

Official sources

Commands and product behavior were checked against first-party documentation on October 19, 2026. Interfaces and authentication flows change; recheck the source when applying this across a team.