/tasks slash command — let users view the internal task checklist

Resolved 💬 4 comments Opened Apr 19, 2026 by nodox-studio Closed Apr 23, 2026

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

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?"

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗