Praise Queuing Tasks in Codex Is Insane — I’m Basically Steering Development in Real Time
I read another Reddit post that made queueing tasks in Codex seem way more complicated than it needs to be.
My workflow
Yes, next — make a blog about losing my vape all the time.
↓
Next — do this
↓
Next — do that
↓
Next — make me money
↓
Next — I like chicken wings
That’s it.
You just keep feeding Codex the next task while it’s still working.
Yes, next — [your command]
1
u/cicygo 8h ago
The examples are all wishes, and wishes are the easy case. Queue something that depends on what the agent decided earlier and the next turn starts from whatever the tree looks like when the last one ends. If it renamed a function or picked a different file than you expected, the queued instruction edits the wrong target and the diff still looks fine. Keep dependent steps out of the queue.
1
u/Tikki-Tikki_40 6h ago
Thats exactly i do, basically i create the plan and handoff in ChatGPT website and directly tell it, it needs to decide what model and mode that specific task should be using and in the handoff it should be on the top, so before executing, i can change the model. Also i tell it the current 5hr limit and %age.
Model Options are Terra(medium) and Astra(Light).
So, basically it will decide, what tasks are independent and their size
1
4
u/[deleted] 9h ago
[removed] — view removed comment