{"version":"2.1.317","anchor":"send-now-on-a-remote-session-reports-no-answer","canonical_anchor":"send-now-on-a-remote-session-reports-no-answer","heading":"Send now on a remote session tells you when the session doesn't answer","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/send-now-on-a-remote-session-reports-no-answer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Send now on a remote session tells you when the session doesn't answer\n\nIf 'send now' gets no answer from a remote session, Claude Code shows a notice and gives your queued lines back\n\n**What**\n\nSend now delivers a message you had queued right away instead of waiting. When you use it on a remote session and the session sends no answer, Claude Code now shows: \"Send now got no answer from the session \u00b7 esc to interrupt and send\".\n\nThe lines you had queued are handed back to you instead of being lost. When the session reports that it was interrupted, Claude Code now falls back to cancelling.\n\nBefore, this failure was only written to the log.\n\n**Why**\n\nSend now no longer fails silently. You see what happened, you can press esc to interrupt the session and send, and your queued text stays with you.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}