Preflight Checklist
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-tools plugin
- 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: 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.
- User has the new skill available for use
Additional Context
No response
Preflight Checklist
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-updateflag, 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:
general-toolsplugin$ claudeauto-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.Additional Context
No response