[DOCS] CLI docs and plugin guides omit `--plugin-url` for session-scoped remote plugin ZIP loading

Resolved 💬 2 comments Opened May 6, 2026 by coygeek Closed May 10, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/cli-reference

Section/Topic

CLI flags and plugin-loading guidance for session-scoped plugin ZIP loading

Current Documentation

No documentation currently exists for --plugin-url <url>.

The closest current docs only describe local-path loading via --plugin-dir:

--plugin-dir | Load a plugin from a directory or .zip archive for this session only. Each flag takes one path. Repeat the flag for multiple plugins: --plugin-dir A --plugin-dir B.zip

The plugin guide also only shows local directory examples:

Run Claude Code with the --plugin-dir flag to load your plugin: claude --plugin-dir ./my-first-plugin

And the plugin CLI reference still describes installation only through marketplaces:

### plugin install Install a plugin from available marketplaces. claude plugin install <plugin> [options]

What's Wrong or Missing?

The v2.1.129 changelog adds --plugin-url <url> to fetch a plugin .zip archive from a URL for the current session, but the docs currently only cover:

  • --plugin-dir for local directories or local .zip archives
  • Marketplace-based plugin installation

That leaves no discoverable documentation for the new remote ZIP workflow: users reading the CLI reference or plugin docs cannot learn that --plugin-url exists, what syntax it uses, or when to choose it instead of --plugin-dir.

Suggested Improvement

Add --plugin-url <url> to the CLI reference with a short example such as:

claude --plugin-url https://example.com/my-plugin.zip

Then update the plugin docs to distinguish the session-scoped loading paths clearly:

  • --plugin-dir for local plugin directories and local .zip archives
  • --plugin-url for remote .zip archives fetched for the current session only

If there are limitations or trust/scope notes for URL-loaded plugins, include them alongside the existing --plugin-dir guidance so users can choose the right flag.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/cli-reference | 86 | --plugin-dir is documented for local directory / local .zip loading, but there is no --plugin-url entry |
| https://code.claude.com/docs/en/plugins | 118-121 | Quickstart only shows claude --plugin-dir ./my-first-plugin |
| https://code.claude.com/docs/en/plugins | 296-315 | Local testing guidance only explains --plugin-dir and repeated local plugin paths |
| https://code.claude.com/docs/en/plugins-reference | 709-741 | Plugin CLI reference covers marketplace install flows only and does not cross-reference a session-scoped remote ZIP flag |

Total scope: 4 page sections affected

Version context: This gap appears against the v2.1.129 changelog entry that adds --plugin-url <url> for loading a plugin .zip archive from a URL for the current session.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗