SDK and remote drivers can stop a single task by id with a new control request.
What's wrong with this entry?
A 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.
- Takes a
task_idstring; a non-string id is rejected with "stop_task: task_id must be a string". - With no handler wired up, it rejects with "stop_task is not supported in this context (callback not registered)".
- A
task_stop_usertelemetry event is emitted on the invalid-id path.
stop_task is not supported in this context (callback not registered)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
claude rmtells you which session is holding a directoryBoth mention stop
-
v2.1.246
New initialize option
perTaskStopAffordancechanges what interrupt killsBoth mention stop task
-
v2.1.246
Per-task stop is first-attached-client-wins and does not survive a worker restart
Both mention stop task