Turn plugins on or off inside a registered marketplace, one at a time or all at once, and understand why the change does not reach Claude Code by itself.
pks marketplace enable <MARKETPLACE_ID> [PLUGIN_NAMES]$ pks marketplace enable my-marketplace plugin-aEnable one specific plugin
$ pks marketplace enable my-marketplaceEnable every plugin in the marketplace
$ pks marketplace disable my-marketplace plugin-aDisable one specific plugin
$ pks marketplace disable my-marketplaceDisable every plugin in the marketplace
pks marketplace enable and pks marketplace disable set the enabled flag on plugins inside a marketplace you already registered. Both are local edits to the last-fetched plugin list, with no network call and no change to any Claude Code file.
pks marketplace list to find it.pks marketplace show <ID> for the per-plugin table. Names are matched literally.Name one or more plugins after the marketplace ID:
pks marketplace enable my-marketplace plugin-a
pks marketplace enable my-marketplace plugin-a plugin-b
Each named plugin is set to enabled and the registry is saved.
Omit the plugin names to enable every plugin the marketplace lists:
pks marketplace enable my-marketplace
disable is the exact mirror — same arguments, opposite result:
pks marketplace disable my-marketplace plugin-a
pks marketplace disable my-marketplace
Read the per-plugin table back and check the enabled column:
pks marketplace show my-marketplace
pks marketplace list also reflects the change in its enabled-of-total count.
Neither command touches Claude Code configuration. The curated state only reaches Claude Code when you render it:
pks claude managed-settings
That command reads the same registry and writes managed-settings.json to stdout, or to a path you pass with --output.
Neither command takes flags.
| Argument | Required | Description |
|---|---|---|
MARKETPLACE_ID | yes | Marketplace ID. |
PLUGIN_NAMES | no | Plugin names to enable or disable. Omit to affect all plugins. |
Nothing changed after naming a plugin. Plugin names that do not appear in the marketplace's plugin list are ignored without a warning or an error, so a typo fails quietly. Copy the name from pks marketplace show <ID> rather than typing it.
Claude Code still loads the old plugin set. These commands edit only the pks registry. Re-run pks claude managed-settings and redistribute the rendered file.
A required plugin was disabled anyway. disable does not check the required flag that a policy document applied during add. A plugin marked required can be disabled here with no warning, which silently defeats the policy. Re-run pks marketplace add against the URL source to reapply the policy.
Enabled state disappeared for a plugin. A plugin that vanishes from the upstream source is dropped on the next pks marketplace refresh, and a newly appearing plugin is added disabled. Check the source document before assuming the registry lost data.