Can't chat with the subagent session anymore v1.1.1 #4210

Open
opened 2026-02-16 17:43:02 -05:00 by yindo · 6 comments
Owner

Originally created by @anjanpoonacha on GitHub (Jan 5, 2026).

Originally assigned to: @thdxr on GitHub.

Question

I heavily use the multi agents capabilities. During the time of execution. I tend to have conversation with the subagents session instead of the primary agent session. In order to save the session from being bloated, and sometimes queue the messages in the subagent session when the agents go sideways. It was very handy.

Is it a bug that we don't see the chat in subagents?

Originally created by @anjanpoonacha on GitHub (Jan 5, 2026). Originally assigned to: @thdxr on GitHub. ### Question I heavily use the multi agents capabilities. During the time of execution. I tend to have conversation with the subagents session instead of the primary agent session. In order to save the session from being bloated, and sometimes queue the messages in the subagent session when the agents go sideways. It was very handy. Is it a bug that we don't see the chat in subagents?
Author
Owner

@rekram1-node commented on GitHub (Jan 5, 2026):

This was intentional, tho note that even before it got removed, you werent actually talking to subagent it was still primary agent just w/ the context of subagent

@rekram1-node commented on GitHub (Jan 5, 2026): This was intentional, tho note that even before it got removed, you werent actually talking to subagent it was still primary agent just w/ the context of subagent
Author
Owner

@anjanpoonacha commented on GitHub (Jan 5, 2026):

oh oh!!
I slightly altered the question to reflect what I really meant.
Sad to see the powerful feature sunset!!

@anjanpoonacha commented on GitHub (Jan 5, 2026): oh oh!! I slightly altered the question to reflect what I really meant. Sad to see the powerful feature sunset!!
Author
Owner

@bobab12 commented on GitHub (Jan 5, 2026):

This was a critical part of my workflow as well. Being able to send messages to subagent sessions allowed me to course-correct when needed and significantly improved subagent performance. Would love to see this restored.

Re: routing to the primary agent - that doesn't quite match my experience. When I sent messages while viewing a subagent (e.g., telling it to use gh CLI instead of webfetch for investigating source code), the subagent changed its behavior directly. Could be wrong, but it felt like direct communication. Either way, the functionality was valuable for steering subagents.

Edit: did some digging and you're technically correct that the TUI agent config was used, not the subagent's. But messages did go to the child session and became part of its context, which influenced subsequent behavior. That's what made it useful. Hope it can come back in some form.

@bobab12 commented on GitHub (Jan 5, 2026): This was a critical part of my workflow as well. Being able to send messages to subagent sessions allowed me to course-correct when needed and significantly improved subagent performance. Would love to see this restored. Re: routing to the primary agent - that doesn't quite match my experience. When I sent messages while viewing a subagent (e.g., telling it to use `gh` CLI instead of webfetch for investigating source code), the subagent changed its behavior directly. Could be wrong, but it felt like direct communication. Either way, the functionality was valuable for steering subagents. Edit: did some digging and you're technically correct that the TUI agent config was used, not the subagent's. But messages did go to the child session and became part of its context, which influenced subsequent behavior. That's what made it useful. Hope it can come back in some form.
Author
Owner

@OmarGoubail commented on GitHub (Jan 5, 2026):

I used this constantly too, It was very useful.

@OmarGoubail commented on GitHub (Jan 5, 2026): I used this constantly too, It was very useful.
Author
Owner

@vladislavlozhkin commented on GitHub (Jan 5, 2026):

This feature was exactly the reason I switched from Claude Code to OpenCode. The ability to interact with subagent sessions and course-correct them mid-execution was a game-changer for my workflow. Really disappointing to see it removed — might as well switch back to Claude Code now.

@vladislavlozhkin commented on GitHub (Jan 5, 2026): This feature was exactly the reason I switched from Claude Code to OpenCode. The ability to interact with subagent sessions and course-correct them mid-execution was a game-changer for my workflow. Really disappointing to see it removed — might as well switch back to Claude Code now.
Author
Owner

@anjanpoonacha commented on GitHub (Jan 6, 2026):

In fact, I stopped using the Opencode Desktop because this specific feature was removed.
I had created a question for that too! https://github.com/anomalyco/opencode/issues/6191

@anjanpoonacha commented on GitHub (Jan 6, 2026): In fact, I stopped using the Opencode Desktop because this specific feature was removed. I had created a question for that too! https://github.com/anomalyco/opencode/issues/6191
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4210