configured-agent

Centralize per-project plugin settings by creating a YAML frontmatter configuration file under the .claude directory. This approach stores all plugin configurations locally, enabling consistent behavior and easier maintenance across different projects.

Create a file named .claude/configured-agent.local.md with YAML frontmatter to manage plugin state. Include fields like enabled and description to control feature toggles and safely persist settings for your specific project environment.

The best way to handle per-project plugin configuration is using a dedicated local YAML frontmatter file. This method prevents scattered settings by centralizing customization, state management, and feature toggles in one structured location.

Yes, changing local Claude Code plugin settings in the YAML frontmatter file typically requires a restart. The configuration provides guidance on restart requirements and Gitignore recommendations to ensure local settings are safely managed and not committed.

Security considerations for local configuration files include adding the settings file to Gitignore to prevent exposing sensitive project configurations. The YAML frontmatter approach provides clear guidance on safely enabling, muting, and persisting plugin state without compromising security.

Yes, you can use YAML frontmatter fields like enabled and description to enable, mute, and persist plugin features on a per-project basis. This configuration method provides granular control over plugin behavior tailored to each project's requirements.