{"version":"2.1.311","anchor":"new-telemetry-and-debug-names","canonical_anchor":"new-telemetry-and-debug-names","heading":"New internal names for streaming, MCP search and startup timing","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/new-telemetry-and-debug-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### New internal names for streaming, MCP search and startup timing\n\nSeveral new internal event and debug names appear, and one telemetry batching setting was renamed; none changes what you see on its own\n\n**What**\n\nSeveral new internal names appear in this build. They are labels Claude Code uses for its own reporting and debugging, not settings you can change:\n\n- `headless_plain_delta_fast_path` and `mcp_search_redial`, added to a list of event names\n\n- `prompt.paint`, added to a list of interfaces offered to programs that host Claude Code\n\n- `tengu_startup_timing`, a new event about startup that is sent with a site field\n\n- `event_batch_upload`, which replaces `joint_upload` in the settings for how usage reports are grouped before sending\n\n**Why**\n\nThe names point to work on a faster path for streamed output when Claude Code runs without its interactive screen, on reconnecting MCP servers during a tool search, and on measuring how long startup takes. On their own they do not change anything you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}