MCP, plugins, skills, and hooks changedthird-party/claude-desktop/extensions
Nearest release: v2.1.322, published 16 hours before 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 10 Nov 2026 18:30 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 10 Nov 2026 18:37 UTC.
Upstream edited
Recorded here
Lines+21added
Lines−2removed
From line
264
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits43to this page, all time
The whole hunk
from line 264, old and new numbered
/
from line 264
264264}
265265```
266266
267Each plugin marked this way still needs a `sha256` on its archive. Claude Desktop re-fetches the manifest periodically and picks up a newly published version without a configuration change or an app relaunch. A plugin the user removes stays removed.
267Each plugin marked this way still needs a `sha256` on its archive. Claude Desktop picks up a newly published version without a configuration change or an app relaunch, as described in [Roll out marketplace updates](#roll-out-marketplace-updates). A plugin the user removes stays removed.
268268
269269Claude Desktop honors these per-plugin marks only when the manifest is served from your inference gateway's or bootstrap server's own origin, because those hosts already carry your deployment's configuration and credentials. On any other origin the marks are ignored, and the marketplace behaves as `"available"`. Entry-level `"auto_install"` and `"required"` continue to require the [admin-side content pin](#marketplace-installation-preferences) on every origin.
270270
from line 283
283283
284284### Roll out marketplace updates
285285
286For a git marketplace, commit the change to the repository, update the `ref` in `allowedPluginMarketplaces` to the new commit SHA, and distribute the updated managed configuration. For a `url` marketplace with a `manifestSha256` pin, publish the new archive, update its `url` and `sha256` in `marketplace.json`, and update `manifestSha256` in configuration to the new file's digest. For a `url` marketplace using [per-plugin auto-install from a trusted origin](#per-plugin-auto-install-from-a-trusted-origin), publish the new `marketplace.json` and no configuration change is needed. Devices sync to the new revision on the next app launch or periodic re-fetch. To remove a marketplace, delete its entry; Claude Desktop unregisters it and uninstalls its plugins on the next sync.
286Publish a new version in the way that matches the marketplace's entry in `allowedPluginMarketplaces`:
287
288* **Git marketplace pinned to a commit**: commit the change to the repository, update `ref` to the new commit SHA, and distribute the updated managed configuration
289* **Git marketplace on a branch or tag**: push the change to the branch, or move the tag, with no configuration change
290* **`url` marketplace with a `manifestSha256` pin**: publish the new archive, update its `url` and `sha256` in `marketplace.json`, and update `manifestSha256` in configuration to the new file's digest
291* **`url` marketplace with no `manifestSha256` pin**: publish the new archive, then the new `marketplace.json`, with no configuration change. A marketplace that uses [per-plugin auto-install from a trusted origin](#per-plugin-auto-install-from-a-trusted-origin) is of this kind
292
293Devices sync to the new revision on the next app launch or periodic re-fetch, about every 10 minutes. A pinned marketplace syncs when the device receives the new pin.
294
295Claude Desktop also checks a `url` marketplace with no `manifestSha256` pin when a user opens a new Chat, Cowork, or Code session, returns to the app with that new session still open, or sends the session's first message:
296
297* **What users see**: a new skill in a plugin the user has installed, or in a plugin marked for automatic installation, shows when the user types `/` in the message box, and Claude can use it in that session
298* **What counts as a change**: Claude Desktop compares the bytes of `marketplace.json` with the copy it installed, so a new zip at the same URL goes unseen until that file changes. When you replace a zip, update its `sha256` in `marketplace.json`, or the plugin's `version` if the archive lists no `sha256`. Otherwise serve the same bytes, with no timestamp or other value that differs between requests
299* **What your server gets**: each device requests `marketplace.json`, at most once every 10 seconds per marketplace. After any change to the file, each device downloads every archive that it lists
300* **If the server is slow or an update fails**: a session waits up to 5 seconds for the marketplace's answer and up to 30 seconds in all, then starts with the copy it has. After a check that fails or gets no answer, or a new version that doesn't install, new sessions don't ask that marketplace again for five minutes
301* **With `userGit` or `credentialHelper`**: opening or returning to a new session checks at most once every five minutes, so a new skill can be missing from the `/` list until the user sends the first message
302
303Earlier versions of Claude Desktop sync only at launch and at the periodic re-fetch.
304
305To remove a marketplace, delete its entry; Claude Desktop unregisters it and uninstalls its plugins on the next sync.
287306
288307### Move a marketplace to a new source
289308
No line in this hunk matches that.