{"version":"2.1.293","anchor":"cloud-session-send-failure-now-has-a-message-that-says-the-m","canonical_anchor":"cloud-session-send-failure-now-has-a-message-that-says-the-m","heading":"Clearer message when a message to a cloud session may not have been sent","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cloud-session-send-failure-now-has-a-message-that-says-the-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Clearer message when a message to a cloud session may not have been sent\n\nWhen sending to a cloud session fails, Claude Code now says if the message may have arrived anyway and to resend if Claude doesn't reply\n\n**What**\n\nWhen a message you send to a cloud session (a Claude Code conversation running on a remote machine rather than your own) cannot be sent, Claude Code now picks between two messages:\n\n- If the message may still have reached the session, it says so and tells you to resend it if Claude doesn't respond.\n\n- Otherwise, it says the message couldn't be sent.\n\n**Why**\n\nA failed send does not always mean the message was lost. Saying which case you are in helps you decide whether to wait or resend, instead of sending the same message twice.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}