### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement The Background tasks panel in the desktop app shows a running task's title, elapsed time, token count, tool-use count, and tool type (e.g. "Agent · 5m 25s · 124.6k tokens · 62 tool uses · Bash"), but it does not show w

[FEATURE] Show which agent/subagent was invoked in the Background tasks panel

Open 💬 0 comments Opened Jul 5, 2026 by DUCKJAIII

Preflight Checklist

[x] I have searched existing requests and this feature hasn't been requested yet
[x] This is a single feature request (not multiple features)

Problem Statement

The Background tasks panel in the desktop app shows a running task's title, elapsed time, token count, tool-use count, and tool type (e.g. "Agent · 5m 25s · 124.6k tokens · 62 tool uses · Bash"), but it does not show which agent/subagent was actually triggered. When multiple agents/subagents are defined, there's no way to tell from this panel which one is doing the work — I can see that an agent is running and what it's costing in tokens, but not its identity.

Proposed Solution

Display the invoked agent's name/type in the Background tasks card, next to or under the existing "Agent" label — e.g. Agent: code-reviewer or Agent (security-auditor). It should match the name shown in the agent definition / /agents list so it's directly traceable.

Alternative Solutions

Surface the agent name on hover (tooltip) or only in the expanded "View transcript" view. This is lighter-weight but weaker — it defeats the purpose of at-a-glance identification, since I'd have to hover or open each task individually. Showing it inline on the card is preferred.

Priority

Low - Nice to have

Feature Category

Other

Use Case Example

I have several agents defined and kick off a background task. The panel shows "Audit stdlib-urllib egress paths — Agent · 5m 25s · 124.6k tokens · 62 tool uses · Bash." I want to confirm the intended agent was selected (not a wrong/fallback one) and attribute the 124.6k-token spend to that specific agent — but without the agent name shown, I have to open the transcript to find out which agent is burning the tokens.

Additional Context

The token count is already surfaced, which is great for cost awareness — surfacing the agent identity alongside it makes the panel genuinely actionable. Screenshot attaches directly in the GitHub form; drag it into the text box.

View original on GitHub ↗