{"version":"2.1.280","anchor":"new-session-initiator-wakeup-source-telemetry-categories","canonical_anchor":"new-session-initiator-wakeup-source-telemetry-categories","heading":"New session-initiator \/ wakeup-source telemetry categories","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-session-initiator-wakeup-source-telemetry-categories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New session-initiator \/ wakeup-source telemetry categories\n\nNew telemetry categories record why and how a session was started or woken up\n\n**What**\n\nClaude Code now records, in telemetry, a category explaining what triggered a session to start. The options include:\n\n- `user`\n\n- `scheduled-task`\n\n- `sleep-auto-resume`\n\n- `quit-auto-resume`\n\n- `remote-restart-auto-resume`\n\n- `ci-monitor`\n\n- `dispatch`\n\n- `side-session-brief`\n\n- `side-session-start`\n\n- `side-session-wake`\n\n- `other`\n\nA separate `wakeup_source` field records whether a wakeup came from `loop_wakeup` or `schedule_wakeup`.\n\n**Why**\n\nThis gives more detailed visibility into how sessions get started or resumed, whether by a person, a scheduled task, auto-resume after sleep or a quit, or other automated triggers.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}