{"version":"2.1.277","anchor":"remote-tools-serving-stubbed-out-with-external-build-reaso","canonical_anchor":"remote-tools-serving-stubbed-out-with-external-build-reaso","heading":"Remote-tools serving stubbed out with 'external_build' reason in this bundle","tier":"soon","area":"Remote Machines","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/remote-tools-serving-stubbed-out-with-external-build-reaso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Remote-tools serving stubbed out with 'external_build' reason in this bundle\n\nRemote-tools serving now always reports 'external_build' as unavailable in this bundle\n\n**Unclear.** The finding doesn't say what 'external_build' means in context or whether this is a temporary state during development.\n\n**What**\n\nThe function responsible for populating the list of served remote tools (part of the device-bridge feature that connects tools across devices) now always returns `servedToolsUnavailable: \"external_build\"`, no matter what's passed to it. Its signature also expanded from three parameters to five, though the two new parameters aren't currently used.\n\n**Why**\n\nIn this build, remote tools served through this path are unconditionally reported as unavailable because of being an external build, rather than based on any actual check. This looks like scaffolding for a feature that isn't wired up yet in this bundle.\n\n- Area: Remote Machines\n- Names: `external_build`\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}