Clients no longer get the stream event announcing that a long tool is still running and interruptible.
What's wrong with this entry?
Claude Code no longer emits the stream message that told clients a long-running tool was still going and could be interrupted. The callback that delivered it has been pulled out of the dispatcher, the SDK message switch and the list of recognised message kinds, so any client subscribed to it simply stops receiving anything. Nothing replaces it as a signal: callers now infer tool state from the abort path instead.
- The event name
interruptible_tool_in_progressdoes not appear anywhere in this build. - Working out why a tool was aborted now rests on whether the tool had actually begun running, and on the shell caller kind reported by
shellCallerOf, which is one ofinner,turnoragent. - The per-tool lookup of interrupt behaviour and the state updater that emitted the event were both deleted.
- Where the tool scheduler used to update interruptible state, it now wakes waiting callers directly.
shellCallerOf, interruptible_tool_in_progress
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.228
Two new content block types are handled instead of hitting the unknown-type path
Both mention streaming
-
v2.1.233
Streamed events are no longer dropped during shutdown
Both mention streaming
-
v2.1.248
Streaming deltas can no longer crowd out task lifecycle events
Both mention streaming