Unclear The finding does not say what user-visible message or indicator appears when cloudMessageHeld is set, only that the state is threaded through to the message list.
What
- 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.
RemoteSessionManagercalls a newtellWithholdableHeld()method on release, gate resolution, withdrawal, and settlement, and fires anonWithholdableHeldChangedcallback when that status changes; the UI tracks this as acloudMessageHeldstate. - Users can now press Escape while idle to reclaim messages that were queued but not yet sent, via a new
cancelHeldMessagescapability, instead of triggering a full interrupt. This shows a notice and logs telemetry. - Cancelling with an empty prompt while in remote mode now also cancels held remote messages, via the same
cancelHeldMessagespath. - 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) — it wasn't sent to the cloud session."
Why
Previously 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.
Names in the bundlecloudMessageHeld
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what user-visible message or indicator appears when `cloudMessageHeld` is set, only that the state is threaded…