You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Message QueueArea: what it touches
ImprovementsKind: in v2.1.281,
What probably matters to youSection of the release
What
A message you type while Claude is still working goes into a queue. The option to send a queued message now has been rewritten. For each such message, Claude Code now decides between:
Waiting.
Moving running tools into the background so the message can be delivered early.
Raising the message to "now" priority.
Interrupting.
Cancelling the current turn (Claude's current reply), as a last resort.
Its log lines start with [low-latency-submit]. The result is sent as usage data under input_low_latency_submit, with outcomes that include delivered_early, fell_back_to_cancel, nothing_moved and check_threw.
Why
Sending a message immediately no longer has to throw away the work in progress, because Claude Code tries gentler ways to get it in first.
