{"version":"2.1.293","anchor":"queued-remote-notifications-track-dropped-reads","canonical_anchor":"queued-remote-notifications-track-dropped-reads","heading":"Queued remote notifications count dropped reads, plus other remote-session bookkeeping","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/queued-remote-notifications-track-dropped-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Queued remote notifications count dropped reads, plus other remote-session bookkeeping\n\nQueued remote notifications gain a readsDroppedThisTurn counter and keep pinned items, alongside several small remote-session tracking changes\n\n**What**\n\nA remote session is one where Claude Code runs somewhere else and you connect to it. Notifications from that session can wait in a queue until they are read. This release changes how that queue keeps track of itself, with a few related changes nearby:\n\n- Queued remote notification state gains a `readsDroppedThisTurn` counter, which counts reads that were dropped during the current turn.\n\n- Pinned notifications are now carried over into the new state. Before, the state always started with an empty pinned list.\n\n- A new feature tag, `rtc_return_announce`, is added.\n\n- The callback that reports how an announcement went now receives a status. The older handler runs only when that status is not `\"returned\"`.\n\n- Diagnostics recorded when a server-sent event (SSE) stream ends, meaning the live connection that pushes updates, now carry `\"sse_stream_ended\"`.\n\n- The counts of settings rules that were dropped now include `credential` and `credentialRestrictions`.\n\n**Why**\n\nThese are internal tracking changes for remote sessions. The one you may notice is that pinned notifications are no longer cleared when the queue's state is rebuilt.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}