Codex weekly limits by plan
A plan name alone does not convert into a permanent task count. Current product rules, model behavior, and workload shape how long an allowance lasts.
Why this page does not publish a fixed task count
One task can be a short edit while another runs tools, searches, tests, and subagents for a long period. Even users on the same plan can consume capacity at different rates. A fixed statement such as tasks per week would create false precision.
Plan entitlements can also change. Verify current availability and limits in official pricing documentation and the signed-in usage interface before purchasing or upgrading.
What can vary between plans
Plans may differ in available capacity, model access, priority, organizational controls, and whether optional reset mechanisms appear. Workspaces can add policy constraints beyond the consumer subscription label.
- Check the exact plan and billing context.
- Check which model and reasoning effort are active.
- Separate five-hour and weekly counters.
- Do not infer your allowance from another user's percentage.
Compare plans using your workload
Track how often your real work reaches a limit, how much productive work remains blocked, and whether the bottleneck is short-window or weekly capacity. This evidence is more useful than comparing isolated screenshots from different users.
Broad resets do not redefine plan limits
An exceptional broad reset can restore capacity for a stated audience without permanently increasing the normal allowance. Unless the announcement explicitly describes a policy change, continue using the official plan terms for long-term planning.