Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

Installed plugins activate in place instead of waiting for /reload-plugins

Plugins you install from /plugin now activate immediately instead of making you run /reload-plugins.

Use it now New Features
JSON All of v2.1.221
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.221,
What probably matters to youSection of the release
What

Finishing an install from the /plugin flow now reloads plugins in the running session and tells you the result, so a freshly installed plugin is usable without a separate reload step.

Details
  • Shows an "Activating plugin…" spinner while the in-session reload runs.
  • Completion message reports the outcome: " Plugin is now active." on success, " The plugin couldn't be loaded — see /plugin for details." on a load error.
  • Falls back to " Run /reload-plugins to apply." only when activation cannot be attempted, including when the live plugin-state getter is not available.
  • Activation is skipped, falling back to reload-required, when the reload reports wouldInvalidateCache, i.e. it would bust the prompt cache.
  • No flag guards this; it is reachable for everyone on this build.
Usage
/plugin
Evidence

Plugin is now active.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/plugin/reload-plugins
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged /plugin install to refresh a stale marketplace catalog and retry before reporting a plugin not found

See this entry in the whole of v2.1.221 →

Feedback