after hitting 5h limit but the goal still running, app keep streaming hit usage limit

Resolved 💬 3 comments Opened May 15, 2026 by charles-chenzz Closed Jun 10, 2026
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.506.31421 (2620)

What subscription do you have?

plus

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

after hitting 5h limit but the goal still running, app keep streaming hit usage limit
<img width="701" height="702" alt="Image" src="https://github.com/user-attachments/assets/5af64428-759f-466a-a9a4-632c8eb5df90" />

What steps can reproduce the bug?

a task running and hitting the limit but the task still didn't finish, is able to reproduce

What is the expected behavior?

only stream one hit limit message and pause the goal or if hitting the limit, just show one message that tell user they've hit the limit and stop the stream

ps: I remember that if we hit limit but task still running, it will still try to finish the job( I'm not saying we should, but keep streaming multi hit-limit message looks ugly..)

Additional information

_No response_

View original on GitHub ↗

3 Comments

etraut-openai contributor · 3 months ago

We could pause the goal, but other users have said that they like the fact that the goal isn't paused in this situation. The agent automatically continues additional usage becomes available.

charles-chenzz · 3 months ago
We could pause the goal, but other users have said that they like the fact that the goal isn't paused in this situation. The agent automatically continues additional usage becomes available.

personally I want the API or agent stop keep streaming same 'you've hit your limit' to the app's conversation flow, which will make the app looks like full of 'hit your limit' message. regarding the goal is paused or not, both of them is fine for me

etraut-openai contributor · 2 months ago

This has been addressed in recent versions. The goal is now paused when you hit the usage limit.