claude-code - 💡(How to fix) Fix Feature request: Show agent/subagent task progress in terminal UI (parity with third-party tools) [1 participants]

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…
GitHub stats
anthropics/claude-code#48246Fetched 2026-04-15 06:29:04
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Love the new desktop UI — but it currently shows significantly less information about agent and subagent activity than third-party wrappers do.

Root Cause

Love the new desktop UI — but it currently shows significantly less information about agent and subagent activity than third-party wrappers do.

Code Example

Running agent  CLAUDE.md compliance review  >

  *  2m 34s · ↓ 2.2k tokens
RAW_BUFFERClick to expand / collapse

Summary

Love the new desktop UI — but it currently shows significantly less information about agent and subagent activity than third-party wrappers do.

Current behavior

When a subagent is running, the first-party Claude UI only shows:

Running agent  CLAUDE.md compliance review  >

  *  2m 34s · ↓ 2.2k tokens
<img width="1000" height="115" alt="Image" src="https://github.com/user-attachments/assets/05d20760-90c4-490c-8e50-1de6492e6f5b" />

That's it — no task list, no subagent breakdown, no status per agent.

Expected / desired behavior

Third-party tools (e.g. Vibe Island) surface much richer information in their UI:

<img width="844" height="651" alt="Image" src="https://github.com/user-attachments/assets/9521000f-412b-4d64-80a8-a54ed02b62e1" />
  • Named tasks with completion status (done / in progress / open)
  • A list of subagents with their descriptions, status, and elapsed time
  • The current tool/command being run

This creates a situation where users get better observability into Claude's own work from a third-party app than from the official one.

Suggested improvement

The terminal UI should surface at minimum:

  • Task list with status indicators (as populated via TaskCreate/TaskUpdate)
  • Active subagent names + status
  • Current tool invocation (already partially shown via the streaming output, but not in a persistent way during agent runs)

This is UX feedback, not a bug. The data is clearly available (tasks and subagents are tracked) — it just isn't surfaced in the terminal UI. Closing this visibility gap would make long agentic runs much easier to monitor from the first-party CLI.

extent analysis

TL;DR

Enhance the terminal UI to display detailed task and subagent information, similar to third-party tools, by leveraging existing data tracked via TaskCreate and TaskUpdate events.

Guidance

  • Review the current UI implementation to identify where task and subagent data is being processed and how it can be integrated into the display.
  • Investigate the TaskCreate and TaskUpdate events to understand the structure of the data they provide and how it can be used to populate a task list with status indicators.
  • Consider adding a section to the UI to display active subagent names, their status, and elapsed time, enhancing the current output that shows only the agent and a limited subset of information.
  • Evaluate the current streaming output to determine how the current tool invocation can be persisted and displayed in a more user-friendly manner during agent runs.

Example

No specific code example can be provided without more details on the implementation, but the enhancement could involve modifying the UI rendering logic to include additional fields such as task status, subagent details, and tool invocation information.

Notes

The solution requires access to the UI codebase and an understanding of how data is currently being handled and displayed. The exact implementation details will depend on the technologies and frameworks used in the project.

Recommendation

Apply a workaround by enhancing the terminal UI to include the suggested improvements, as there is no indication of a fixed version that addresses this issue. This approach directly targets the user's need for better observability into Claude's work from the official UI.

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