{"version":"2.1.277","anchor":"new-prompt-source-classification-for-message-origin-telemetr","canonical_anchor":"new-prompt-source-classification-for-message-origin-telemetr","heading":"New prompt-source classification for message origin telemetry","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/new-prompt-source-classification-for-message-origin-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### New prompt-source classification for message origin telemetry\n\nInternal telemetry now classifies where each message came from into one of nine categories\n\n**What**\n\nClaude Code now sorts every incoming message into one of nine origin categories for internal telemetry: `human`, `sdk`, `scheduled`, `task_notification`, `auto_continuation`, `peer`, `host_synthetic`, `system`, or `unknown`. It works this out from more detailed signals than before, including what woke the session up and specific origin types like a scheduled trigger, a peer sending a message, or a relay between projects.\n\n**Why**\n\nThis is internal bookkeeping used for telemetry rather than something a user configures directly. Sorting messages this precisely lets Claude Code's own systems tell apart, for example, a message a human typed from one generated by a scheduled job or forwarded from another session.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}