The first client to attach decides per-task stop behaviour, and it is lost on worker restart.
What's wrong with this entry?
The perTaskStopAffordance declaration is stored on a per-surface capability latch: the first client to attach sets it, and later clients cannot change it. Across worker restarts it is classified as "lost" rather than restored, so a reconnecting client must declare it again or interrupts go back to killing background tasks.
- Plumbed through the initialize config and the control-request handshake.
- Any SDK consumer on this build can reach it by setting the field; no remote flag gates it.
Declares that this consumer renders a per-task stop control wired to the stop_task control request, perTaskStopAffordance
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