Use it now
--plugin-dir help text now documents that a folder of plugins can be passed
What
The command-line help text for the --plugin-dir flag now explains that it can also load a directory containing multiple plugins, with each one loaded as a separate child plugin.
Why
This makes it clear that --plugin-dir A --plugin-dir B.zip can be used to load a folder of plugins at once, not just a single plugin directory or archive, requiring Claude Code v2.1.265 or later.
Names in the bundle--plugin-dir
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.
Added since
A small documentation edit on Create plugins touched a line naming --plugin-dir after this was published.
Trying the plugin with `--plugin-dir` tells you it can work. To find out how often Claude actually reaches for it and gets the right result, run it against a set of test prompts with [`claude plugin eval`](/docs/en/plugin-evals). Each prom…plugins see the edit
Confirmed since
Anthropic's documentation has since written up --plugin-dir, on Discover and install prebuilt plugins through marketplaces.
* Edits to a plugin you loaded with [`--plugin-dir`](/docs/en/plugins#test-your-plugins-locally) while you develop itdiscover-plugins see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --plugin-dir, on Discover and install prebuilt plugins through marketplaces.
Anthropic's release notes agree
Added support for pointing --plugin-dir at a folder of plugins: each child folder with a manifest loads, and children added or removed while…