{"version":"2.1.274","anchor":"new-device-id-validation-before-trusting-bridgesession-peer","canonical_anchor":"new-device-id-validation-before-trusting-bridgesession-peer","heading":"New device-ID validation before trusting bridge\/session peer","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-device-id-validation-before-trusting-bridgesession-peer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### New device-ID validation before trusting bridge\/session peer\n\nDevice IDs are now validated against a pattern before being trusted for bridge\/session connections\n\n**What**\n\nWhen a device ID is used to identify a peer (another connected device or session, such as over a bridge connection), Claude Code now checks it against a regular expression before accepting it. This applies both to the general device-ID validity check and to the step that pushes external configuration to a peer. Previously any non-empty string was accepted as a valid device ID.\n\n**Why**\n\nThis stops malformed device IDs from being treated as valid, which could otherwise let unexpected or malformed values flow into peer connections and configuration syncing.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}