Skip to content

chore(cli): document local marketplace naming - #87

Open
hanming5 wants to merge 1 commit into
Factory-AI:mainfrom
hanming5:docs/local-marketplace-naming
Open

hanming5 wants to merge 1 commit into
Factory-AI:mainfrom
hanming5:docs/local-marketplace-naming

Conversation

@hanming5

@hanming5 hanming5 commented Nov 1, 2026

Copy link
Copy Markdown

Summary

When a marketplace is added from a local path, droid registers it under the directory name, not the name field in marketplace.json. The plugins docs and the enterprise plugin registry docs don't say this. Users who follow them and install with <plugin>@<marketplace.json name> hit Marketplace "..." not found.

This PR documents the naming rule where local marketplaces are added, and points to droid plugin marketplace list for the exact registered name.

  • docs/cli/configuration/plugins.mdx: add a note under "From local path"
  • docs/enterprise/enterprise-plugin-registry.mdx: add the naming rule and a matching install example (security-toolkit@company-plugins)
  • Japanese mirrors updated to match

building-plugins.mdx already says "The folder name becomes the marketplace name", so these pages now agree with it.

Notes

This is a docs-only change. Keying the marketplace by the manifest name, or improving the error message, would have to happen in the CLI.

Refs #6

Local-path marketplaces are registered under their directory name, not
the `name` field in marketplace.json. The plugins and enterprise registry
docs did not mention this, so following them led to "Marketplace not
found" errors on install. Document the naming rule and point to
`droid plugin marketplace list` for the exact name.

Refs Factory-AI#6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant