{"version":"2.1.304","anchor":"scheduled-tasks-gain-optional-plugin-field-auto-mode-and-pe","canonical_anchor":"scheduled-tasks-gain-optional-plugin-field-auto-mode-and-pe","heading":"Changes to scheduled tasks, auto mode and permission prompts","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/scheduled-tasks-gain-optional-plugin-field-auto-mode-and-pe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Changes to scheduled tasks, auto mode and permission prompts\n\nScheduled tasks can name a plugin, and auto mode no longer counts as active when a hook may ask for permission\n\n**Unclear.** When a request counts as person-only, and what the plugin field on a scheduled task does, is not stated.\n\n**What**\n\nSeveral small changes affect when Claude Code asks you something or acts on its own:\n\n- Scheduled tasks can now carry an optional `plugin` field.\n\n- Auto mode, where Claude acts without asking each time, is no longer treated as active when a hook may ask for permission. A hook is a command you configure to run at certain points.\n\n- A permission prompt is now also forced when a request is marked as person-only.\n\n- An automatic reaction to built-in artifacts now respects a setting that hides that artifact from MCP servers (outside tools Claude can connect to).\n\n**Why**\n\nThese change when permission prompts appear and when automatic actions happen.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}