Codex does not have one universal weekly number for every plan, model, workspace, and task. Check the current plan guidance and usage panel, then record the exact source and verification date.
The short answer
Codex usage is affected by the plan, model, task size, reasoning mode, input and output tokens, workspace eligibility, and current product rollout. A weekly limit shown for one account should not be copied as a universal quota for every user.
| Plan | Limit | Window / reset | Overage | Evidence |
|---|---|---|---|---|
| PlusCodex | Token-based credits; no fixed allowance in this draftcredits | No fixed windowCheck the current Codex usage panel and plan guidance; do not infer a fixed reset window from the rate card.The official Rate Card publishes credits per input, cached-input, and output token; this draft intentionally does not claim a fixed quota. | Plan and workspace eligibility determine whether additional credits are available. | OfficialChecked Aug 13, 2026, 9:17 AM UTC |
| ProCodex | Token-based credits; no fixed allowance in this draftcredits | No fixed windowCheck the current Codex usage panel and plan guidance; do not infer a fixed reset window from the rate card.The official Rate Card publishes credits per input, cached-input, and output token; this draft intentionally does not claim a fixed quota. | Plan and workspace eligibility determine whether additional credits are available. | OfficialChecked Aug 13, 2026, 9:17 AM UTC |
Why a single weekly number is risky
The official Codex rate card describes token-based credit rates rather than a universal message allowance. The usage guide also explains that limits can depend on plan and task complexity. This means an editor should record the exact plan, model, window, reset rule, and evidence before publishing a precise number.
How to check your current limit
Open the current Codex usage panel, compare it with the linked official guidance, and note the UTC time of the check. If a public announcement changes limits or adds a reset, record it as a separate Event with its own source instead of silently rewriting the historical limit.
Open the structured Codex limits page and review Codex pricing context. For reset notices, use the current reset status and reset history.
Editorial status
This Draft article intentionally avoids claiming an exact weekly quota. It becomes publishable only after an editor confirms the current plan scope, effective date, source URL, and any regional or workspace conditions.
Frequently asked questions
Does Codex have one fixed weekly limit?
No single number should be assumed across plans, models, task sizes, workspaces, or product rollouts. Record the exact scope and source before publishing.
Where should a weekly limit change be recorded?
Keep the structured limit version for the rule and create a separate sourced Event when a reset, policy, or product change occurs.
Sources and verification
Last checked Aug 13, 2026, 9:17 AM UTC.