Bug Description
When installing a plugin from a directory-based marketplace, Claude Code adds the plugin to installed_plugins.json but does NOT add it to settings.json enabledPlugins. This requires manual intervention to enable the plugin.
Steps to Reproduce
- Create a directory-based marketplace in
known_marketplaces.json:
"local-dev": {
"source": {"source": "directory", "path": "C:\path\to\marketplace"},
"installLocation": "C:\Users\Me\.claude\plugins\marketplaces\local-dev"
}
- Install a plugin:
claude plugin install rlm@local-dev
- Check
~/.claude/installed_plugins.json - plugin is listed ✓
- Check
~/.claude/settings.json enabledPlugins - plugin is NOT listed ✗
- Plugin hooks don't work until manually added to
settings.json
Expected Behavior
Plugin should be auto-enabled in settings.json just like GitHub marketplace plugins.
Actual Behavior
Plugin is installed but not enabled. Manual edit required:
"enabledPlugins": {
"rlm@local-dev": true
}
Environment
- Claude Code Version: v2.1.6
- OS: Windows
Workaround
Manually add plugin to settings.json after installation.
Impact
Plugins appear "installed" but don't function, causing confusion. Hooks silently fail to load without clear error messages.
Bug Description
When installing a plugin from a directory-based marketplace, Claude Code adds the plugin to
installed_plugins.jsonbut does NOT add it tosettings.jsonenabledPlugins. This requires manual intervention to enable the plugin.Steps to Reproduce
known_marketplaces.json:claude plugin install rlm@local-dev~/.claude/installed_plugins.json- plugin is listed ✓~/.claude/settings.jsonenabledPlugins- plugin is NOT listed ✗settings.jsonExpected Behavior
Plugin should be auto-enabled in
settings.jsonjust like GitHub marketplace plugins.Actual Behavior
Plugin is installed but not enabled. Manual edit required:
Environment
Workaround
Manually add plugin to
settings.jsonafter installation.Impact
Plugins appear "installed" but don't function, causing confusion. Hooks silently fail to load without clear error messages.