{"version":"2.1.280","anchor":"remote-session-manager-tracks-unanswered-replicas","canonical_anchor":"remote-session-manager-tracks-unanswered-replicas","heading":"Live-collaboration replica tracking gains an 'unanswered' bucket","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-session-manager-tracks-unanswered-replicas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Live-collaboration replica tracking gains an 'unanswered' bucket\n\nRemote\/live-collaboration session replicas that never responded are now tracked as their own category\n\n**Unclear.** leaving placeholder, fix below\n\n**What**\n\nThe state Claude Code keeps for live-collaboration\/remote session replicas now includes a new `unanswered` set (or map) alongside the existing `replicas`, `unavailable`, `tooOld`, and `opening` buckets. It is cleared on reset\/teardown along with the others.\n\n**Why**\n\nThis lets Claude Code distinguish replicas that simply never responded from ones that are known-unavailable or stale, which should make replica-state handling and cleanup more accurate for remote\/cloud collaboration sessions.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}