Codex usage limits currently interrupt active coding work in a way that can lose execution continuity.

What version of Codex CLI is running?

v0.142.5

What subscription do you have?

Pro

Which model were you using?

gpt-5.5

What platform is your computer?

Linux

What terminal emulator and version are you using (if applicable)?

Konsole

Codex doctor report

What issue are you seeing?

Codex usage limits currently interrupt active coding work in a way that can lose execution continuity.

The worst part is that once the limit is reached, Codex may refuse even a final cleanup/checkpoint prompt. That means the user cannot ask the agent to write CODEX_PROGRESS.md, summarize the latest work, commit safe changes, or preserve the next action before quitting.

Expected behavior:

• When a usage limit is reached mid-task, Codex should enter a “paused/checkpoint-only” mode.
• It should allow a small final non-reasoning cleanup action:
• write progress file
• print latest git status
• summarize current task state
• optionally commit a WIP checkpoint
• It should persist the active run state automatically.
• After reset, it should resume the same run, not restart from planning.
• There should be an option: “Resume automatically after reset.”

Current behavior:

• Codex hits the limit.
• The user cannot even ask it to checkpoint.
• Resume may restart from plan or reconstruct state poorly.
• The user has to manually recover from disk and babysit the agent.

This is especially bad for long-running coding tasks where the whole point of Codex is autonomous execution.

What steps can reproduce the bug?

Uploaded thread: 019f28eb-2a9a-7903-9abb-fe75bb953c7e

What is the expected behavior?

_No response_

Additional information

_No response_