{"version":"2.1.304","anchor":"plugin-scheduled-wakeupsqueued-commands-carry-plugin-attrib","canonical_anchor":"plugin-scheduled-wakeupsqueued-commands-carry-plugin-attrib","heading":"Scheduled wakeups and queued messages now record which plugin made them","tier":"internal","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/plugin-scheduled-wakeupsqueued-commands-carry-plugin-attrib","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Scheduled wakeups and queued messages now record which plugin made them\n\nScheduled wakeups and queued messages can now carry a plugin name, and messages from people are taken from the queue first\n\n**What**\n\nClaude Code can schedule a wakeup, meaning a future turn, and keep a queue of waiting messages. Both can now record the name of the plugin that created them. When a session is resumed, a waiting wakeup whose plugin name is not valid is not scheduled again.\n\nQueued commands from plugins or coordinators are handled separately. When picking the next queued message, Claude Code prefers messages from a person, an observer, or a coordinator or peer that is not tied to a plugin.\n\n**Why**\n\nThis lays groundwork for plugins that schedule turns of their own.\n\n- Area: Scheduled Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}