Enabling plugin cause errors in claude settings.json

[edurbs]

After activating any plugin in the 21st desktop UI, when I start the claude doctor in a terminal, it gives error in settings.json

 Invalid Settings
 /home/user/.claude/settings.json
  └ enabledPlugins: Expected record, but received array

The error in json file is here:

...
   "enabledPlugins": [
    "claude-plugins-official:jdtls-lsp",
    "zai-coding-plugins:glm-plan-usage",
    "claude-plugins-official:context7",
    "claude-plugins-official:claude-md-management",
    "claude-plugins-official:code-simplifier"
  ],
...

21st-desktop version: 0.0.84 (linux Zorin OS 18)
Claude Code v2.1.58 (stable)

[CarlDegio]

yes, I found this bug in earlier version. It should be '{}' but not '[]'

[comfan12]

Just here to give this a +1 and add a fully fleshed-out bug report, together with a proposed fix. Cheers!

---

Summary

1Code reads and writes enabledPlugins in ~/.claude/settings.json as a string[].
The format mandated by the [official Claude Code settings spec](https://code.claude.com/docs/en/settings#enabledplugins) is Record<string, boolean> - a map of "plugin@marketplace": true/false entries.

This causes two compounding issues:

1. Read bug: On startup, 1Code incorrectly detects the existing object as "no plugins enabled" and renders all plugins as inactive in the UI - even when they are active in Claude Code.
2. Write bug: As soon as the user makes any change and saves, 1Code writes back a string[], permanently replacing the correctly structured object.

The result: a user who opens 1Code, sees their plugins appear unconfigured, and clicks around to "fix" it will silently corrupt their settings.json.

---

Steps to reproduce

1. Have at least one plugin enabled in Claude Code (e.g. via /plugin marketplace install). Confirm ~/.claude/settings.json contains an enabledPlugins object.
2. Open 1Code. Observe that all plugins appear as disabled in the UI, despite being active in Claude Code.
3. Add or toggle any plugin in 1Code's settings UI and save.
4. Inspect ~/.claude/settings.json.

Before (correct - written by Claude Code):

{
  "enabledPlugins": {
    "context7@official": true,
    "github@official": true
  }
}

After (written by 1Code - incorrect):

{
  "enabledPlugins": [
    "context7@official",
    "github@official"
  ]
}

---

Root cause

In getEnabledPlugins, the check Array.isArray(settings.enabledPlugins) returns false for a correctly structured object, so the function falls back to []. This causes the UI to display all plugins as inactive:

// Reads the object as empty - UI shows all plugins as off
const plugins = Array.isArray(settings.enabledPlugins)
  ? (settings.enabledPlugins as string[])
  : []  // <-- always hits this branch for a valid settings.json

When the user subsequently saves any change, setPluginEnabled writes a string[] back to disk:

settings.enabledPlugins = enabledPlugins  // writes string[], discarding the object

This conflicts with the [official Claude Code settings spec](https://code.claude.com/docs/en/settings#enabledplugins), which defines enabledPlugins as an object at all scopes (user, project, local, managed):

{
  "enabledPlugins": {
    "plugin-name@marketplace-name": true,
    "other-plugin@marketplace-name": false
  }
}

This is also confirmed by the [official JSON schema at SchemaStore](https://json.schemastore.org/claude-code-settings.json).

---

Expected behavior

• On open, 1Code correctly reads the existing enabledPlugins object and reflects the active plugin state in the UI.
• On save, enabledPlugins is written back as Record<string, boolean>. Enabling a plugin sets its key to true; disabling removes the key (or sets it to false).

---

Suggested fix

function getEnabledPlugins(settings: Record<string, unknown>): Record<string, boolean> {
  const raw = settings.enabledPlugins
  if (raw && typeof raw === "object" && !Array.isArray(raw)) {
    return raw as Record<string, boolean>
  }
  return {}
}

function setPluginEnabled(
  settings: Record<string, unknown>,
  pluginSource: string,
  enabled: boolean
): void {
  const plugins = getEnabledPlugins(settings)
  if (enabled) {
    plugins[pluginSource] = true
  } else {
    delete plugins[pluginSource]
  }
  settings.enabledPlugins = plugins
}

The cache invalidation logic (invalidateEnabledPluginsCache) can remain as-is - only the read/write format needs to change.

---

References

• Claude Code settings docs - enabledPlugins
• [Official JSON schema (SchemaStore)](https://json.schemastore.org/claude-code-settings.json)
• Affected file: claude-settings.ts