{"version":"2.1.302","anchor":"remote-tools-announce-adds-device-bridge-server-present-tele","canonical_anchor":"remote-tools-announce-adds-device-bridge-server-present-tele","heading":"Remote tool handling checks for a device bridge and can wait for an attach announcement","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/remote-tools-announce-adds-device-bridge-server-present-tele","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Remote tool handling checks for a device bridge and can wait for an attach announcement\n\nPassthrough and remote tool announcements now check whether a device bridge server is present, and an 'attached' result can wait for the computer to announce\n\n**What**\n\nRemote tools are tools that run on another machine. A device bridge is a connection to a computer or device that provides such tools.\n\n- When a request carries passthrough MCP tools, tools forwarded from elsewhere, a new check `deviceBridgeServerPresent()` runs and its result is passed on.\n\n- The announcement of remote tools now records whether a device bridge server is present, through a new `deviceBridgeServerPresent` option.\n\n- A new helper can hold back a tool result with the state \"attached\" for up to a time limit, to wait for the computer's announcement.\n\nWhere these results are used further was not traced.\n\n**Why**\n\nThis affects only setups where a device bridge provides remote tools. Others will see no difference.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}