What probably matters to youSection of the release
What
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.
Details
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.
Evidence
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.
