{"version":"2.1.296","anchor":"send-now-cuts-a-running-turn-only-while-a-run-is-ending-beh","canonical_anchor":"send-now-cuts-a-running-turn-only-while-a-run-is-ending-beh","heading":"Send-now messages can interrupt a running turn that is already ending","tier":"notice","area":"Message Queue","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/send-now-cuts-a-running-turn-only-while-a-run-is-ending-beh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Send-now messages can interrupt a running turn that is already ending\n\nA message sent with send-now can now cut into a running turn, but only when that turn is ending and a remote switch allows it\n\n**Unclear.** It is not stated what the remote setting falls back to when the server sends no value, so whether the new case applies without a server change is unknown.\n\n**What**\n\nWhen you queue a message while Claude Code is still working, a send-now request asks it to deliver that message right away and interrupt the current turn. A turn is one round of Claude working before it hands control back. Previously, once a run had started taking queued messages, a send-now request was always skipped as busy.\n\nThere is now one more case:\n\n- If the run is ending and a remotely controlled setting is on, the send-now request is allowed through.\n\n- If Claude Code has not yet fetched its remote settings, the request is skipped and recorded as `skipped_busy_flags_not_fetched`.\n\n- Otherwise it is still skipped as busy.\n\n**Why**\n\nThis changes when queued messages interrupt a turn in headless sessions, which run without the interactive screen, and in remote sessions.\n\n- Area: Message Queue\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}