Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

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

Use it now
Useful4 Signal0
Plugins

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

/plugin/reload-plugins
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →