{"version":"2.1.271","anchor":"teleport-device-tool-relay-now-distinguishes-repeated-automa","canonical_anchor":"teleport-device-tool-relay-now-distinguishes-repeated-automa","heading":"Teleport device-tool relay now distinguishes repeated automation-tool requests","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/teleport-device-tool-relay-now-distinguishes-repeated-automa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Teleport device-tool relay now distinguishes repeated automation-tool requests\n\nTeleport's device-tool relay now only reverts on a repeated device-tool request, once automation tools are active\n\n**What**\n\nTeleport (Claude Code's relay for using tools on a connected device) used to revert its relay any time a device-tool call came in. Now it checks whether an automation-tools marker is set on the active teleport session:\n\n- If the marker is not set, any device-tool call still reverts the relay, logged as `device_tool_requested`.\n\n- If the marker is set, only a *repeated* device-tool request from the same message triggers the revert, now logged as `device_tool_request_repeated`, alongside a new `upgrade_relay_end` telemetry event.\n\n**Why**\n\nThis avoids reverting the relay unnecessarily once automation tools are already active, only stepping in when the same message repeats a device-tool request.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}