{"version":"2.1.133","anchor":"better-documentation-for-plugin-setting-precedence","canonical_anchor":"better-documentation-for-plugin-setting-precedence","heading":"Better Documentation for Plugin Setting Precedence","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.133\/e\/better-documentation-for-plugin-setting-precedence","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.133","markdown":"### Better Documentation for Plugin Setting Precedence\n\nThe `enabledPlugins` setting description now documents the precedence order directly: user < project < local < flag < policy.\n\n**Details**\n\n- This makes it clearer why disabling a plugin in user settings may not work when the project re-enables it.\n- The schema description now points users to `.claude\/settings.local.json` for project-specific opt-outs.\n\n**Evidence**\n\nUpdated setting description (search for `\"Settings precedence is user < project < local < flag < policy\"`)."}