{"version":"2.1.304","anchor":"a-mod-enable-prompt-text-added","canonical_anchor":"a-mod-enable-prompt-text-added","heading":"New prompt asks before turning on mods that Claude writes","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/a-mod-enable-prompt-text-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### New prompt asks before turning on mods that Claude writes\n\nClaude Code has a new prompt asking whether to turn on mods Claude writes in a session, with a warning that a mod is code running with your access\n\n**Unclear.** What causes this prompt to appear is not stated.\n\n**What**\n\nClaude Code now contains a prompt that asks: \"Turn on the mods Claude writes in this session?\" A mod here is a piece of code Claude writes during the session that extends Claude Code as a plugin. The prompt warns that a mod is code and runs with your access, which means it can do whatever you can do on your computer. It points you to `\/plugin`, the command for managing plugins.\n\n**Why**\n\nThis is a consent step: before code that Claude wrote is allowed to run as a plugin, you are asked to agree, and told plainly what agreeing means.\n\n- Area: Plugins\n- Names: `\/plugin`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}