Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Show the current session's subagents and background tasks, with stop and transcript view

Open
  • Is something wrong?
#439 5 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@ayush5harma is already working on this.

Since Oct 14, 2026.

  • #443 by @ayush5harma — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
ai-infra-agents, cli

Research direction

Start from the task lifecycle the bridge normalizes (task_started, task_progress, task_updated, task_notification) and from sdk_inventory.tasks and TaskMetadata, which the progress fields would extend. The new commands wrap Query.stopTask(), getSubagentMessages() and listSubagents(). Done means the progress fields reach TaskMetadata, stop_task and get_subagent_messages work, and the UI placement agreed in #443 is implemented. The UI decision is still open, so confirm it before starting.

Written by the indexing model from the issue text.

Description

area: agent-sdk status: discussion type: feature

Rescoped after review on #443: the current session's agents only, built on the Agent SDK, with no Claude Code UI and no private job files.

Problem Statement

A session's subagents and background tasks are visible only as their tool calls in the transcript, where a detached launch shows a ↗ icon and a later result. There is no single place to see which of them are still running, what each is doing, or how much it has used. A running task cannot be stopped from claude-rs, and a subagent's own transcript cannot be read.

Proposed Solution

Add a view of the active session's subagents and background tasks, built on the Agent SDK the bridge already uses:

  • Source of truth: the task lifecycle state the bridge already normalizes from task_started / task_progress / task_updated / task_notification, held in Rust as sdk_inventory.tasks and on the Detached tool calls. The view projects that state and keeps no second store.
  • Progress data: forward the token and tool-use counts, last_tool_name and the progress summary from task_progress as fields of the existing TaskMetadata.
  • Stop: a stop_task command calls Query.stopTask(). The resulting stopped notification flows through the existing task path.
  • Subagent transcript: a get_subagent_messages command calls getSubagentMessages(), and listSubagents() shows which subagents have a transcript.
  • UI: placement, command name and any footer indicator are to be agreed in #443 before implementation.

Out of scope: other sessions, Claude Code's global background-session roster, and Claude Code's own agent view.

Alternatives Considered
  • Handing the terminal to Claude Code's claude agents, and reading its job files for a footer count. That was implemented in #443 and declined: claude-rs should not launch Claude Code's UI or reimplement its private job state.
Checklist
  • I have searched existing issues and discussions to ensure this is not a duplicate
Dominant language
Rust
Stars
261
Forks
57
Avg merge
10h 15m
Merged PRs (30d)
58

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from srothgan/claude-code-rust

All issues in srothgan/claude-code-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.