{"version":"2.1.281","anchor":"remote-control-bridge-re-sends-its-tool-host-advert-when-re","canonical_anchor":"remote-control-bridge-re-sends-its-tool-host-advert-when-re","heading":"Remote Control bridge re-sends its tool-host advert when re-registering","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/remote-control-bridge-re-sends-its-tool-host-advert-when-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Remote Control bridge re-sends its tool-host advert when re-registering\n\nRemote Control now re-sends its tool-host advert when it re-registers after a 401 or 404\n\n**Unclear.** The finding does not say what the tool-host advert contains or what a reader notices when it is missing.\n\n**What**\n\nThe Remote Control bridge links a local Claude Code session to a remote client. It re-registers when a poll, its regular check-in with the server, comes back with a 401 or 404 error. It now includes its tool-host advert (`getToolHostAdvert`) when it re-registers, and it records whether that advert was confirmed.\n\nTwo logging changes come with this:\n\n- The ack and stop calls can now log a different id from the one they send.\n\n- When re-registration returns a different environment id, the log line now says \"not adopting it\".\n\n**Why**\n\nAfter the bridge reconnects, the server hears again what the local session offers, instead of that information being dropped. The log wording makes clear that a new environment id is not picked up.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}