{"version":"2.1.288","anchor":"per-turn-timing-capability-and-new-telemetry-event-names","canonical_anchor":"per-turn-timing-capability-and-new-telemetry-event-names","heading":"New usage-reporting events for language server requests and tool progress","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/per-turn-timing-capability-and-new-telemetry-event-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### New usage-reporting events for language server requests and tool progress\n\nTwo new usage-reporting event names appear, one for language server requests and one for tool progress heartbeats\n\n**Unclear.** Where these events are sent from and whether anything controls them is not established.\n\n**What**\n\nClaude Code's list of telemetry events (the usage data it reports back) gains two names: `lsp_request` and `heartbeat_tool_progress`. LSP refers to language servers, the helper programs that give code intelligence such as go-to-definition. The `per_turn_timing` capability now also appears in a further capability list.\n\n**Why**\n\nThe names suggest Claude Code can report on language server requests and send periodic progress signals while a tool is still running.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}