{"version":"2.1.285","anchor":"background-tasks-dialog-collapses-self-managed-tasks-into-on","canonical_anchor":"background-tasks-dialog-collapses-self-managed-tasks-into-on","heading":"Background tasks dialog groups self-managed tasks into one row","tier":"notice","area":"Background Tasks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/background-tasks-dialog-collapses-self-managed-tasks-into-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Background tasks dialog groups self-managed tasks into one row\n\nA new 'self-managed tasks' kind is collapsed into a single expandable row in the background tasks dialog and excluded from one task-type check\n\n**Unclear.** It is not clear which tasks count as self-managed or what controls the self-managed section.\n\n**What**\n\nClaude 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:\n\n- The dialog now gathers some tasks into a single `self_managed_tasks` row. Selecting that row expands it to show the individual tasks. The findings could not trace which tasks count as self-managed.\n\n- The dialog also has a new section keyed `self-managed`. It appears only when a separate internal setting is switched on.\n\n- A check that decides how a task is treated now returns false for `self_managed_tasks`, the same way it already did for `monitor_ws`.\n\n- The `local_workflow` part of the dialog no longer checks whether workflows are available before showing or stopping them.\n\n**Why**\n\nIf 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.\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}