{"version":"2.1.265","anchor":"remotecloud-sessions-take-back-held-but-unsent-messages","canonical_anchor":"remotecloud-sessions-take-back-held-but-unsent-messages","heading":"Unsent messages to remote sessions can now be taken back","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/remotecloud-sessions-take-back-held-but-unsent-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Unsent messages to remote sessions can now be taken back\n\nEscape (or an empty-prompt cancel) now reclaims messages queued for a remote session that haven't been sent yet\n\n**What**\n\n- Remote\/cloud sessions now track when a queued message is \"held\" (queued but not yet sent to the cloud session) and could still be withdrawn. `RemoteSessionManager` calls a new `tellWithholdableHeld()` method on release, gate resolution, withdrawal, and settlement, and fires an `onWithholdableHeldChanged` callback when that status changes; the UI tracks this as a `cloudMessageHeld` state.\n\n- Users can now press Escape while idle to reclaim messages that were queued but not yet sent, via a new `cancelHeldMessages` capability, instead of triggering a full interrupt. This shows a notice and logs telemetry.\n\n- Cancelling with an empty prompt while in remote mode now also cancels held remote messages, via the same `cancelHeldMessages` path.\n\n- Taking back the very first prompt (the one given on the command line, which starts out withheld) now shows a distinct notice: \"You took back your first message (the one given on the command line) \u2014 it wasn't sent to the cloud session.\"\n\n**Why**\n\nPreviously a message queued for a remote\/cloud session but not yet sent couldn't easily be pulled back. Now pressing Escape, or cancelling with an empty prompt, retracts it before it reaches the cloud session, with clear feedback about what happened.\n\n- Area: Sessions\n- Names: `Esc`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}