First-party sleep/wait with wake signals

Open 💬 2 comments Opened Jun 21, 2026 by danthegoodman1
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

App

What feature would you like to see?

For loop-like behavior where say an implementer and reviewer thread is spawned by a coorindator, there's a lot of time wasted when an implementer or reviewer finishes, and the coordiantor is doing something like 5min waits to check on progress. If you have too short of a wait, the coordinator burns a lot of tokens checking something that's in-progress, but if you have too long of a wait, there's a ton of wasted time where the coordinator is waiting for something that's already finished.

The better result would be a first-class wait mechanism that can be interrupted by events like steer messages or spawned threads completing. That would allow the sleep period to be more of a timeout so that blocking tool calls/out of control threads can be identified by the coordinator, but it can also iterate without delay when things complete running.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #28144

Powered by Codex Action

danthegoodman1 · 2 months ago

#28144 is similar, but seems specific to goals. I'm also specifically calling out threads as a signal.