You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.307,
ImprovementsSection of the release
What
Three small changes in how Claude Code handles plugins, which are add-on packages of commands, tools and settings:
Plugin lists show one particular marketplace (a catalogue plugins are installed from) under a fixed label instead of its own marketplace name.
The confirmation after /plugin disable still names .claude/settings.local.json as the file it wrote to, and now adds the settings scope after that path.
Enabling or disabling a plugin now checks that a synced plugin is not hidden behind another plugin of the same name.
Why
These are mostly wording changes. The scope note makes it clearer where a disable was recorded.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeSelf-hosted runner: Fixed sessions with --use-anthropic-git-proxy committing a .claude/settings.local.json left in the clone by an earlier…
