{"version":"2.1.319","anchor":"bridge-identity-probe-get-bridge-identity-added-to-the-loc","canonical_anchor":"bridge-identity-probe-get-bridge-identity-added-to-the-loc","heading":"Local browser pairing gains an identity check and external relay tracking","tier":"internal","area":"Extension Pairing","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bridge-identity-probe-get-bridge-identity-added-to-the-loc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Local browser pairing gains an identity check and external relay tracking\n\nLocal pairing can now ask the paired side for its bridge identity and logs its extension version and external relay support\n\n**What**\n\nPairing links Claude Code to another program on the same machine through a local connection. Several things were added to it:\n\n- An identity check that asks the paired side for its device ID and verifies the reply.\n\n- The pairing log line now reports the paired extension's version and whether it supports external relay.\n\n- A way to push external configuration to the paired side, and tracking of external relay.\n\n- A maximum pairing age: a call still in progress when the pairing reaches that age fails with a message saying so.\n\n**Why**\n\nThis only matters if you use local pairing. The clearest visible change is that a long-lived pairing can now end a call in progress once it reaches its maximum age.\n\n- Area: Extension Pairing\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}