codex - 💡(How to fix) Fix Subagent review requests are not clearly surfaced in the main thread

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

What version of the IDE extension are you using?

26.506.31421

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

Linux 7.0.4-100.fc43.x86_64 x86_64

What issue are you seeing?

When the subagent is waiting for an instruction or for a question to be answered, the user is not always clearly notified in the main thread. However, after opening the subagent thread for the first time and then returning to the main thread, the question starts appearing there, in the main thread, for subsequent interactions.

Sometimes, you may wait for a long time thinking the subagent is still running, while the required-review notification is not clear enough in the first time.

I ran a brief example:

Main thread <img width="447" height="911" alt="Image" src="https://github.com/user-attachments/assets/46650a15-c103-45c8-86b3-63f0215e9b00" />

Subagent thread <img width="447" height="911" alt="Image" src="https://github.com/user-attachments/assets/d7c8bb8d-beaa-47d8-89fe-d5ef3f9bc34a" />

What steps can reproduce the bug?

Start a thread asking the agent to spawn a subagent with instructions to run a command that will likely require your review. Example: docker ps.

What is the expected behavior?

There are a few ways to make the notification clearer:

  • Always expand the subagent details wrapper attached to the composer.
  • Always show the question in the main thread, with clear information about which subagent is asking it. When multiple subagents require input, this could be shown as a multi-step question flow.

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING