{"version":"2.1.295","anchor":"machine-plugin-key-load-records-policy","canonical_anchor":"machine-plugin-key-load-records-policy","heading":"New check on plugin settings loaded from machine-level files","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/machine-plugin-key-load-records-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### New check on plugin settings loaded from machine-level files\n\nClaude Code now checks plugin-related settings that come from settings files users cannot write to\n\n**Unclear.** What Claude Code does with the result of this check is not stated.\n\n**What**\n\nClaude Code now has a check on settings that were loaded from places a normal user cannot edit, such as files an organization manages. The check only looks at plugin-related settings:\n\n- `enabledPlugins`\n\n- `extraKnownMarketplaces`\n\n- `strictKnownMarketplaces`\n\n- `prependPlugins`\n\n- `appendPlugins`\n\n- `policyHelper`\n\n**Why**\n\nThis relates to how plugin settings set by an organization are handled, as opposed to settings a user chose.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}