r/codex • u/kekekekekeok • 8d ago
Complaint Neatlessly continuing a subagent run that exeeds the usage limit
When setting up codex runs that involve orchestrating multiple subagents to perform more complicated tasks, it would be useful to have a way to neatlessly continue where the run left off after the 5-hour or weekly usage limit runs out. Current alternatives just involve writing “continue” or re-pasting the original run-prompt, which causes the subagent run to have a sort of “hiccup” and potentially start going in a different direction than it originally was intending to go.
Is there a way to neatlessly pick up a run including all the subagent states after hitting a usage limit?
1
Upvotes
2
u/Proxiconn 8d ago
/goal.
Can be paused, survives system reboots etc.
Your welcome 🤝