{"version":"2.1.319","anchor":"tool-use-telemetry-and-thread-counts-in-resource-samples","canonical_anchor":"tool-use-telemetry-and-thread-counts-in-resource-samples","heading":"Usage reports always list the tools used, and process samples count threads","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/tool-use-telemetry-and-thread-counts-in-resource-samples","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Usage reports always list the tools used, and process samples count threads\n\nClaude Code's usage reports now always include which tools were used, and its process samples now record a thread count\n\n**What**\n\nTelemetry is the usage information Claude Code sends back about how it runs. Two parts of it changed:\n\n- The list of tools used is now always reported. Before, it was sent only when a certain condition held, and was empty otherwise.\n\n- Samples of the Claude Code process now include the number of threads, which are the separate lines of work a program runs at the same time.\n\n**Why**\n\nThis changes what Claude Code reports about a session: the tools used are included in every case.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}