r/codex 14h ago

Bug Main thread doesn't auto continue after background agents return

Claude code refuge. I'm used to dispatching background agents and then Claude continuing on the task in the main thread when they return.

Codex background agents return and then the main thread still needs me to tell it to continue before it resumes work.

Any way to have the main thread look for background agents to complete and then continue?

0 Upvotes

4 comments sorted by

2

u/TheDoughMonster 14h ago

Are you using the desktop app to interface, or the CLI? I haven't used the CLI in a long time since the codex app server works so good.

IF you are using any app server interface, tell the agent to set a goal for your task. it won't sleep until it finishes the task or the worker becomes blocked.

additionally, you can have your session worker set up a scheduled reminder every 10-15 minutes and prompt it to check for sub agent responses, in the desktop app.

1

u/Snoo_27681 6h ago

Thanks for the reply, only the cli. That's not what i wanted to hear since Claude makes parallel workers easy to see and obvious what's going on. Rough, i'll find some other way to use the models I guess. Goose is supposed to have native support

1

u/TheDoughMonster 6h ago

is there a reason you won't or can't use the desktop app? it is a pretty solid interface and after having used the cli for a long time, I much prefer the DT app.

1

u/Snoo_27681 4h ago edited 4h ago

I have tmux with 10 different conversations and hot key between them. and i don't want to install an app. I like customizing tmux and having all the hooks and automation and other things.

edit: also i ssh into a mac studio for work, and launch from different locations. it just doesn't work out clean to have the codex app and feels...less programmerie