enabledPlugins in settings.local.json silently ignored unless key also exists in settings.json

[kitaekatt]

Note: This is a re-filing of #26150, which was incorrectly closed as a duplicate of #24657. These are different bugs:

• SessionStart hooks fire for disabled plugins (settings.local.json override ignored) #19893: enabledPlugins exists in both scopes, but local override (true → false) doesn't suppress hook execution
• This issue: enabledPlugins exists only in settings.local.json — the key is absent from settings.json entirely, causing local values to be silently dropped during merge

Description

enabledPlugins defined in settings.local.json has no effect unless enabledPlugins also exists as a key in settings.json. This contradicts the documented settings merge behavior where local scope settings should apply independently and override broader ones.

The docs state:

Settings are merged, with more specific settings adding to or overriding broader ones.

And explicitly list enabledPlugins as valid in user, project, and local scopes.

For example, a user who enables plugins only in settings.local.json will see the /plugin Marketplaces tab correctly report their marketplace with plugins available (e.g., "11 available"), the Discover tab report "All available plugins are already installed," and the Installed tab report "No plugins or MCP servers installed" — all at the same time. There are no errors — plugins silently fail to load, and the only diagnostic signal is three tabs contradicting each other.

100% Reproduction

Setup: Install any plugin from a marketplace so it appears in installed_plugins.json.

Case 1: Local-only enabledPlugins (fails)

1. Remove enabledPlugins from ~/.claude/settings.json entirely
2. Add enabledPlugins to ~/.claude/settings.local.json with plugins set to true
3. Restart Claude Code
4. /plugin > Installed tab: "No plugins or MCP servers installed"
5. /plugin > Discover tab: "All available plugins are already installed"
6. Plugin skills/hooks/commands do not load

Case 2: Local overrides user (works)

1. Set enabledPlugins in ~/.claude/settings.json with all plugins false
2. Set enabledPlugins in ~/.claude/settings.local.json with all plugins true
3. Restart Claude Code
4. /plugin > Installed tab: All plugins shown and enabled
5. Plugin skills/hooks/commands load correctly

Root Cause

The settings merge for enabledPlugins only applies overrides to an existing key. If enabledPlugins is absent from settings.json, the local scope values are silently dropped rather than being introduced into the merged result.

Impact

• Users who configure enabledPlugins exclusively in settings.local.json (as the docs suggest is valid) get silently broken plugins with no error
• The Discover and Installed tabs show contradictory information with no diagnostic signal
• Workaround: ensure enabledPlugins exists in settings.json (even as {}), then local overrides work

Environment

• Claude Code version: 1.0.33+
• Platform: Linux (Ubuntu), also likely affects macOS/Windows

[github-actions]

Found 3 possible duplicate issues:

1. enabledPlugins in settings.local.json silently ignored unless key also exists in settings.json #25086
2. enabledPlugins in settings.local.json silently ignored unless key also exists in settings.json #26150
3. enabledMcpjsonServers in .claude/settings.local.json is ignored #24657

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[technicalpickles]

Still reproducing on 1.0.41 (macOS, Opus 4.6). Adding some context that might help triage, cuz the failure mode is weirder than "plugins don't load."

Skills load. Hooks don't. When enabledPlugins only exists in settings.local.json, plugin skills still show up in the system prompt and the skills list. But hooks defined in hooks/hooks.json never fire. So the plugin looks like it's working until you notice your PreToolUse hooks are doing nothing. No errors, no warnings. Just silence.

claude plugin list --json reports enabled: false too. Any plugin that calls claude plugin list at runtime to check its own status or discover other enabled plugins sees enabled: false, even though skills from that same plugin are loaded and in the prompt. So plugins that do runtime discovery based on enabled state silently break.

How people actually hit this: claude plugin install --scope local. That's the default for project-scoped installation, and it's what plugin managers use. So if you install plugins through the documented project-scoped flow, you hit this automatically unless you also happen to have enabledPlugins (even just {}) in your global ~/.claude/settings.json.

The workaround in this issue works (ensure the key exists globally). But the partial-load behavior (skills yes, hooks no, plugin list says disabled) is particularly rough to debug since there's no single consistent signal. Three different subsystems give you three different answers about whether your plugin is enabled.