plugin-settings

Per-project plugin settings in Claude Code are configured by creating a .claude/plugin-name.local.md file at your project root and defining YAML frontmatter to control plugin behavior for that specific repository.

Managing per-repo Claude Code plugin configuration is best done using local YAML frontmatter files, allowing teams to ship project-specific settings that activate or deactivate features without editing code.

YAML frontmatter local files control hooks and commands by storing configuration in .claude/plugin-name.local.md, enabling predictable, per-repo customization of Claude Code plugins across multiple repositories.

Claude Code requires a restart for local plugin configuration changes to take effect, as the parsing rules and restart guidance ensure the new YAML frontmatter settings are properly loaded.

To prevent accidental leakage of local plugin settings, you should add the .claude/plugin-name.local.md file to your gitignore, following the secure defaults and gitignore recommendations provided by the configuration framework.

Yes, per-project configuration allows teams to ship plugins with project-specific settings that activate or deactivate features without editing code, simply by defining the desired behavior in the local YAML frontmatter file.