{"version":"2.1.302","anchor":"remote-send-now-for-queued-messages","canonical_anchor":"remote-send-now-for-queued-messages","heading":"Queued messages can be sent right away in remote sessions","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/remote-send-now-for-queued-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Queued messages can be sent right away in remote sessions\n\nIn remote sessions, the send-now key and an empty Enter can now push a waiting message through immediately while Claude is working\n\n**Unclear.** It is not clear which remote machines support sending now, so whether this works in a given session is unknown.\n\n**What**\n\nWhen you type a message while Claude is still working, it waits in a queue. In a remote session, where Claude runs on another machine, Claude Code can now send that queued message immediately. This works when:\n\n- the remote machine supports sending immediately\n\n- Claude is in the middle of a turn\n\n- no sends are being held back\n\nThe send-now key does this, and so does pressing Enter on an empty prompt, which has one more condition of its own. If the remote machine does not support it, you see \"Send now isn't available here \u00b7 esc to interrupt and send\". Before, send-now only worked on your own machine's queue.\n\n**Why**\n\nThis changes what Enter and the send-now key do in remote and cloud sessions. Where sending now is not supported, press Esc to interrupt Claude and send instead.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}