{"version":"2.1.283","anchor":"remote-control-bridge-re-registers-its-environment-when-the","canonical_anchor":"remote-control-bridge-re-registers-its-environment-when-the","heading":"Remote Control re-registers a machine when what it offers changes","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/remote-control-bridge-re-registers-its-environment-when-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Remote Control re-registers a machine when what it offers changes\n\nA Remote Control machine now re-registers itself when its tool-hosting details, Claude Code version or platform change, not only after an error\n\n**Unclear.** It is not clear whether this behaviour sits behind a setting or a server-side switch.\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, describing what it offers: its tool-hosting details, its Claude Code version and its platform.\n\nEach time it asks the server for work, it now compares what it offers with what it registered last. If they differ, it re-registers the same environment in place. Before, it re-registered only after the server answered a request with \"unauthorised\" or \"not found\".\n\n- If the server refuses the new registration, the error is written to the log.\n\n- At startup, a failure to set up tool hosting is logged as a non-fatal error.\n\n**Why**\n\nAfter you upgrade Claude Code, or the machine's tool-hosting abilities change, the server gets current details instead of stale ones.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}