What extraKnownMarketplaces Actually Does for Your Team
A repo's committed .claude/settings.json declares
extraKnownMarketplaces pointing at your team's plugin catalog. A
teammate clones the repo and trusts the folder for the first time.
What happens automatically at that point?
The correct answer is "The marketplace is registered — plugins still need an explicit install."
Once the folder is trusted, Claude Code registers the marketplace
automatically, with no manual /plugin marketplace add required.
But registering the catalog does not, by itself, install any
externally-sourced plugin from it for every teammate — each plugin
still needs an explicit install step (or the project can also list it
in enabledPlugins to complete the install). This is a deliberate
safety property: a repo can advertise what plugins the team uses
without silently executing anyone's install of unreviewed code.
The distractors overstate or understate what happens: plugins don't auto-install just because the marketplace is known; nothing here requires an org admin's separate approval step; and registration isn't tied to who authored the repo — it applies to any teammate who trusts the folder.
Share this question