claude-code - 💡(How to fix) Fix Show subagents of agents in the Agents view

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…

The Agents view currently shows top-level agents but does not display their spawned subagents. We'd like subagents to appear nested under their parent agent in the view.

Root Cause

  • Observability: Users can't see what subagents are doing or whether they've completed/failed
  • Debugging: Hard to diagnose issues in multi-agent workflows without seeing the full tree
  • Transparency: Complex tasks often spawn many subagents; visibility into the hierarchy helps understand what's happening and why
RAW_BUFFERClick to expand / collapse

Feature Request

Summary

The Agents view currently shows top-level agents but does not display their spawned subagents. We'd like subagents to appear nested under their parent agent in the view.

Current Behavior

The Agents view (FleetView) shows running agents, but subagents spawned via the Agent tool (or equivalent SDK calls) are not visible — they're essentially invisible from a monitoring perspective.

Desired Behavior

When an agent spawns subagents, those subagents should appear nested/indented under the parent agent in the Agents view, showing:

  • Subagent name/description
  • Current status (running, completed, failed)
  • Their output or last message

Why This Matters

  • Observability: Users can't see what subagents are doing or whether they've completed/failed
  • Debugging: Hard to diagnose issues in multi-agent workflows without seeing the full tree
  • Transparency: Complex tasks often spawn many subagents; visibility into the hierarchy helps understand what's happening and why

Use Case

When running a task that spawns multiple subagents (e.g., a feature-dev workflow with code-explorer, code-architect, and code-reviewer agents), it's currently impossible to monitor all the work happening without digging into log files.

Suggested UX

  • Show a collapsible tree under each agent with its spawned subagents
  • Indicate parent-child relationships (spawner → spawned)
  • Show subagent status inline

This would make the Agents view much more useful for complex, multi-agent workflows.

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