[DOCS] `plugin enable`/`plugin disable` docs still show `--scope` default as `user`

Open 💬 6 comments Opened Feb 19, 2026 by coygeek

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/plugins-reference

Section/Topic

plugin enable and plugin disable option tables for --scope.

Current Documentation

The reference currently states:

-s, --scope <scope> | Scope to enable: user, project, or local | user
-s, --scope <scope> | Scope to disable: user, project, or local | user

What's Wrong or Missing?

Claude Code v2.1.49 changed behavior so plugin enable and plugin disable auto-detect the correct scope when --scope is omitted.

Docs still describe user as the default, which can mislead users about which config file will be modified.

Suggested Improvement

Update both option tables and surrounding prose:

  • Replace default value user with auto-detected (or equivalent wording).
  • Document how scope is inferred when omitted.
  • Add one concrete example showing behavior when a plugin exists in project vs user scope.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/plugins-reference | 532-535, 551-554 | plugin enable/plugin disable tables list user as default scope |

Total scope: 1 page affected

View original on GitHub ↗

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