{"version":"2.1.265","anchor":"cli-teleport-relay-ended-replaces-generic-upgrade-teleport-c","canonical_anchor":"cli-teleport-relay-ended-replaces-generic-upgrade-teleport-c","heading":"cli_teleport_relay_ended replaces generic upgrade_teleport_cache logging for device_tool_requested","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/cli-teleport-relay-ended-replaces-generic-upgrade-teleport-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### cli_teleport_relay_ended replaces generic upgrade_teleport_cache logging for device_tool_requested\n\nTeleport relay reverts caused by a requested device tool now log a dedicated event instead of a generic one\n\n**What**\n\nWhen a teleport relay (an internal connection-forwarding mechanism) reverts specifically because a `device_tool_requested`, Claude Code now logs a dedicated `cli_teleport_relay_ended` event at info level, instead of the previous generic `upgrade_teleport_cache` telemetry event.\n\n**Why**\n\nThis makes it possible to distinguish this specific cause of a relay ending from other, unrelated cache-upgrade events in telemetry, which should make diagnosing relay behavior clearer.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}