{"version":"2.1.323","anchor":"single-paired-peer-sealed-calls-in-the-bridge-client-set","canonical_anchor":"single-paired-peer-sealed-calls-in-the-bridge-client-set","heading":"Groundwork for sending sealed calls to a single paired device","tier":"internal","area":"Paired Devices","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/single-paired-peer-sealed-calls-in-the-bridge-client-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Groundwork for sending sealed calls to a single paired device\n\nClaude Code gains a way to send sealed calls that only go through when exactly one paired device is connected\n\n**What**\n\nClaude Code's connection to paired devices gains a way to send sealed calls. A call is only sent when exactly one paired device is connected. Before sending, it can also require that the device identifies itself with a device ID. It can check what the connected device says it supports.\n\n**Why**\n\nNothing visible uses this yet. It prepares for sending calls to one specific paired device.\n\n- Area: Paired Devices\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}