How to update Claude plugins and how auto-update works
Update one plugin with claude plugin update, or a whole marketplace from the /plugin panel. How auto-update and plugin versions decide what you get.
To update one plugin in Claude Code, run claude plugin update <plugin>@<marketplace> in your shell, or open the plugin on the Installed tab in /plugin and select Update now. In the Claude app, plugins from a marketplace or the directory update on your account automatically. Everything below comes from Anthropic's documentation as read in November 2026.
Update one plugin in Claude Code
The docs give two ways:
- In a session, run
/plugin, go to the Installed tab, open the plugin and select Update now. - In your shell, run this command:
claude plugin update <plugin>@<marketplace>
The running session keeps the version it already loaded. The docs say claude plugin update ends with Restart to apply changes. To load the new version without restarting, run this in the session:
/reload-plugins
Update every plugin from one marketplace
Anthropic's documentation says there is no command that updates every plugin at once. The closest thing works one marketplace at a time:
- Run
/pluginin a session. - Go to the Marketplaces tab.
- Select the marketplace.
- Choose Update marketplace.
The docs say this refreshes the marketplace's listing, updates the plugins you installed from it, and reports any plugin it left for you to update yourself.
There are also commands that update a marketplace's listing:
claude plugin marketplace update <name>
/plugin marketplace update <name>
The docs say that claude plugin marketplace update run in your shell with no name refreshes every marketplace's listing but leaves your installed plugins at their current versions.
How auto-update works in Claude Code
Plugins update automatically only when the marketplace they came from has auto-update turned on. The documented defaults are:
- On by default:
claude-plugins-officialand the other official marketplace names, exceptknowledge-work-pluginsandfirst-party-plugins, plus marketplaces added from claude.ai. - Off by default: every other marketplace, including the community marketplace, third-party marketplaces and local development marketplaces.
In an interactive session, after you send your first message, Claude Code waits a random delay of up to ten minutes. It then refreshes every marketplace with auto-update on and updates the plugins installed from them on disk. The running session keeps what it loaded, and you see Plugin updated: <name> · Run /reload-plugins to apply. Whether or not you reload, the new versions load on your next launch.
Turn auto-update on or off for a marketplace
- Run
/pluginin a Claude Code session. - Go to the Marketplaces tab.
- Select the marketplace.
- Select Enable auto-update or Disable auto-update.
A marketplace author cannot switch it on for you: the docs say marketplace.json has no field for it. An administrator can set "autoUpdate": true on the marketplace's extraKnownMarketplaces entry in managed settings.
Three environment variables turn the whole auto-update pass off and hide the toggle: DISABLE_UPDATES=1, DISABLE_AUTOUPDATER=1 and CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1. Setting FORCE_AUTOUPDATE_PLUGINS=1 as well keeps plugin auto-update running.
How a plugin's version decides whether you get an update
Claude Code computes a version for every plugin it installs, and that version is how it detects an update. If the computed version matches the one already recorded, the cached copy is not replaced. The order, for most source types, is:
- The
versionfield in the plugin'splugin.json. - The
versionfield in the plugin's marketplace entry. - If neither is set, a value from the source. For a
github,urlorgit-subdirsource, that is the commit SHA shortened to 12 characters.
The docs say a manifest that pins "version": "1.0.0" keeps every user on the cached copy until the author changes the string, however many commits they push. Authors who want users to track commits leave version out of both places. If you publish plugins yourself, see how to build a plugin.
What happens in the Claude app
For claude.ai and the desktop app, the docs say plugins from a marketplace or the directory update from their source. After a new version syncs from the source, you get it on your account automatically, with nothing to accept. In Customize > Plugins you can:
- select Check for updates to pull the latest from a marketplace you added;
- turn on Sync automatically for a marketplace you added yourself from github.com.
Claude Code's own marketplaces have a separate auto-update setting. The documentation does not say how often a source is checked when Sync automatically is on.
Plugins saved to your account also reach Claude Code as synced plugins. When an updated one arrives mid-session you see Plugins changed. Run /reload-plugins to activate. The sign-in and timing rules are in Claude plugin not syncing to Claude Code.
When an update does not arrive
Check these in order:
- The version did not change. If
claude plugin updateprints<name> is already at the latest version (<version>).after the author pushed commits, the computed version is unchanged. - You have not reloaded. Run
/reload-pluginsor start a new session. The docs add that monitors need a session restart. - Auto-update is off for that marketplace. It is off by default for anything that is not an official marketplace or one added from claude.ai.
- An environment variable disabled the pass. Look for the three variables listed above.
- A private marketplace could not authenticate. The docs say a background update fails quietly when a git credential helper would need to prompt, and your plugins keep working from the last synced state. For GitHub, the docs suggest
gh auth loginfollowed bygh auth setup-git. - The plugin is skipped by design. A plugin with a
commandsource, or whose marketplace entry sets aheadersHelpercommand, is not updated by Update marketplace. Update it from the Installed tab or withclaude plugin update.
If the marketplace itself is missing or misnamed, see Claude Code marketplace not found. For plugins that update but then do nothing, see Claude plugins not working.
Sources
Read more
Claude plugin not syncing to Claude Code? The documented rules
Plugins sync one way, from your Claude account to Claude Code, and only in sessions signed in with claude.ai. The documented rules and the checks, in order.
Claude Code marketplace not found: how to fix it
A typo'd marketplace name surfaces as a plugin-not-found error. The real error messages and the checks that fix them.
Private Claude plugin marketplace for a team or company
How to host a private Claude plugin marketplace, who can reach it, and how admins require, restrict and update plugins in the Claude app and Claude Code.
Turn off or remove a Claude plugin (and why removing a marketplace removes its plugins)
Turning off, uninstalling and removing a marketplace differ: removing a marketplace uninstalls its plugins and deletes their data. Tested on v2.1.325.