Repository navigation
Persistent Callback orchestration/Loop #14110
Description
What variant of Codex are you using?
CLI
What feature would you like to see?
Why does codex not have this same feature claude code has:
- a persistent local agent process that stays alive between turns
- a scheduler/job controller that can sleep, watch processes, and resume work
So the short version is:
- Claude Code likely has a persistent orchestrator around the model
- this environment is turn-based
- background Bash can monitor things here, but it cannot inject a new assistant turn by itself
basically if I start running a script I want to be able to have a bash timer set for lets say 3 minutes to auto start a next process or check the log of the script running to know if it has to fix something, an error pops up to auto fix the bug, or to auto start the next process when the script finishes. Claude code does this by using a bash task with a timer where it can do tasks in teh background, when the background timer finishes it notofies claude to check on said task or do a specific task in that item without using tokens while it essentially sleeps
Additional information
No response
Activity
github-actions commentedon Mar 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
awaiter#12921Powered by Codex Action
cruzlauroiii commentedon Mar 24, 2026
This overlaps with #15679, which tracks the narrower in-chat
/loop <interval Xm> <message>implementation.Working implementation and reviewable diff are already available there:
That implementation queues recurring prompts in the same Codex thread, replaces the previous schedule when
/loopis run again, and automatically removes the loop when a loop-triggered turn determines the work is already complete.LawrentChen commentedon Sep 21, 2026
Hi guys. I am not a professional developer, but I made my tiny solution (a skill) for this polling issue in long-run tasks.
https://github.com/LawrentChen/codex_callback
For me it works pretty well. It allows the thread to be smoothly awakened and take over each time(can be more than once) the long-run task encounters a problem, and after completing phased tasks, it smoothly transitions to downstream docking tasks, requiring no polling or human intervention.
I use codex app and ssh to my developing server. It just works fine.
Take a look if you are interested.
etraut-openai commentedon Sep 22, 2026
Codex implements
/goalcommand for this purpose.LawrentChen commentedon Sep 22, 2026
Oh I forgot the /goal command. Sorry about that. I will make a try later. Thx!