{"version":"2.1.288","anchor":"telemetry-fields-for-tool-use-id-and-transport","canonical_anchor":"telemetry-fields-for-tool-use-id-and-transport","heading":"Usage data can now include a tool call id and a connection type","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/telemetry-fields-for-tool-use-id-and-transport","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Usage data can now include a tool call id and a connection type\n\nClaude Code's usage data now keeps `tool_use_id` and `transport` fields, with `transport` limited to bridge, native or other\n\n**Unclear.** It is not clear which usage events carry these fields or what `bridge` and `native` refer to.\n\n**What**\n\nClaude Code sends usage data (telemetry) about how it is used, and it cleans that data before it is sent. The cleaning step now handles two more fields:\n\n- `tool_use_id`, an identifier for a single tool call. A tool call is one action Claude takes, such as reading a file.\n\n- `transport`, which is kept only if it is `bridge` or `native`. Any other value is recorded as `other`.\n\n**Why**\n\nThis shows which extra details can now appear in usage data. The connection type is limited to a few fixed values, so nothing unexpected passes through that field.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}