[Bug] Plugin output style not discovered or activated when plugin is enabled
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Output styles provided by a plugin are not discovered and do not appear in the /config output style picker, regardless of how the plugin is enabled (either via enabledPlugins in settings.json or manually through the plugin manager).
Because the style never appears in the picker, force-for-plugin: true cannot activate it either.
What Should Happen?
When a plugin is enabled and contains an output-styles/ directory with a valid .md output style file, that style should appear in the /config output style picker. If the style's frontmatter includes force-for-plugin: true, it should activate automatically for the session without requiring the user to set outputStyle in settings.json.
Error Messages/Logs
Steps to Reproduce
- Create a plugin with a .claude-plugin/plugin.json manifest
- Add an output-styles/ directory inside the plugin containing a .md file with valid output style frontmatter, including force-for-plugin: true
- Enable the plugin - either by adding it to enabledPlugins in .claude/settings.json, or manually via the plugin manager (/plugin)
- Run /reload-plugins - the plugin loads successfully (correct plugin count reported)
- Start a fresh session
- Run /config and navigate to Output style
Result: The custom output style from the plugin is absent from the picker.
Workaround: Explicitly setting "outputStyle": "<style-name>" in settings.json applies the style correctly, confirming the style file itself is valid - only plugin-based discovery is broken.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.161
Platform
Other
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗