/plugin TUI cannot add a marketplace plugin to more than one project

Resolved 💬 3 comments Opened Feb 20, 2026 by devinrosen Closed Feb 20, 2026

Environment

  • Claude Code version: 2.1.49
  • Platform: macOS (Darwin 25.3.0)
  • Shell: zsh

Description

When using the /plugin interactive TUI to enable a plugin from a custom marketplace, it works for the first project but fails when trying to enable the same plugin in a second project. The TUI does not allow completing the operation for the second project.

The workaround is manually editing ~/.claude/settings.json to add the plugin entry to enabledPlugins.

Steps to reproduce

  1. Configure a custom marketplace (e.g., a private GitHub-hosted marketplace)
  2. Open Claude Code in Project A
  3. Use /plugin TUI to enable a plugin from the marketplace (e.g., jira@my-marketplace) — this works
  4. Open Claude Code in Project B
  5. Use /plugin TUI to enable the same plugin from the marketplace — this fails

Expected behavior

The /plugin TUI should allow enabling the same marketplace plugin across multiple projects.

Actual behavior

The TUI fails to add the plugin to a second project. The user must manually edit ~/.claude/settings.json to add the plugin.

Workaround

Manually add the plugin to ~/.claude/settings.json:

{
  "enabledPlugins": {
    "plugin-name@marketplace-name": true
  }
}

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗