{"version":"2.1.285","anchor":"bridge-read-receipts-and-inbound-message-tracking","canonical_anchor":"bridge-read-receipts-and-inbound-message-tracking","heading":"Remote clients can get read receipts for messages they send to a session","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/bridge-read-receipts-and-inbound-message-tracking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Remote clients can get read receipts for messages they send to a session\n\nThe remote connection can now report when an incoming message was read and track messages that arrive more than once\n\n**Unclear.** It is not clear what decides whether read receipts are offered for a given connection.\n\n**What**\n\nClaude Code can be driven from another app over a remote connection it calls the bridge. When that connection starts up, Claude Code can now tell the other side that it supports read receipts, meaning it will confirm when a message sent to it has been read.\n\nClaude Code also now keeps track of incoming messages that get delivered a second time. It distinguishes these cases:\n\n- a repeat that arrives while the first copy is still being handled\n\n- a repeat that arrives after the first copy was finished\n\n- a repeat that arrives after the session started\n\n**Why**\n\nThe app on the other end can see that a message reached the session and was read. Claude Code can also recognise a duplicate and skip it instead of acting on the same message twice.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}