CODEX FIELD NOTES
How Codex usage limits work
Separate personal usage windows from public reset announcements, then plan coding sessions with less guesswork.
By codex resets editorial team · Updated · 3 min read
A useful Codex session plan starts with the task you need to finish and the allowance your account actually shows. This article focuses on keeping work resumable. The rate-limit reset guide contains the detailed window rules, reset types and official model estimates.
Identify the interruption before changing the plan
A usage limit, a conversation context boundary, a tool failure and a workspace restriction are different interruptions. Record the exact message and which counter changed. Do not assume that waiting for a public reset will fix an execution failure or an administrator restriction.
The Usage dashboard and Codex CLI /status show the current account allowances. Read each applicable renewal time separately. A public announcement cannot inspect those private counters.
Choose a checkpoint you can review
Define an observable result before beginning: a reproducible failing case, a reviewed patch, or a bounded investigation with supporting evidence. Save completed findings in the repository when appropriate. A checkpoint should let a person or another session continue without repeating the whole investigation.
Avoid splitting every trivial action into a separate chat. The goal is to preserve useful context while keeping the work understandable, not to maximize the number of starts and stops. Record what was tested and the strongest remaining uncertainty.
Keep context relevant to the job
Supply the files, constraints and examples that affect the intended result. Remove unrelated logs and repeated background explanations. Reuse research that is already complete rather than requesting it again from scratch.
A message is not a fixed unit of work. Model choice, reasoning, context, tools and speed affect consumption. Choose the configuration that can solve the task and evaluate the result against the acceptance criteria. Lower apparent usage is not useful if the patch leaves hidden work for the reviewer.
Preserve a handoff before a pause
Write down the current branch, changed files, checks already run, and the next concrete step. Distinguish evidence from hypotheses. Keep secrets out of handoff notes and select only the material necessary for the next task.
If an allowance runs out, consult the account's renewal time and available options. Do not plan a deadline around an unscheduled public reset or assume that a stored banked reset will be available to every account.
Read the current mechanism rules in one place
As verified on 2026-10-29, OpenAI pricing gives five-hour estimates for Plus and Standard Business; Pro currently has no five-hour limit. Weekly limits can also apply. Work and Codex share usage, while API-key use is billed separately.
For full details and account controls, use the Codex and ChatGPT rate-limit reset guide. For public event history, use the event timeline. Those pages answer different questions from the task-planning workflow above.