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.
What
When 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.
There is now one more case:
- If the run is ending and a remotely controlled setting is on, the send-now request is allowed through.
- If Claude Code has not yet fetched its remote settings, the request is skipped and recorded as
skipped_busy_flags_not_fetched. - Otherwise it is still skipped as busy.
Why
This changes when queued messages interrupt a turn in headless sessions, which run without the interactive screen, and in remote sessions.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
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…