claude-code - 💡(How to fix) Fix /tasks slash command — let users view the internal task checklist [2 comments, 3 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#50862Fetched 2026-04-20 12:10:59
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Timeline (top)
commented ×2labeled ×2

Code Example

> /tasks

Create privacy policy page
Create about page
Update navbar with help popover    (in progress)
Add footer links
Push to deploy
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

During long or complex sessions, Claude Code internally creates tasks (TaskCreate / TaskUpdate) to track its own progress — visible as a swirling progress indicator in the TUI. However, as a user, I have no way to inspect what those tasks actually are, their status, or how many remain.

My workflow: I run extended sessions (editorial sites, design systems) where Claude works through 5–10 subtasks in sequence or parallel. I can see the spinner but not the breakdown. I often wonder:

  • Is it stuck or making progress?
  • How many steps are left?
  • Should I interrupt and redirect, or wait?

This is especially painful during autonomous /loop sessions or when running background agents overnight — I come back and have no checklist to review.

The data already exists internally — Claude tracks tasks with status (pending, in_progress, completed). The gap is purely on the user-facing side: there's no way to read it.

A /tasks slash command that prints the current task list (like the recap feature does for conversation state) would close this gap. Something as simple as:

> /tasks

  ✓ Create privacy policy page
  ✓ Create about page
  ● Update navbar with help popover    (in progress)
  ○ Add footer links
  ○ Push to deploy

This would improve transparency, trust, and make it easier to collaborate with Claude on multi-step work without constantly asking "where are we?"

extent analysis

TL;DR

Implementing a /tasks slash command to display the current task list with their status would provide users with the necessary transparency and control over Claude's progress.

Guidance

  • Introduce a new /tasks command that queries Claude's internal task tracking system to retrieve the list of tasks with their respective statuses.
  • Design the command's output to display tasks in a clear and concise format, such as the proposed example, to facilitate easy understanding of the progress.
  • Consider adding filtering or sorting options to the /tasks command to allow users to customize the output based on their needs.
  • Ensure the implementation of the /tasks command does not introduce any performance issues or overhead on Claude's internal task tracking system.

Example

> /tasks

  ✓ Create privacy policy page
  ✓ Create about page
  ● Update navbar with help popover    (in progress)
  ○ Add footer links
  ○ Push to deploy

This example illustrates a simple and effective way to display the task list with their statuses.

Notes

The implementation details of the /tasks command may vary depending on Claude's internal architecture and task tracking system. It is essential to ensure that the command's output is consistent with the actual task status and does not introduce any inconsistencies or inaccuracies.

Recommendation

Apply workaround: Implement the /tasks command as proposed to provide users with the necessary transparency and control over Claude's progress. This solution directly addresses the user's need to inspect the tasks and their status, improving the overall user experience.

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