{"version":"2.1.140","anchor":"marketplace-autoupdate-synced-from-settings","canonical_anchor":"marketplace-autoupdate-synced-from-settings","heading":"Marketplace autoUpdate Synced from Settings","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140\/e\/marketplace-autoupdate-synced-from-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140","markdown":"### Marketplace `autoUpdate` Synced from Settings\n\n**What**\n\nThe `autoUpdate` setting for known marketplaces can now be centrally managed via `managed-settings.json`, the `--settings` flag, or an `--add-dir` directory's settings file.\n\n**Details**\n\n- Claude Code checks all settings layers in priority order. If any layer specifies `autoUpdate` for a marketplace, that value is synced to the persisted marketplace config.\n- Log message: `\"Synced autoUpdate=<value> from settings for marketplace: <name>\"`.\n- The source of the override (managed settings, `--settings` flag, or add-dir settings) is reported if the user asks to modify it: \"\u2026can't be changed here. Update that settings source (or ask your admin to) instead.\"\n\n**Evidence**\n\n`Lr7()` function (search for `\"Synced autoUpdate=\"`)"}