{"version":"2.1.280","anchor":"new-session-origin-categories-route-to-host-synthetic","canonical_anchor":"new-session-origin-categories-route-to-host-synthetic","heading":"New session-origin categories route to host_synthetic","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-session-origin-categories-route-to-host-synthetic","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New session-origin categories route to host_synthetic\n\nNew internal session-origin types now explicitly map to the host_synthetic category\n\n**Unclear.** The finding does not say what side-session-brief, side-session-start, or side-session-wake correspond to in user-visible terms, only that they route to host_synthetic.\n\n**What**\n\nClaude Code tracks where a session or turn originated from, and internally groups these into broader categories for reporting purposes. Several origin types have been added to the mapping that produces this grouping:\n\n- `side-session-brief`\n\n- `side-session-start`\n\n- `side-session-wake`\n\n- `other`\n\nEach of these now explicitly maps to the `host_synthetic` category, rather than falling into it through a default catch-all case.\n\n**Why**\n\nThis is an internal bookkeeping change. Making the mapping explicit rather than relying on a default case reduces the chance that new origin types get miscategorized in the future, but it should not change anything a user of Claude Code sees or interacts with directly.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}