{"version":"2.1.268","anchor":"chrome-devtools-bridge-now-pushes-external-config-to-every-c","canonical_anchor":"chrome-devtools-bridge-now-pushes-external-config-to-every-c","heading":"Chrome DevTools bridge now pushes external config to every connected peer, not just one","tier":"notice","area":"Chrome & Browser","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/chrome-devtools-bridge-now-pushes-external-config-to-every-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Chrome DevTools bridge now pushes external config to every connected peer, not just one\n\nChrome DevTools bridge now pushes config updates to all connected devices, not just the selected one\n\n**What**\n\nThe bridge relay client used for the Chrome DevTools connection gained two new methods: `pushExternalConfigToPeer(deviceId, config)` and `pushExternalConfigToAllPeers(config)`. Messages sent over the bridge now carry a `target_device_id`. When a pairing event ('paired') occurs, the client now calls `pushExternalConfigToAllPeers()` to update every connected peer, instead of only updating whichever device was currently selected. A newly connected peer also receives its own targeted push.\n\n**Why**\n\nThis keeps configuration consistent across every connected device rather than only the one currently selected, which matters when more than one device is bridged at once.\n\n- Area: Chrome & Browser\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}