{"version":"2.1.271","anchor":"forked-slash-commands-now-register-with-a-task-registry-and","canonical_anchor":"forked-slash-commands-now-register-with-a-task-registry-and","heading":"Forked slash commands now register with a task registry and share an abort controller","tier":"internal","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/forked-slash-commands-now-register-with-a-task-registry-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Forked slash commands now register with a task registry and share an abort controller\n\nForked slash-command subagents now register in a task registry and share an abort controller with their caller\n\n**What**\n\nWhen a slash command runs as a forked subagent (a separate agent process spun off to handle it), it now registers itself into a `taskRegistry` with an abort controller linked to the caller, and marks its status as 'failed' or 'completed' when it finishes. This replaces the previous, simpler cleanup call.\n\n**Why**\n\nThis gives Claude Code a more structured way to track and cancel forked subagent tasks tied to slash commands, including propagating cancellation from the caller.\n\n- Area: Slash Commands\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}