Preflight Checklist
Problem Statement
When working with subagents in visual studio code, the main chat window does not show which subagent performed which tool call. it would be useful to be able to see what subagent performed which actions.
This would help evaluating if sub agents are doing what they are supposed to do.
Proposed Solution
If a subagent performed a tool call such as MCP call, bash, etc, label the tool with the subagents name.
something like:
Alternative Solutions
I tried to give the orchestrator instructions to label tool calls, but the UI doesn't allow for this at the moment.
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
I'm using a fetcher/writer/reviewer loop to develop N8N workflows.
the main window acts as orchestrator for these three subagents.
right now, i'm unsure which agent is actually doing the tool calls i see. main orchestrator, or the sub agents.
to limit token usage and refine the instructions, knowing which agent does what is needed.
Additional Context
No response
Preflight Checklist
Problem Statement
When working with subagents in visual studio code, the main chat window does not show which subagent performed which tool call. it would be useful to be able to see what subagent performed which actions.
This would help evaluating if sub agents are doing what they are supposed to do.
Proposed Solution
If a subagent performed a tool call such as MCP call, bash, etc, label the tool with the subagents name.
something like:
Bash (subagent writer) xxxxxx
N8n-mcp [get_workflow_details] (subagent reviewer) xxxxx
Alternative Solutions
I tried to give the orchestrator instructions to label tool calls, but the UI doesn't allow for this at the moment.
Priority
Medium - Would be very helpful
Feature Category
Interactive mode (TUI)
Use Case Example
I'm using a fetcher/writer/reviewer loop to develop N8N workflows.
the main window acts as orchestrator for these three subagents.
right now, i'm unsure which agent is actually doing the tool calls i see. main orchestrator, or the sub agents.
to limit token usage and refine the instructions, knowing which agent does what is needed.
Additional Context
No response