Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.242 Home All releases ←olderv2.1.241 v2.1.243newer→
Claude Code v2.1.242

Interrupt behaviour for held sends is now written down

Under the hood
Useful2 Signal2
Elsewhere

The control protocol now spells out that interrupts keep held messages queued unless you cancel them.

What

The control-protocol schema now explains what happens to a message a client is still holding back: a plain interrupt leaves it held and lists it under still_queued, while cancelling queued messages withdraws it and reports it under cancelled.

Details
  • The same message can also be withdrawn on its own with cancel_async_message.
  • Today the only such hold is a message waiting for the session to take the initial upload from that machine.
  • A hosted-session driver follows a cancellation with a command_lifecycle frame marked cancelled when its own sweep cancels a send it had already delivered.
  • The behaviour is advertised to clients through the interrupt_cancel_queued_v1 capability.
Evidence

behind a send gate (today: waiting for the session to take the initial upload from that machine)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.242 →