Active turns cannot complete after 5-hour limit when Auto-review approval calls are required
What version of the Codex App are you using (From “About Codex” dialog)?
26.622.11653
What subscription do you have?
ChatGPT Plus ($20)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
An active Codex turn is allowed to continue past the five-hour limit, but when using approve for me mode, a required Auto-review sub-call is rejected as a new quota-consuming request. The parent turn remains nominally active yet cannot safely execute any command that crosses that approval boundary, such as elevated risk terminal/powershell commands. This failure was also noted by Codex itself. In my case, Codex could not access/sync to canonical WSL or run the remaining Linux-only validation gates, even though the task was still in progress.
<img width="769" height="75" alt="Image" src="https://github.com/user-attachments/assets/ff7691af-6506-4917-8d0b-60d500557eba" />
<img width="847" height="148" alt="Image" src="https://github.com/user-attachments/assets/f5f65eb5-cabd-4801-ae19-bd3068372922" />
What steps can reproduce the bug?
- Start a Codex Desktop local task with Approve for me / Auto-review enabled.
- Start or continue a sufficiently long-running task so that the five-hour local-message usage window becomes exhausted while the original task/turn is still in progress.
- While that same active task is still working, have Codex attempt a known approval-requiring command. For example, have it need to use a host-side PowerShell command that requires approval in the current configuration..
- Observe the Auto-review item. The collapsed UI presents it as “Auto-review denied high risk.” The expanded error says that automatic approval review failed because the account hit its usage limit and provides the same retry/reset time as the five-hour limit.
- Observe that the parent task remains nominally active but cannot execute the required elevated command. It may instead report that it cannot safely sync, verify, or run the remaining work until the approval path becomes available again.
What is the expected behavior?
When Codex permits an already-active turn to continue after a five-hour usage limit, all required internal operations necessary to safely complete that turn, including eligible Auto-review approval calls, should remain admissible under the same continuation policy, subject to fair-use and safety limits. Otherwise, I effectively cannot finish the term properly if the turn requires extensive elevated risk commands like PowerShell commands.
Additional information
_No response_