{"version":"2.1.280","anchor":"remote-control-bridge-failures-now-emit-distinct-telemetry-p","canonical_anchor":"remote-control-bridge-failures-now-emit-distinct-telemetry-p","heading":"Remote-control bridge failures now emit distinct telemetry per failure reason","tier":"internal","area":"Remote Control","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/remote-control-bridge-failures-now-emit-distinct-telemetry-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Remote-control bridge failures now emit distinct telemetry per failure reason\n\nFailures to start the remote-control bridge now report which specific reason caused the failure\n\n**What**\n\nThe remote-control bridge lets Claude Code connect to a remote session. When it fails to start, Claude Code now records which of several specific reasons caused the failure before showing the error:\n\n- `org_policy_denied` \u2014 an organization policy blocked the connection\n\n- `bridge_disabled` \u2014 the bridge feature itself is turned off\n\n- `version_floor` \u2014 the installed version is too old to support it\n\nPreviously, this diagnostic reporting only happened for the org-policy case.\n\n**Why**\n\nRecording the exact failure reason makes it possible to tell these distinct causes apart instead of lumping them together, which helps diagnose why a given connection attempt didn't work.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}