Protected ReadonlycommandProtected ReadonlyfetchProtected ReadonlyloggerProtected ReadonlymcpProtected ReadonlymessageProtected ReadonlypluginProtected ReadonlypluginProtected ReadonlypolicyProtected ReadonlyskillProtectedapplyApplies a batch, reporting one info message for the successes and one warning if anything failed. Each update is isolated so one failure does not abort the rest.
Runs one update pass. Never rejects - a registry that cannot be reached is logged and otherwise ignored, since a failed fetch is not evidence that anything needs updating.
ProtectedcollectResolves every installed artifact that has an update available and is not set to off.
Forces a registry refresh first - the cached response would not surface anything new.
ProtectedpromptAsks once, ever, whether updates should be applied automatically from now on. "Once" is anchored on the preference rather than on separate bookkeeping, so setting it by hand in Settings counts as answering. Dismissing writes nothing and the prompt returns on the next window load.
updates the user has not already applied. Turning auto update on applies them right away, since a user who just asked for automatic updates would otherwise watch the ones that prompted the question sit untouched until the next reload.
ProtectedpromptOffers the pending updates. There is deliberately no "don't update" action: closing the notification already means "not now", and the pass runs again on the next window load. Per-artifact policy is not offered here either; it lives in the gear menu, where it can name its target.
ProtectedsettingsProtectedsettingsProtectedsettingsMarkdown link opening the default preference. Notification messages are rendered as
inline markdown and their links are opened through the OpenerService, where core's
CommandOpenHandler picks up the command: scheme.
ProtectedshowOpens the Extensions view on the installed artifacts, where updates surface per card.
Checks the registry for updates to installed skills, MCP servers and Agent Plugins and applies or offers them according to the effective RegistryAutoUpdatePolicy.
Drifted artifacts are deliberately excluded in every mode: they classify as
fix-skill/fix-config/fix-pluginrather thaninstalled-from-registry, so they never reach collectPending and the user resolves them with Fix in the Extensions view.Updates go through the install services directly rather than the contributions' action handlers, so a batch reports one summary message instead of one message per artifact.