Repository navigation
Subagent messages are sent to main chat instead of subagent chat, breaking flow #2294
Description
When invoking a subagent, if it performs an action, the resulting message is not sent in the subagent chat. Instead, it appears in the main chat, disrupting the intended conversational flow.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 28, 2025
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
ak127a commentedon Aug 28, 2025
Looks like I should be using a primary agent and not a subagent.. closing the issue
ak127a commentedon Aug 28, 2025
Just realised I have a few of these setup and cycling them TAB isn't gonna be easy..
Any way to directly invoke an agent?
rekram1-node commentedon Aug 28, 2025
@ak127a just do an "@" reference to agent
ex: agent is called docs-agent
type into input:
@docs-agent please write docs on redis
rekram1-node commentedon Aug 28, 2025
you can also use the /agents slash command to open a dialog to select your primary agent from instead of tabbing
ak127a commentedon Aug 29, 2025
@ only lists the subagents, not the primary agents.
rekram1-node commentedon Aug 29, 2025
you can make an agent be both if you want to do that, but a primary agent is one that you specifically talk to, a subagent is one that the primary agent can call
rekram1-node commentedon Aug 29, 2025
you could also write slash commands for your agents and trigger them that way
gimbo commentedon Oct 1, 2025
@rekram1-node — I think the docs aren't clear on this point. In particular, in the Subagents section of the Agents page we have:
My initial reading of that final sentence was that I could directly interact with a subagent, but AFAICS that's not the case (and your comment suggests that too).
E.g. if I do this:
I might (from the docs) expect that question to be answered by the
generalagent (subagent), perhaps replying with its model name, or agent name. In fact, it seems it's handled by whatever primary agent is active. (As it happens, when I did it, it triggered a task for thegeneralagent, but that's different to directly interacting with the subagent, and the primary agent seems to have still been involved in the interaction.)rekram1-node commentedon Oct 1, 2025
yes u are correct in your understanding, it does still involve the primary agent we should probably be more clear on that…