{"version":"2.1.299","anchor":"device-bridge-tool-call-telemetry","canonical_anchor":"device-bridge-tool-call-telemetry","heading":"Usage data now records when a tool call waits for a device connection","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/device-bridge-tool-call-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Usage data now records when a tool call waits for a device connection\n\nClaude Code's tool-call usage data now notes whether a call was for a device bridge, how long it waited, and how the wait ended\n\n**What**\n\nWhen Claude Code runs a tool call (one action the model takes, such as reading a file or running a command), it sends usage data about that call back to Anthropic. That data now includes three new details:\n\n- Whether the call was meant for a device bridge, a connection Claude Code uses to reach a computer or device.\n\n- How long, in milliseconds, the call waited for that connection.\n\n- How the wait ended. If the call never waited, this is recorded as not having waited for a computer.\n\n**Why**\n\nThe new details show that a tool call can now pause and wait for a connection to a computer or device before it runs.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}