What
Claude Code can run tasks in the background while you keep working, and the background tasks dialog (opened with /tasks) lists them. This release adds a new grouping for tasks called self-managed tasks:
- The dialog now gathers some tasks into a single
self_managed_tasksrow. Selecting that row expands it to show the individual tasks. The findings could not trace which tasks count as self-managed. - The dialog also has a new section keyed
self-managed. It appears only when a separate internal setting is switched on. - A check that decides how a task is treated now returns false for
self_managed_tasks, the same way it already did formonitor_ws. - The
local_workflowpart of the dialog no longer checks whether workflows are available before showing or stopping them.
Why
If you run many background tasks, some may now appear under one collapsed row instead of as separate lines, so you may need to open that row to find a particular task. Workflows listed in the dialog can also be shown and stopped without the availability check that used to come first.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear which tasks count as self-managed or what controls the self-managed section.
Anthropic's release notes agree
Changed /tasks to fold background work Claude Code runs for itself under one "System tasks" row; press Enter on it to show those tasks