[BUG] Tasks lacking descriptive task information

Resolved 💬 3 comments Opened Jan 17, 2026 by internationils Closed Feb 27, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Agent ac449f2 has completed classifying prompts. Agent af811a7 is still running ... and TaskOutput task: "af811a7" are not very helpful.

...this information does not tell me what the task is doing. It is very hard to follow when several parallel tasks are running in the background and reporting.

What Should Happen?

Make the task reporting clearer with the format is Action: File to Goal with three elements:

Action - verb (Update, Search, Edit, etc.): what's being done (Update, Search, Edit, etc.)
File - target file or scope: what file/target is affected
Goal - the purpose or outcome

Examples: "Update: Ch3 HTML to fix hierarchy", "Search: codebase to find auth code"

I tried to get claude to report this but it does not work:

## Task Agents
**Naming convention for task descriptions:** Use the format `Action: File to Goal`
- Examples: "Update: Ch3 HTML to fix hierarchy", "Search: codebase to find auth code", "Edit: deploy.sh to add validation"

## Progress Visibility
Use TodoWrite for any task expected to take 20+ seconds. This provides visibility into progress during longer operations. Use Action: File to Goal format.

Error Messages/Logs

Steps to Reproduce

Provide a prompt that requires longer running subtasks (log analysis, ...)

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.11

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_

View original on GitHub ↗

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