Parent agent stops waiting on subagent after reconnect; requires manual prompt to resume
Open 💬 1 comment Opened Apr 1, 2026 by leandrotcawork
What version of the IDE extension are you using?
1.113
What subscription do you have?
Plus
Which IDE are you using?
VS Code
What platform is your computer?
WindowsMicrosoft Windows NT 10.0.26200.0
What issue are you seeing?
Description
When using subagents, if the Codex session is disconnected and later reconnected while a task is running, the parent agent stops properly observing the subagent lifecycle.
Even after the subagent completes its execution, the parent agent does not resume automatically. It behaves as if the task has finished or is idle, requiring a manual user prompt to continue execution.
This breaks the expected orchestration flow between parent agent and subagent.
What steps can reproduce the bug?
Steps to reproduce
- Start a task that uses a subagent
- Let the parent agent dispatch the subagent and wait for completion
- Disconnect from Codex (close session, reload, etc.)
- Reconnect to Codex
- Allow the subagent to finish execution
- Observe that:
- Parent agent does not resume automatically
- Send any manual prompt
- Parent agent resumes execution
##Actual behavior
After reconnecting:
- Subagent executes normally
- Subagent completes successfully
- Parent agent does not resume
- Parent appears stuck or idle
- Only resumes after manual user input (e.g. sending a message)
What is the expected behavior?
- Parent agent should continuously observe subagent status
- Upon subagent completion, parent should automatically resume execution
- Reconnecting should restore the observation loop/state correctly
Additional information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗