{"version":"2.1.307","anchor":"command-lifecycle-started-events-now-carry-wakeup-source-a","canonical_anchor":"command-lifecycle-started-events-now-carry-wakeup-source-a","heading":"\"Started\" events now say when a command came from a scheduled wakeup","tier":"internal","area":"Message Queue","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/command-lifecycle-started-events-now-carry-wakeup-source-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### \"Started\" events now say when a command came from a scheduled wakeup\n\nWhen a queued command starts, its event now includes what woke it and when it was scheduled for, if it came from a scheduled wakeup\n\n**What**\n\nClaude Code records an event when a queued command starts running. If the command came from a scheduled wakeup, the event now also includes what woke it and the time it was scheduled for. Previously it carried only the command's ID. Commands without an ID are now skipped.\n\n**Why**\n\nIn a session's events, commands started by a scheduled wakeup can now be told apart from commands you typed.\n\n- Area: Message Queue\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}