{"version":"2.1.281","anchor":"device-bridge-startup-devicemcpquestion-transport-and-an","canonical_anchor":"device-bridge-startup-devicemcpquestion-transport-and-an","heading":"Device bridge startup: deviceMcpQuestion, transport, and an awaited pre-step","tier":"internal","area":"Remote Devices","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/device-bridge-startup-devicemcpquestion-transport-and-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Device bridge startup: deviceMcpQuestion, transport, and an awaited pre-step\n\nConnecting a device bridge now waits for an extra setup step and passes new details to the tool list\n\n**Unclear.** The finding does not say what `deviceMcpQuestion` or the new setup step do.\n\n**What**\n\nWhen a device bridge (a link that exposes tools from a connected device) is set up, it now waits for a new setup step before gathering its tools, and stops if the bridge was shut down in the meantime. It passes two new details, `deviceMcpQuestion` and `transport`, to the list of available tools. Attaching to an existing bridge also passes `deviceMcpQuestion`.\n\n**Why**\n\nA bridge that is stopped during setup no longer carries on registering tools.\n\n- Area: Remote Devices\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}