Claude Code Plugins From Other Projects Appear in Current Project with Misleading Error

What this error means

Failed to uninstall plugin: Plugin is enabled at project scope (.claude/settings.json, shared with your team). To disable just for you: claude plugin disable --scope local — but running the command fails with 'already disabled at local scope' is a Claude Code failure pattern reported for developers trying to fix claude code plugin scope error where plugins from other projects leak into current project ui. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #59629 on anthropics/claude-code: plugins installed with —scope project in one project incorrectly appear in Manage Plugins UI of unrelated projects. Error message misleadingly claims plugin is enabled via .claude/settings.json when no such file exists. Affects Claude Code paid users on Windows/VSCode.

Common causes

• GitHub issue #59629 on anthropics/claude-code: plugins installed with —scope project in one project incorrectly appear in Manage Plugins UI of unrelated projects. Error message misleadingly claims plugin is enabled via .claude/settings.json when no such file exists. Affects Claude Code paid users on Windows/VSCode.

Quick fixes

1. Confirm the exact error signature matches Failed to uninstall plugin: Plugin is enabled at project scope (.claude/settings.json, shared with your team). To disable just for you: claude plugin disable --scope local — but running the command fails with 'already disabled at local scope'.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/59629

Evidence note: GitHub issue #59629 on anthropics/claude-code: plugins installed with —scope project in one project incorrectly appear in Manage Plugins UI of unrelated projects. Error message misleadingly claims plugin is enabled via .claude/settings.json when no such file exists. Affects Claude Code paid users on Windows/VSCode.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact Failed to uninstall plugin: Plugin is enabled at project scope (.claude/settings.json, shared with your team). To disable just for you: claude plugin disable --scope local — but running the command fails with 'already disabled at local scope' text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without Failed to uninstall plugin: Plugin is enabled at project scope (.claude/settings.json, shared with your team). To disable just for you: claude plugin disable --scope local — but running the command fails with 'already disabled at local scope'.