{"version":"2.1.246","anchor":"remote-tool-discovery-outcomes-are-now-sent-as-telemetry","canonical_anchor":"remote-tool-discovery-outcomes-are-now-sent-as-telemetry","heading":"Remote tool discovery outcomes are now sent as telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/remote-tool-discovery-outcomes-are-now-sent-as-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Remote tool discovery outcomes are now sent as telemetry\n\nWhether remote device tools were found is now reported in first-party telemetry.\n\n**What**\n\nThe event that records whether device-bridge remote tools were found (`list_failed`, `listed_empty`, `no_bridge_connection`) already fired but was not on the first-party allowlist; it has been added, so those outcomes now leave the client. It follows the usual first-party telemetry opt-out.\n\n**Evidence**\n\n`tengu_remote_tool_targets`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}