[FEATURE] Ability to enable or configure automatic updating of a marketplace and plugin

Open 💬 11 comments Opened Oct 24, 2025 by lukepattersontech

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:

  1. User in org installs the org marketplace and a general-tools plugin
  2. 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
  3. User starts a new Claude Code session via $ claude
  4. CC searches each installed marketplace and plugin definition file, and where it finds auto-update: true it 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.
  5. User has the new skill available for use

Additional Context

_No response_

View original on GitHub ↗

This issue has 11 comments on GitHub. Read the full discussion on GitHub ↗