Codex hit its usage limit. Resuming safely is harder than clicking Continue.

说明与用途

当 Codex 达到使用限制时，恢复长任务比点击继续更困难。Continua 保存中断的任务，在恢复前验证环境，并避免重复提交，但在真实使用限制周期后自动恢复尚未得到验证。

问题

When Codex usage limits are hit, interrupted long coding tasks must be resumed safely, but detecting the interruption, verifying the environment, and avoiding duplicate submissions is difficult.

结果

The host-retry fix in Continua is implemented; the engine suite passed 336 tests and 27 native-controller checks. The patched build safely cancels stale continuations when newer user activity appears. However, unattended recovery through a fresh real usage-limit cycle remains unproven.

工作流

• Detect Codex task interruption and save task metadata and scope
• Wait for usage limit reset or monitor usage availability
• Before resuming, verify that the live Codex session matches the saved task and environment
• If no submission has been made, retry environment verification within a bounded recovery window
• If a submission may already exist, reconcile its outcome before any further submission
• If newer user activity is detected, cancel the stale continuation
• Resume the task by sending a continuation when all checks pass

证据

The host-retry fix is implemented and installed. The engine suite passed 336 tests, and 27 isolated native-controller checks passed.

来源

A timer answers when to check again. It does not establish that a particular task is safe to resume.

来源

The current implementation checks the original live writer and the rollout file it actually has open. It also checks the task metadata and project scope.

来源