{"version":"2.1.267","anchor":"session-name-telemetry-now-classifies-theme-into-a-fixed-set","canonical_anchor":"session-name-telemetry-now-classifies-theme-into-a-fixed-set","heading":"Session-name telemetry now classifies theme into a fixed set, defaulting unknown themes to 'custom'","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/session-name-telemetry-now-classifies-theme-into-a-fixed-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Session-name telemetry now classifies theme into a fixed set, defaulting unknown themes to 'custom'\n\nStartup telemetry now reports theme as one of a known set of names, labeling anything else 'custom'\n\n**What**\n\nWhen Claude Code sends startup telemetry, the `theme` field used to report whatever value was set for the theme, verbatim. It now checks that value against a fixed list of known theme names and sends `custom` instead if the configured theme isn't on that list.\n\n**Why**\n\nThis keeps theme telemetry data consistent and easier to analyze, by grouping any non-standard or custom theme configurations under a single label rather than sending arbitrary values.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}