[Bug] Local scope plugin installation incorrectly checks global state instead of project-specific state

Resolved 💬 3 comments Opened Jan 4, 2026 by nguyenhcp2004 Closed Jan 7, 2026

Bug Description
Bug: Cannot install plugin with local scope in a different project

When I install a plugin with local scope in Project A, I cannot install the same plugin in Project B. The system shows "Plugin is already installed" even though local scope should only apply to the specific project.

Steps to reproduce:

Install a plugin with local scope in Project A:
/plugin install context7@claude-plugins-official --scope local
Navigate to Project B
Try to install the same plugin:
/plugin install context7@claude-plugins-official --scope local
Error: "Plugin 'context7@claude-plugins-official' is already installed"
Expected behavior:
Local scope plugins should be project-specific. Installing a plugin with local scope in Project A should not prevent installation in Project B.

Actual behavior:
The system checks if the plugin is installed globally instead of checking per project path. The only workaround is to manually delete the plugin entry from ~/.claude.json.

Environment Info

  • Platform: win32
  • Terminal: vscode
  • Version: 2.0.76
  • Feedback ID:

Errors

[]

View original on GitHub ↗

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