Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] CLI docs and plugin guides omit `--plugin-url` for session-scoped remote plugin ZIP loading [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56488•Fetched 2026-05-06 06:26:43
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×5

Code Example

claude --plugin-url https://example.com/my-plugin.zip
RAW_BUFFERClick to expand / collapse

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:

PageLine(s)Context
https://code.claude.com/docs/en/cli-reference86--plugin-dir is documented for local directory / local .zip loading, but there is no --plugin-url entry
https://code.claude.com/docs/en/plugins118-121Quickstart only shows claude --plugin-dir ./my-first-plugin
https://code.claude.com/docs/en/plugins296-315Local testing guidance only explains --plugin-dir and repeated local plugin paths
https://code.claude.com/docs/en/plugins-reference709-741Plugin 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.

extent analysis

TL;DR

Add documentation for the --plugin-url <url> flag to the CLI reference and plugin docs to cover remote ZIP loading.

Guidance

  • Update the CLI reference to include --plugin-url <url> with a short example, such as claude --plugin-url https://example.com/my-plugin.zip.
  • Revise the plugin docs to clearly distinguish between --plugin-dir for local directories and local .zip archives, and --plugin-url for remote .zip archives.
  • Consider adding notes on limitations, trust, or scope for URL-loaded plugins to help users choose the right flag.
  • Review the affected pages (CLI reference, plugin docs, and plugin reference) to ensure consistency and accuracy in the updated documentation.

Example

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

This example demonstrates how to use the --plugin-url flag to load a plugin from a remote URL.

Notes

The documentation update should be applied to the specified pages and should be consistent with the existing documentation style and tone.

Recommendation

Apply workaround: Add the missing documentation for --plugin-url <url> to the CLI reference and plugin docs, as this will provide users with the necessary information to use the feature correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#cache issue#memory leak#API versioning#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] CLI docs and plugin guides omit `--plugin-url` for session-scoped remote plugin ZIP loading [1 participants]