Does /compact Reset Codex Usage Limits?
Codex /compact frees conversation context. Learn which meter to check, how to preserve your task, and what to do when compaction reports a usage limit.
Codex /compact addresses a crowded conversation. A usage-limit message addresses the account doing the work. The distinction matters when a long coding session produces both: clearing space in the conversation does not establish that the account can run another task.
On this page
1. Read the meter before choosing a command
In the interactive Codex CLI chat, enter /status. These slash commands belong in Codex’s composer, not at your shell’s normal prompt. Read the context information separately from any account-limit rows. OpenAI documents /status for inspecting the session and for checking remaining limits during a CLI session. Command reference · Current usage limits.
Save the task checkpoint, then use /compact to summarize the chat.
Open the usage dashboard. Check the affected allowance, reset time and available account options.
Use the official usage dashboard when the limit label is unclear. Compare the same signed-in account and workspace. Do not infer a remaining account percentage from the amount of space left in one chat.
2. Preserve the unfinished task, then compact
Before summarizing a long session, save the details you cannot afford to have blurred: the next change, the files involved, decisions already made and what has actually been checked. Write the note yourself if account usage is exhausted.
This is an illustrative checkpoint for a fictional preferences feature. Replace every file and result with your own; write “not checked” when that is the truth.
Goal: Add a keyboard shortcut to open Preferences.
Decision: Reuse the existing Preferences window.
Changed: src/preferences.ts and src/shortcuts.ts.
Verified: Shortcut parsing tests passed before the latest edit.
Not checked: Window focus after the latest edit.
Next: Review the last diff, rerun tests, then check focus.
Now enter /compact in the Codex CLI. If Codex offers confirmation, review it and confirm the summary. The documented behavior replaces earlier turns with a concise summary to make room in context. OpenAI’s compaction instructions.
After compaction, use the checkpoint to check the next proposed action. A useful prompt is: “Before editing, restate the pending change, the constraint we must preserve, and the next verification.” Correct missing details before letting the agent continue. A summary helps continuity; keep exact requirements and test evidence in a durable note when they matter.
3. If compaction reports a usage limit, follow that limit
A message can name a compact task and still describe an account problem. A May 2026 user report records this wording:
Error running remote compact task: You’ve hit your usage limit.
That is a historical report from an older CLI, not a test of the current release. It illustrates why the operation’s name alone is insufficient to choose the fix. Read the rest of your current error and compare it with your account dashboard.
Check the affected allowance and its reset time. OpenAI’s pricing guidance directs users to the dashboard for current limits and describes additional credit routes that depend on the account or workspace. An active turn may be allowed to finish subject to fair-use limits; that is not evidence of a newly refilled allowance. OpenAI’s usage-limit guidance.
If a fresh reading still conflicts with the error, retain both, along with the time, model and CLI version, for a focused support report. Avoid a retry loop that keeps producing the same blocked operation.
4. Start a new chat for a new task, not a new allowance
Use /new when a fresh conversation is the right workspace for the next task. For unfinished work, bring the checkpoint so the new chat starts with the actual goal and outstanding check. OpenAI lists /new as a fresh-chat command. Built-in CLI commands.
The account relationship persists: OpenAI documents that local messages and cloud chats share the plan’s allowance. Starting another conversation does not create another subscription budget. Longer context can affect consumption, but there is no fixed percentage of allowance you can recover by compacting. What affects Codex usage.
Treat compaction as context maintenance. Decide whether to continue, wait or use an account-specific option from the current provider reading.