[FEATURE] Ability to enable or configure automatic updating of a marketplace and plugin
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Many organizations are building a private marketplace and plugins to distribute common shared CC tools among their organization. The problem though is that the current update path requires users to proactively navigate through the CC meny to trigger an update of a given marketplace and/or plugin. In reality, this will not happen at scale.
Proposed Solution
I propose instead that a marketplace definition file and a plugin definition file support an auto-update flag, which when enabled will cause an update to run automatically upon a CC session starting, and also restart the session automatically afterward (which is another impediment to updating currently).
The goal would be that organizations could have a sort of Continuous Delivery of Claude Code plugins to their teams/users so that they always have the most up-to-date tools (agents, commands, skills, hooks, etc). This will really help teams move faster with adoption of the great stuff Anthropic keeps adding.
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
Other
Use Case Example
Example Scenario:
- User in org installs the org marketplace and a
general-toolsplugin - Plugin owning team (ie. Platform, DevEx, etc) adds a new skill to the plugin, publishing it to the marketplace via a git commit to the marketplace repo
- User starts a new Claude Code session via
$ claude - CC searches each installed marketplace and plugin definition file, and where it finds
auto-update: trueit runs the internal update command. If any updates were made then it reloads the session with a no-op flag that bypasses this check upon the restart / new session. - User has the new skill available for use
Additional Context
_No response_
Showing cached comments. Read the full discussion on GitHub ↗
11 Comments
As long as this is not supported directly in claude, I use a
SessionStart-Hook which callsclaude plugin marketplace update <your-marketplace-name>to trigger updates on every session start as a workaround.This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Related practical suggestion: Add
/plugin updatecommand for CLI-based update management.Proposed behavior:
/plugin update- Lists available updates across all marketplaces (default: list mode)/plugin update --all- Batch update all available/plugin update [plugin-name]- Update specific plugin--marketplace [name]to scope to specific marketplaceThis enables update management without navigating marketplace UI, complementing the auto-update configuration requested here.
Submitted feedback ID:
463f7ab1-611c-4ebe-8657-bcec5962dc7cAgree, with this flag.
maybe this could be a flag that is only available or works on not github.com urls.
or non-internal repos.
this would mitigate against public marketplaces setting autoupdate.
Any update?
Would be great to have this feature as the list of marketplaces keeps growing.
check on this, https://github.com/anthropics/claude-code/issues/17627
FORCE_AUTOUPDATE_PLUGINSHitting this also. We're using Cowork org marketplace with "Sync automatically" enabled, but every end user still has to click "Update" on the plugin tile when a new version ships. We pushed a new skill 24 hours ago and just spent half a day diagnosing why teammates couldn't see it — root cause was Cowork users not knowing to click Update
Two-tier friction (admin clicks "Re-sync" + each user clicks "Update") effectively means non-engineer team members are perpetually on stale plugin versions - which really hurts in companies like ours, where the majority of Claude users rely on Cowork.
+1 to the auto-update flag in marketplace.json proposed above — would fix this end-to-end.
+1
+1
+1