Unclear It is not clear what condition makes an install fail with "replace_unavailable".
What
claude plugin install in replace mode can now stop with the failure code "replace_unavailable".
More refusal codes exist for switching a plugin from one marketplace (a source you install plugins from) to another, such as "replace_needs_fresh_listing" and "invalid_plugin_id". Most of that switching path is switched off in this build, so you are unlikely to see them.
Why
This looks like groundwork for moving an installed plugin between marketplaces.
Names in the bundleclaude plugin install
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude plugin install, on Claude Code changelog.
* Fixed a failed first `claude plugin install` leaving the plugin enabled and recorded when a dependency's version range could not be metchangelog see the edit
Added since
A small documentation edit on Install and manage plugins touched a line naming claude plugin install after this was published.
* **Project scope**: the plugin is enabled for everyone who works in this repository. The entry goes in `.claude/settings.json`, which you commit. Committing that entry turns the plugin on for your collaborators but doesn't download it to …plugins/install see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear what condition makes an install fail with "replace_unavailable".
Anthropic's documentation agrees
A small documentation edit on Install and manage plugins touched a line naming claude plugin install after this was published.