{"version":"2.1.281","anchor":"new-low-latency-submit-controller-for-messages-queued-while","canonical_anchor":"new-low-latency-submit-controller-for-messages-queued-while","heading":"New low-latency submit controller for messages queued while a turn is running","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-low-latency-submit-controller-for-messages-queued-while","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New low-latency submit controller for messages queued while a turn is running\n\nSending a queued message now can deliver it early without cancelling Claude's turn, falling back to cancelling only if needed\n\n**What**\n\nA 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:\n\n- Waiting.\n\n- Moving running tools into the background so the message can be delivered early.\n\n- Raising the message to \"now\" priority.\n\n- Interrupting.\n\n- Cancelling the current turn (Claude's current reply), as a last resort.\n\nIts 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`.\n\n**Why**\n\nSending a message immediately no longer has to throw away the work in progress, because Claude Code tries gentler ways to get it in first."}