{"version":"2.1.288","anchor":"remote-bridge-v2-fences-worker-epochs-and-handles-attach-con","canonical_anchor":"remote-bridge-v2-fences-worker-epochs-and-handles-attach-con","heading":"Remote Control handles two machines trying to attach to one session","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/remote-bridge-v2-fences-worker-epochs-and-handles-attach-con","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Remote Control handles two machines trying to attach to one session\n\nWhen two machines try to host the same Remote Control session, one can now follow the newer one or step down\n\n**Unclear.** It is unclear what decides which of these paths runs, or whether this tracking is active.\n\n**What**\n\nRemote Control lets a computer host a Claude Code session you reach from elsewhere. It now keeps track of which host is the current one for a session. If another host has taken over, the connection can continue with a follow-up check, continue without that check, or step down and close with the reason that it was replaced by another worker.\n\n**Why**\n\nThis changes what happens when two Remote Control hosts compete for one session.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}