Roll out a plugin to your whole organization changedplugins/org-rollout
Nearest release: v2.1.283, published under an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 18:00 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+9added
Lines−9removed
From line
11
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 11, old and new numbered
/
from line 11
1111
1212> [!NOTE]
1313>
14> * If you want to list a plugin publicly, see [Publish to the directory](/docs/directory/publish)
15> * If you haven't built the plugin yet, see [Build your first plugin](/docs/plugins/quickstart) and [Plugin structure and testing](/docs/plugins/build)
14> * If you want to list a plugin publicly, see [Publish to the directory](/docs/directory/publish.md)
15> * If you haven't built the plugin yet, see [Build your first plugin](/docs/plugins/quickstart.md) and [Plugin structure and testing](/docs/plugins/build.md)
1616
1717## Choose a rollout route
1818
from line 24
2424| Where you set it up | [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory) | Server-managed settings, an MDM policy, or a `managed-settings.json` file |
2525| What you set | An availability for each plugin, such as **Installed by default** or **Required** | `extraKnownMarketplaces` to register your marketplace and `enabledPlugins` to install plugins from it |
2626| Access to your repository | Members need none. Organization sync reads the repository through your organization's GitHub or GitLab connection. | Each machine fetches the marketplace itself. For a private Git repository, it uses the Git credentials already on that machine. |
27| Which components load | Depends on the surface. See [Plugin feature support across platforms](/docs/plugins/platform-support). | Every component |
28| Full setup steps | [Manage plugins for your organization](/docs/plugins/admin) | [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org) in the Claude Code docs |
27| Which components load | Depends on the surface. See [Plugin feature support across platforms](/docs/plugins/platform-support.md). | Every component |
28| Full setup steps | [Manage plugins for your organization](/docs/plugins/admin.md) | [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org) in the Claude Code docs |
2929
3030A plugin on a member's account reaches Claude Code as a synced plugin in Cowork and in terminal sessions where the member signs in with their claude.ai account on Claude Code v2.1.273 or later. [Plugins synced from claude.ai](https://code.claude.com/docs/en/plugins/loading#synced-plugins) has the sign-in and timing rules. For developers whose terminal sessions don't sync from a claude.ai account, use managed settings.
3131
from line 39
3939
4040**2. Check the repository against the organization sync rules**
4141
42Organization sync is stricter than Claude Code about the repository's visibility and about which plugin source types it accepts, and it rejects a plugin with a top-level `bin/` directory. Check [the plugin sources that organization sync accepts](/docs/plugins/org-sync#plugin-sources-that-organization-sync-accepts) before you continue.
42Organization sync is stricter than Claude Code about the repository's visibility and about which plugin source types it accepts, and it rejects a plugin with a top-level `bin/` directory. Check [the plugin sources that organization sync accepts](/docs/plugins/org-sync.md#plugin-sources-that-organization-sync-accepts) before you continue.
4343
4444**3. Sync the repository from organization settings**
4545
46In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), add the repository as [Add your own plugins](/docs/plugins/admin#add-your-own-plugins) describes, then [set each plugin's availability](/docs/plugins/admin#set-availability).
46In [**Organization settings > Plugins & skills**](https://claude.ai/admin-settings/skills?tab=inventory), add the repository as [Add your own plugins](/docs/plugins/admin.md#add-your-own-plugins) describes, then [set each plugin's availability](/docs/plugins/admin.md#set-availability).
4747
4848**4. Register the same marketplace in managed settings**
4949
from line 60
6060
6161## Build one repository for both audiences
6262
63One plugin folder can serve both audiences, because each surface skips the components it doesn't load. Hooks and agents load in Cowork and Claude Code and not in chat, and a local MCP server doesn't run in chat. Check each component you include against [Plugin feature support across platforms](/docs/plugins/platform-support) before you promise a behavior to people who only use chat.
63One plugin folder can serve both audiences, because each surface skips the components it doesn't load. Hooks and agents load in Cowork and Claude Code and not in chat, and a local MCP server doesn't run in chat. Check each component you include against [Plugin feature support across platforms](/docs/plugins/platform-support.md) before you promise a behavior to people who only use chat.
6464
6565## Update a plugin you've rolled out
6666
from line 92
9292
9393## Next steps
9494
95* [Sync your organization's plugins from a repository](/docs/plugins/org-sync): check your repository and plugin sources against the rules organization sync enforces
96* [Manage plugins for your organization](/docs/plugins/admin): set availability for everyone or for user groups, and control what members can add themselves
95* [Sync your organization's plugins from a repository](/docs/plugins/org-sync.md): check your repository and plugin sources against the rules organization sync enforces
96* [Manage plugins for your organization](/docs/plugins/admin.md): set availability for everyone or for user groups, and control what members can add themselves
9797* [Manage Claude Code plugins for your organization](https://code.claude.com/docs/en/plugins/org): set the managed-settings keys and deliver them to developers' machines
9898
No line in this hunk matches that.