Repository navigation
Bug: When a spawned agent finished the calling agent/session does not continue #22755
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.513.20950 (2816)
What subscription do you have?
Pro+
What platform is your computer?
26.4.1 (25E253)
What issue are you seeing?
A sub-agent is spawned, the main agent/session is just sitting there doing nothing. I have seen it where it for example says "I will spawn an agent to do X while I do Y", spawns X and then just sits there.
Also, saying "I will spawn agent to do X" and then just sits there.
Even when the sub-agent completes the task it never continues. When I then ask it sometimes says it got the "notification" the sub-agent finished but it never got the result.
What steps can reproduce the bug?
Feedback ID: 019e26a3-c50e-79b3-a819-9f5ab712d78e
What is the expected behavior?
When it says it will spawn and agent and then itself continue on something to actually continue. And in the end when the sub-agent completes to get the results and continue working on the task.
Additional information
No response
Activity
ehendrix23 commentedon May 15, 2026
Adding another feedback. This time I wanted to start "clean" making sure was not an issue due to context compaction before or so. Still happening however.
Feedback: 019e2c28-bdab-7671-a583-7bb64844e1c5
Next I will try to not use /goal to see if it happens.
ehendrix23 commentedon May 15, 2026
This time without using "/goal". For this it spawned 4 agents. 3 of them finished their work, but 1 of them just sat there not doing anything at all.
It then stated 3 of them completed, and then stopped processing.
Feedback: 019e2ca6-33dc-7992-9587-438deb282ad5