{"version":"2.1.287","anchor":"marketplace-autoupdate-taken-only-from-trusted-settings-for","canonical_anchor":"marketplace-autoupdate-taken-only-from-trusted-settings-for","heading":"Project settings can no longer change auto-update for the official marketplace","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/marketplace-autoupdate-taken-only-from-trusted-settings-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Project settings can no longer change auto-update for the official marketplace\n\nAuto-update for the official plugin marketplace is now read only from user, `--settings` and managed settings, not from project files\n\n**Unclear.** It is not fully confirmed which built-in marketplace entry this applies to or the exact condition that triggers it.\n\n**What**\n\nA plugin marketplace is a catalogue that Claude Code installs plugins from, and its `autoUpdate` setting controls whether it keeps itself up to date. For the official built-in marketplace, Claude Code now takes `autoUpdate` only from:\n\n- User settings\n\n- Settings passed with `--settings`\n\n- Managed settings (set by an organisation administrator)\n\nValues for it in project settings, local settings, or settings in a directory added with `--add-dir` are ignored. Claude Code writes a debug log line when it ignores one.\n\n**Why**\n\nA repository you open can no longer switch off auto-update for the official marketplace through its own settings files. Only settings you or your organisation control decide it.\n\n- Area: Plugins\n- Names: `autoUpdate`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}