{"version":"2.1.304","anchor":"session-crons-can-carry-a-plugin-name","canonical_anchor":"session-crons-can-carry-a-plugin-name","heading":"Scheduled tasks in a session now record which plugin created them","tier":"internal","area":"Scheduled Tasks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/session-crons-can-carry-a-plugin-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Scheduled tasks in a session now record which plugin created them\n\nSession scheduled tasks now store the plugin that created them, and on resume a task with an invalid plugin name is skipped\n\n**What**\n\nScheduled tasks in a session (prompts set to run at set times) now record the plugin that created them, if any. Plugins are add-ons that extend Claude Code.\n\nWhen you resume a session, a scheduled task whose stored plugin name does not meet the rules for a valid name is left out.\n\n**Why**\n\nThis lets plugins own the scheduled tasks they set up.\n\n- Area: Scheduled Tasks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}