{"version":"2.1.268","anchor":"terminal-identityversion-now-reported-in-a-startup-telemetr","canonical_anchor":"terminal-identity-xtversion-response-now-normalizedclassi","heading":"Terminal identity detection now feeds startup telemetry","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/terminal-identityversion-now-reported-in-a-startup-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Terminal identity detection now feeds startup telemetry\n\nClaude Code now identifies your terminal app and version from its XTVERSION reply and reports it in startup telemetry.\n\n**Unclear.** Nothing has been read yet about how the `tengu_terminal_probe` gate itself is set for any account.\n\n**What**\n\n- A new classifier reads the raw XTVERSION terminal-identification reply your terminal sends back and matches it against a list of known terminal apps (iTerm2, ghostty, WezTerm, tmux, kitty, and others) plus several version-format patterns.\n\n- If the terminal isn't recognized, it's bucketed as \"other\"; if there's no reply at all, it's bucketed as \"no_reply\".\n\n- The result is packaged as an `xtversion` field inside a `tengu_terminal_probe` telemetry event sent at startup.\n\n**Why** This lets Claude Code understand which terminal emulators and versions people actually use, without sending raw, potentially inconsistent terminal strings \u2014 only normalized values reach telemetry.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}