SDK clients can opt in so an interrupt kills only the current turn, not background agents.
What's wrong with this entry?
The SDK and stream-json initialize request accepts a new boolean saying your client renders a per-task stop control wired to the existing stop_task control request. Set it to true and an interrupt on an interactive stream-json session aborts only the current turn, leaving running background agents and workflows alive.
- Absence fails closed: the interrupt kills background tasks, as before.
- A one-shot run with stdin closed still kills hold-back tasks even when the option is declared.
- Client-declared at initialize; there is no server-side flag involved.
Declares that this consumer renders a per-task stop control wired to the stop_task control request, so the user can stop an individual background task.
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.238
stop_taskcontrol request stops a single taskBoth mention task stop
-
v2.1.227
claude rmtells you which session is holding a directoryBoth mention stop