{"version":"2.1.238","anchor":"stop-task-control-request-stops-a-single-task","canonical_anchor":"stop-task-control-request-stops-a-single-task","heading":"stop_task control request stops a single task","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/stop-task-control-request-stops-a-single-task","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### `stop_task` control request stops a single task\n\nSDK and remote drivers can stop a single task by id with a new control request.\n\n**What**\n\nA program driving Claude Code over the SDK or a remote connection can now stop one running task by id, instead of interrupting the whole turn. It joins `interrupt`, `set_permission_mode` and `set_model` in the accepted control requests, and only works if the host program has registered a handler for it.\n\n**Details**\n\n- Takes a `task_id` string; a non-string id is rejected with \"stop_task: task_id must be a string\".\n- With no handler wired up, it rejects with \"stop_task is not supported in this context (callback not registered)\".\n- A `task_stop_user` telemetry event is emitted on the invalid-id path.\n\n**Evidence**\n\n`stop_task is not supported in this context (callback not registered)`\n\n- Area: SDK\n- Names: `stop_task`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5"}