{"version":"2.1.321","anchor":"bridge-environment-re-registers-when-directory-browse-advert","canonical_anchor":"bridge-environment-re-registers-when-directory-browse-advert","heading":"Remote Control now keeps a host's directory-browsing offer in sync","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/bridge-environment-re-registers-when-directory-browse-advert","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control now keeps a host's directory-browsing offer in sync\n\nWith Remote Control, Claude Code re-registers the machine whenever its directory-browsing offer changes, and handles host requests\n\n**What**\n\nRemote Control lets you drive a Claude Code session on one machine from somewhere else. The machine registers itself with the server and says what it offers. It now also says whether it offers directory browsing, and when that offer changes, the machine registers again. Before, only a change in the tools it offered caused this.\n\nIf registering again fails for a passing reason, the registration is marked \"unconfirmed\" rather than treated as done. Claude Code also now handles a kind of work called host requests, which it previously turned away as unsupported. Work declined because the machine is at capacity is now handled in one shared place.\n\n**Why**\n\nA machine can offer directory browsing over Remote Control, and the server's view of that offer stays up to date.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}