{"version":"2.1.285","anchor":"remote-bridge-read-receipts-and-stream-flush-option","canonical_anchor":"remote-bridge-read-receipts-and-stream-flush-option","heading":"Remote session bridge reports read receipts and delivery","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/remote-bridge-read-receipts-and-stream-flush-option","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote session bridge reports read receipts and delivery\n\nThe connection to remote sessions can now report when incoming messages are read and delivered, and flush streamed output sooner\n\n**Unclear.** What these new reporting options control for someone using a remote session is not clear.\n\n**What**\n\nThe remote bridge is the link between Claude Code and a session running elsewhere. It can now:\n\n- report read receipts for incoming messages, meaning it signals when a message has been received and read\n\n- report message delivery\n\n- send streamed output as soon as the first piece of text arrives\n\nSeparately, reporting worktree state over the bridge is still controlled by a remote switch, and is off unless it is switched on remotely.\n\n**Why**\n\nThis gives remote sessions better tracking of whether messages actually arrived.\n\n- Flag `tengu_ccr_handoff_metadata`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.285; this account: on, anonymous baseline: on, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}