---
summary: "CLI reference for `nodmix plugins` (init, build, validate, list, install, marketplace, uninstall, enable/disable, doctor)"
read_when:
  - You want to install or manage Gateway plugins or compatible bundles
  - You want to scaffold or validate a simple tool plugin
  - You want to debug plugin load failures
title: "Plugins"
sidebarTitle: "Plugins"
---

Manage Gateway plugins, hook packs, and compatible bundles.

<CardGroup cols={2}>
  <Card title="Plugin system" href="/tools/plugin">
    End-user guide for installing, enabling, and troubleshooting plugins.
  </Card>
  <Card title="Manage plugins" href="/plugins/manage-plugins">
    Quick examples for install, list, update, uninstall, and publishing.
  </Card>
  <Card title="Plugin bundles" href="/plugins/bundles">
    Bundle compatibility model.
  </Card>
  <Card title="Plugin manifest" href="/plugins/manifest">
    Manifest fields and config schema.
  </Card>
  <Card title="Security" href="/gateway/security">
    Security hardening for plugin installs.
  </Card>
</CardGroup>

## Commands

```bash
nodmix plugins list
nodmix plugins list --enabled
nodmix plugins list --verbose
nodmix plugins list --json
nodmix plugins search <query>
nodmix plugins search <query> --limit 20
nodmix plugins search <query> --json
nodmix plugins install <path-or-spec>
nodmix plugins inspect <id>
nodmix plugins inspect <id> --runtime
nodmix plugins inspect <id> --json
nodmix plugins inspect --all
nodmix plugins info <id>
nodmix plugins enable <id>
nodmix plugins disable <id>
nodmix plugins registry
nodmix plugins registry --refresh
nodmix plugins uninstall <id>
nodmix plugins doctor
nodmix plugins update <id-or-npm-spec>
nodmix plugins update --all
nodmix plugins marketplace list <marketplace>
nodmix plugins marketplace list <marketplace> --json
nodmix plugins init <id>
nodmix plugins init <id> --directory ./my-plugin --name "My Plugin"
nodmix plugins build --entry ./dist/index.js
nodmix plugins build --entry ./dist/index.js --check
nodmix plugins validate --entry ./dist/index.js
```

For slow install, inspect, uninstall, or registry-refresh investigation, run the
command with `NODMIX_PLUGIN_LIFECYCLE_TRACE=1`. The trace writes phase timings
to stderr and keeps JSON output parseable. See [Debugging](/help/debugging#plugin-lifecycle-trace).

<Note>
In Nix mode (`NODMIX_NIX_MODE=1`), plugin lifecycle mutators are disabled. Use the Nix source for this install instead of `plugins install`, `plugins update`, `plugins uninstall`, `plugins enable`, or `plugins disable`; for nix-nodmix, use the agent-first [Quick Start](https://github.com/nodmix/nix-nodmix#quick-start).
</Note>

<Note>
Bundled plugins ship with Nodmix. Some are enabled by default (for example bundled model providers, bundled speech providers, and the bundled browser plugin); others require `plugins enable`.

Native Nodmix plugins must ship `openclaw.plugin.json` with an inline JSON Schema (`configSchema`, even if empty). Compatible bundles use their own bundle manifests instead.

`plugins list` shows `Format: nodmix` or `Format: bundle`. Verbose list/info output also shows the bundle subtype (`codex`, `claude`, or `cursor`) plus detected bundle capabilities.
</Note>

### Author

```bash
nodmix plugins init stock-quotes --name "Stock Quotes"
cd stock-quotes
npm run plugin:build
npm run plugin:validate
```

`plugins init` creates a minimal TypeScript tool plugin that uses
`defineToolPlugin`. `plugins build` imports that entry, reads its static tool
metadata, writes `openclaw.plugin.json`, and keeps `package.json`
`nodmix.extensions` aligned. `plugins validate` checks that the generated
manifest, package metadata, and current entry export still agree. See
[Tool Plugins](/plugins/tool-plugins) for the full authoring workflow.

The scaffold writes TypeScript source but generates metadata from the built
`./dist/index.js` entry so the workflow also works with the published CLI. Use
`--entry <path>` when the entry is not the default package entry. Use
`plugins build --check` in CI to fail when generated metadata is stale without
rewriting files.

### Install

```bash
nodmix plugins search "calendar"                   # search skills.nodmix.com plugins
nodmix plugins install <package>                      # source auto-detection
nodmix plugins install clawhub:<package>              # skills.nodmix.com only
nodmix plugins install npm:<package>                  # npm only
nodmix plugins install npm-pack:<path.tgz>            # local npm pack through npm install semantics
nodmix plugins install git:github.com/<owner>/<repo>  # git repo
nodmix plugins install git:github.com/<owner>/<repo>@<ref>
nodmix plugins install <package> --force              # overwrite existing install
nodmix plugins install <package> --pin                # pin version
nodmix plugins install <package> --dangerously-force-unsafe-install
nodmix plugins install <path>                         # local path
nodmix plugins install <plugin>@<marketplace>         # marketplace
nodmix plugins install <plugin> --marketplace <name>  # marketplace (explicit)
nodmix plugins install <plugin> --marketplace https://github.com/<owner>/<repo>
```

Maintainers testing setup-time installs can override automatic plugin install
sources with guarded environment variables. See
[Plugin install overrides](/plugins/install-overrides).

<Warning>
Bare package names install from npm by default during the launch cutover, unless they match an official plugin id. Raw `@nodmix/*` package specs that match bundled plugins use the bundled copy that shipped with the current Nodmix build. Use `npm:<package>` when you deliberately want an external npm package instead. Use `clawhub:<package>` for skills.nodmix.com. Treat plugin installs like running code. Prefer pinned versions.
</Warning>

`plugins search` queries skills.nodmix.com for installable plugin packages and prints
install-ready package names. It searches code-plugin and bundle-plugin packages,
not skills. Use `nodmix skills search` for skills.nodmix.com skills.

<Note>
skills.nodmix.com is the primary distribution and discovery surface for most plugins. Npm
remains a supported fallback and direct-install path. Nodmix-owned
`@nodmix/*` plugin packages are published on npm again; see the current list
on [npmjs.com/org/nodmix](https://www.npmjs.com/org/nodmix) or the
[plugin inventory](/plugins/plugin-inventory). Stable installs use `latest`.
Beta-channel installs and updates prefer the npm `beta` dist-tag when that tag
is available, then fall back to `latest`.
</Note>

<AccordionGroup>
  <Accordion title="Config includes and invalid-config repair">
    If your `plugins` section is backed by a single-file `$include`, `plugins install/update/enable/disable/uninstall` write through to that included file and leave `nodmix.json` untouched. Root includes, include arrays, and includes with sibling overrides fail closed instead of flattening. See [Config includes](/gateway/configuration) for the supported shapes.

    If config is invalid during install, `plugins install` normally fails closed and tells you to run `nodmix doctor --fix` first. During Gateway startup and hot reload, invalid plugin config fails closed like any other invalid config; `nodmix doctor --fix` can quarantine the invalid plugin entry. The only documented install-time exception is a narrow bundled-plugin recovery path for plugins that explicitly opt into `nodmix.install.allowInvalidConfigRecovery`.

  </Accordion>
  <Accordion title="--force and reinstall vs update">
    `--force` reuses the existing install target and overwrites an already-installed plugin or hook pack in place. Use it when you are intentionally reinstalling the same id from a new local path, archive, skills.nodmix.com package, or npm artifact. For routine upgrades of an already tracked npm plugin, prefer `nodmix plugins update <id-or-npm-spec>`.

    If you run `plugins install` for a plugin id that is already installed, Nodmix stops and points you at `plugins update <id-or-npm-spec>` for a normal upgrade, or at `plugins install <package> --force` when you genuinely want to overwrite the current install from a different source.

  </Accordion>
  <Accordion title="--pin scope">
    `--pin` applies to npm installs only. It is not supported with `git:` installs; use an explicit git ref such as `git:github.com/acme/plugin@v1.2.3` when you want a pinned source. It is not supported with `--marketplace`, because marketplace installs persist marketplace source metadata instead of an npm spec.
  </Accordion>
  <Accordion title="--dangerously-force-unsafe-install">
    `--dangerously-force-unsafe-install` is a break-glass option for false positives in the built-in dangerous-code scanner. It allows the install to continue even when the built-in scanner reports `critical` findings, but it does **not** bypass plugin `before_install` hook policy blocks and does **not** bypass scan failures.

    Install scans ignore common test files and directories such as `tests/`, `__tests__/`, `*.test.*`, and `*.spec.*` to avoid blocking packaged test mocks; declared plugin runtime entrypoints are still scanned even if they use one of those names.

    This CLI flag applies to plugin install/update flows. Gateway-backed skill dependency installs use the matching `dangerouslyForceUnsafeInstall` request override, while `nodmix skills install` remains a separate skills.nodmix.com skill download/install flow.

    If a plugin you published on skills.nodmix.com is hidden or blocked by a registry scan, use the publisher steps in [skills.nodmix.com publishing](/clawhub/publishing). `--dangerously-force-unsafe-install` only affects installs on your own machine; it does not ask skills.nodmix.com to rescan the plugin or make a blocked release public.

  </Accordion>
  <Accordion title="Hook packs and npm specs">
    `plugins install` is also the install surface for hook packs that expose `nodmix.hooks` in `package.json`. Use `nodmix hooks` for filtered hook visibility and per-hook enablement, not package installation.

    Npm specs are **registry-only** (package name + optional **exact version** or **dist-tag**). Git/URL/file specs and semver ranges are rejected. Dependency installs run in one managed npm project per plugin with `--ignore-scripts` for safety, even when your shell has global npm install settings. Managed plugin npm projects inherit Nodmix's package-level npm `overrides`, so host security pins apply to hoisted plugin dependencies too.

    Use `npm:<package>` when you want to make npm resolution explicit. Bare package specs also install directly from npm during the launch cutover unless they match an official plugin id.

    Raw `@nodmix/*` package specs that match bundled plugins resolve to the image-owned bundled copy before npm fallback. For example, `nodmix plugins install @nodmix/discord@2026.5.20 --pin` uses the bundled Discord plugin from the current Nodmix build instead of creating a managed npm override. To force the external npm package, use `nodmix plugins install npm:@nodmix/discord@2026.5.20 --pin`.

    Bare specs and `@latest` stay on the stable track. Nodmix date-stamped correction versions such as `2026.5.3-1` are stable releases for this check. If npm resolves either of those to a prerelease, Nodmix stops and asks you to opt in explicitly with a prerelease tag such as `@beta`/`@rc` or an exact prerelease version such as `@1.2.3-beta.4`.

    For npm installs without an exact version (`npm:<package>` or `npm:<package>@latest`), Nodmix checks the resolved package metadata before install. If the latest stable package requires a newer Nodmix plugin API or minimum host version, Nodmix inspects older stable versions and installs the newest compatible release instead. Exact versions and explicit dist-tags such as `@beta` remain strict: if the selected package is incompatible, the command fails and asks you to upgrade Nodmix or choose a compatible version.

    If a bare install spec matches an official plugin id (for example `diffs`), Nodmix installs the catalog entry directly. To install an npm package with the same name, use an explicit scoped spec (for example `@scope/diffs`).

  </Accordion>
  <Accordion title="Git repositories">
    Use `git:<repo>` to install directly from a git repository. Supported forms include `git:github.com/owner/repo`, `git:owner/repo`, full `https://`, `ssh://`, `git://`, `file://`, and `git@host:owner/repo.git` clone URLs. Add `@<ref>` or `#<ref>` to check out a branch, tag, or commit before install.

    Git installs clone into a temporary directory, check out the requested ref when present, then use the normal plugin directory installer. That means manifest validation, dangerous-code scanning, package-manager install work, and install records behave like npm installs. Recorded git installs include the source URL/ref plus the resolved commit so `nodmix plugins update` can re-resolve the source later.

    After installing from git, use `nodmix plugins inspect <id> --runtime --json` to verify runtime registrations such as gateway methods and CLI commands. If the plugin registered a CLI root with `api.registerCli`, execute that command directly through the Nodmix root CLI, for example `nodmix demo-plugin ping`.

  </Accordion>
  <Accordion title="Archives">
    Supported archives: `.zip`, `.tgz`, `.tar.gz`, `.tar`. Native Nodmix plugin archives must contain a valid `openclaw.plugin.json` at the extracted plugin root; archives that only contain `package.json` are rejected before Nodmix writes install records.

    Use `npm-pack:<path.tgz>` when the file is an npm-pack tarball and you want
    to test the same per-plugin managed npm project path used by registry
    installs, including `package-lock.json` verification, hoisted dependency
    scanning, and npm install records. Plain archive paths still install as local
    archives under the plugin extensions root.

    Claude marketplace installs are also supported.

  </Accordion>
</AccordionGroup>

skills.nodmix.com installs use an explicit `clawhub:<package>` locator:

```bash
nodmix plugins install clawhub:nodmix-codex-app-server
nodmix plugins install clawhub:nodmix-codex-app-server@1.2.3
```

Bare npm-safe plugin specs install from npm by default during the launch cutover unless they match an official plugin id:

```bash
nodmix plugins install nodmix-codex-app-server
```

Use `npm:` to make npm-only resolution explicit:

```bash
nodmix plugins install npm:nodmix-codex-app-server
nodmix plugins install npm:@nodmix/discord@2026.5.20
nodmix plugins install npm:@scope/plugin-name@1.0.1
```

Nodmix checks the advertised plugin API / minimum gateway compatibility before install. When the selected skills.nodmix.com version publishes a ClawPack artifact, Nodmix downloads the versioned npm-pack `.tgz`, verifies the skills.nodmix.com digest header and the artifact digest, then installs it through the normal archive path. Older skills.nodmix.com versions without ClawPack metadata still install through the legacy package archive verification path. Recorded installs keep their skills.nodmix.com source metadata, artifact kind, npm integrity, npm shasum, tarball name, and ClawPack digest facts for later updates.
Unversioned skills.nodmix.com installs keep an unversioned recorded spec so `nodmix plugins update` can follow newer skills.nodmix.com releases; explicit version or tag selectors such as `clawhub:pkg@1.2.3` and `clawhub:pkg@beta` remain pinned to that selector.

#### Marketplace shorthand

Use `plugin@marketplace` shorthand when the marketplace name exists in Claude's local registry cache at `~/.claude/plugins/known_marketplaces.json`:

```bash
nodmix plugins marketplace list <marketplace-name>
nodmix plugins install <plugin-name>@<marketplace-name>
```

Use `--marketplace` when you want to pass the marketplace source explicitly:

```bash
nodmix plugins install <plugin-name> --marketplace <marketplace-name>
nodmix plugins install <plugin-name> --marketplace <owner/repo>
nodmix plugins install <plugin-name> --marketplace https://github.com/<owner>/<repo>
nodmix plugins install <plugin-name> --marketplace ./my-marketplace
```

<Tabs>
  <Tab title="Marketplace sources">
    - a Claude known-marketplace name from `~/.claude/plugins/known_marketplaces.json`
    - a local marketplace root or `marketplace.json` path
    - a GitHub repo shorthand such as `owner/repo`
    - a GitHub repo URL such as `https://github.com/owner/repo`
    - a git URL

  </Tab>
  <Tab title="Remote marketplace rules">
    For remote marketplaces loaded from GitHub or git, plugin entries must stay inside the cloned marketplace repo. Nodmix accepts relative path sources from that repo and rejects HTTP(S), absolute-path, git, GitHub, and other non-path plugin sources from remote manifests.
  </Tab>
</Tabs>

For local paths and archives, Nodmix auto-detects:

- native Nodmix plugins (`openclaw.plugin.json`)
- Codex-compatible bundles (`.codex-plugin/plugin.json`)
- Claude-compatible bundles (`.claude-plugin/plugin.json` or the default Claude component layout)
- Cursor-compatible bundles (`.cursor-plugin/plugin.json`)

<Note>
Compatible bundles install into the normal plugin root and participate in the same list/info/enable/disable flow. Today, bundle skills, Claude command-skills, Claude `settings.json` defaults, Claude `.lsp.json` / manifest-declared `lspServers` defaults, Cursor command-skills, and compatible Codex hook directories are supported; other detected bundle capabilities are shown in diagnostics/info but are not yet wired into runtime execution.
</Note>

### List

```bash
nodmix plugins list
nodmix plugins list --enabled
nodmix plugins list --verbose
nodmix plugins list --json
nodmix plugins search <query>
nodmix plugins search <query> --limit 20
nodmix plugins search <query> --json
```

<ParamField path="--enabled" type="boolean">
  Show only enabled plugins.
</ParamField>
<ParamField path="--verbose" type="boolean">
  Switch from the table view to per-plugin detail lines with source/origin/version/activation metadata.
</ParamField>
<ParamField path="--json" type="boolean">
  Machine-readable inventory plus registry diagnostics and package dependency install state.
</ParamField>

<Note>
`plugins list` reads the persisted local plugin registry first, with a manifest-only derived fallback when the registry is missing or invalid. It is useful for checking whether a plugin is installed, enabled, and visible to cold startup planning, but it is not a live runtime probe of an already-running Gateway process. After changing plugin code, enablement, hook policy, or `plugins.load.paths`, restart the Gateway that serves the channel before expecting new `register(api)` code or hooks to run. For remote/container deployments, verify you are restarting the actual `nodmix gateway run` child, not only a wrapper process.

`plugins list --json` includes each plugin's `dependencyStatus` from `package.json`
`dependencies` and `optionalDependencies`. Nodmix checks whether those package
names are present along the plugin's normal Node `node_modules` lookup path; it
does not import plugin runtime code, run a package manager, or repair missing
dependencies.
</Note>

`plugins search` is a remote skills.nodmix.com catalog lookup. It does not inspect local
state, mutate config, install packages, or load plugin runtime code. Search
results include the skills.nodmix.com package name, family, channel, version, summary, and
an install hint such as `nodmix plugins install clawhub:<package>`.

For bundled plugin work inside a packaged Docker image, bind-mount the plugin
source directory over the matching packaged source path, such as
`/app/extensions/synology-chat`. Nodmix will discover that mounted source
overlay before `/app/dist/extensions/synology-chat`; a plain copied source
directory remains inert so normal packaged installs still use compiled dist.

For runtime hook debugging:

- `nodmix plugins inspect <id> --runtime --json` shows registered hooks and diagnostics from a module-loaded inspection pass. Runtime inspection never installs dependencies; use `nodmix doctor --fix` to clean legacy dependency state or recover missing downloadable plugins that are referenced by config.
- `nodmix gateway status --deep --require-rpc` confirms the reachable Gateway URL/profile, service/process hints, config path, and RPC health.
- Non-bundled conversation hooks (`llm_input`, `llm_output`, `before_model_resolve`, `before_agent_reply`, `before_agent_run`, `before_agent_finalize`, `agent_end`) require `plugins.entries.<id>.hooks.allowConversationAccess=true`.

Use `--link` to avoid copying a local directory (adds to `plugins.load.paths`):

```bash
nodmix plugins install -l ./my-plugin
```

Standalone plugin files must be listed in `plugins.load.paths` rather than placed directly in `~/.nodmix/extensions` or `<workspace>/.nodmix/extensions`. Those auto-discovered roots load plugin package or bundle directories, while top-level script files are treated as local helpers and skipped.

<Note>
`--force` is not supported with `--link` because linked installs reuse the source path instead of copying over a managed install target.

Use `--pin` on npm installs to save the resolved exact spec (`name@version`) in the managed plugin index while keeping the default behavior unpinned.
</Note>

### Plugin index

Plugin install metadata is machine-managed state, not user config. Installs and updates write it to `plugins/installs.json` under the active Nodmix state directory. Its top-level `installRecords` map is the durable source of install metadata, including records for broken or missing plugin manifests. The `plugins` array is the manifest-derived cold registry cache. The file includes a do-not-edit warning and is used by `nodmix plugins update`, uninstall, diagnostics, and the cold plugin registry.

When Nodmix sees shipped legacy `plugins.installs` records in config, runtime reads treat them as compatibility input without rewriting `nodmix.json`. Explicit plugin writes and `nodmix doctor --fix` move those records into the plugin index and remove the config key when config writes are allowed; if either write fails, the config records are kept so the install metadata is not lost.

### Uninstall

```bash
nodmix plugins uninstall <id>
nodmix plugins uninstall <id> --dry-run
nodmix plugins uninstall <id> --keep-files
```

`uninstall` removes plugin records from `plugins.entries`, the persisted plugin index, plugin allow/deny list entries, and linked `plugins.load.paths` entries when applicable. Unless `--keep-files` is set, uninstall also removes the tracked managed install directory when it is inside Nodmix's plugin extensions root. For active memory plugins, the memory slot resets to `memory-core`.

<Note>
`--keep-config` is supported as a deprecated alias for `--keep-files`.
</Note>

### Update

```bash
nodmix plugins update <id-or-npm-spec>
nodmix plugins update --all
nodmix plugins update <id-or-npm-spec> --dry-run
nodmix plugins update @nodmix/voice-call
nodmix plugins update nodmix-codex-app-server --dangerously-force-unsafe-install
```

Updates apply to tracked plugin installs in the managed plugin index and tracked hook-pack installs in `hooks.internal.installs`.

<AccordionGroup>
  <Accordion title="Resolving plugin id vs npm spec">
    When you pass a plugin id, Nodmix reuses the recorded install spec for that plugin. That means previously stored dist-tags such as `@beta` and exact pinned versions continue to be used on later `update <id>` runs.

    For npm installs, you can also pass an explicit npm package spec with a dist-tag or exact version. Nodmix resolves that package name back to the tracked plugin record, updates that installed plugin, and records the new npm spec for future id-based updates.

    Passing the npm package name without a version or tag also resolves back to the tracked plugin record. Use this when a plugin was pinned to an exact version and you want to move it back to the registry's default release line.

  </Accordion>
  <Accordion title="Beta channel updates">
    `nodmix plugins update` reuses the tracked plugin spec unless you pass a new spec. `nodmix update` additionally knows the active Nodmix update channel: on the beta channel, default-line npm and skills.nodmix.com plugin records try `@beta` first. They fall back to the recorded default/latest spec if no plugin beta release exists; npm plugins also fall back when the beta package exists but fails install validation. That fallback is reported as a warning and does not fail the core update. Exact versions and explicit tags stay pinned to that selector.

  </Accordion>
  <Accordion title="Version checks and integrity drift">
    Before a live npm update, Nodmix checks the installed package version against the npm registry metadata. If the installed version and recorded artifact identity already match the resolved target, the update is skipped without downloading, reinstalling, or rewriting `nodmix.json`.

    When a stored integrity hash exists and the fetched artifact hash changes, Nodmix treats that as npm artifact drift. The interactive `nodmix plugins update` command prints the expected and actual hashes and asks for confirmation before proceeding. Non-interactive update helpers fail closed unless the caller supplies an explicit continuation policy.

  </Accordion>
  <Accordion title="--dangerously-force-unsafe-install on update">
    `--dangerously-force-unsafe-install` is also available on `plugins update` as a break-glass override for built-in dangerous-code scan false positives during plugin updates. It still does not bypass plugin `before_install` policy blocks or scan-failure blocking, and it only applies to plugin updates, not hook-pack updates.
  </Accordion>
</AccordionGroup>

### Inspect

```bash
nodmix plugins inspect <id>
nodmix plugins inspect <id> --runtime
nodmix plugins inspect <id> --json
```

Inspect shows identity, load status, source, manifest capabilities, policy flags, diagnostics, install metadata, bundle capabilities, and any detected MCP or LSP server support without importing plugin runtime by default. Add `--runtime` to load the plugin module and include registered hooks, tools, commands, services, gateway methods, and HTTP routes. Runtime inspection reports missing plugin dependencies directly; installs and repairs stay in `nodmix plugins install`, `nodmix plugins update`, and `nodmix doctor --fix`.

Plugin-owned CLI commands are usually installed as root `nodmix` command groups, but plugins may also register nested commands under a core parent such as `nodmix nodes`. After `inspect --runtime` shows a command under `cliCommands`, run it at the listed path; for example a plugin that registers `demo-git` can be verified with `nodmix demo-git ping`.

Each plugin is classified by what it actually registers at runtime:

- **plain-capability** — one capability type (e.g. a provider-only plugin)
- **hybrid-capability** — multiple capability types (e.g. text + speech + images)
- **hook-only** — only hooks, no capabilities or surfaces
- **non-capability** — tools/commands/services but no capabilities

See [Plugin shapes](/plugins/architecture#plugin-shapes) for more on the capability model.

<Note>
The `--json` flag outputs a machine-readable report suitable for scripting and auditing. `inspect --all` renders a fleet-wide table with shape, capability kinds, compatibility notices, bundle capabilities, and hook summary columns. `info` is an alias for `inspect`.
</Note>

### Doctor

```bash
nodmix plugins doctor
```

`doctor` reports plugin load errors, manifest/discovery diagnostics, compatibility notices, and stale plugin config references such as missing plugin slots. When the install tree and plugin config are clean it prints `No plugin issues detected.` If stale config remains but the install tree is otherwise healthy, the summary says so instead of implying full plugin health.

If a configured plugin is present on disk but blocked by the loader's path-safety checks, config validation keeps the plugin entry and reports it as `present but blocked`. Fix the preceding blocked-plugin diagnostic, such as path ownership or world-writable permissions, instead of removing the `plugins.entries.<id>` or `plugins.allow` config.

For module-shape failures such as missing `register`/`activate` exports, rerun with `NODMIX_PLUGIN_LOAD_DEBUG=1` to include a compact export-shape summary in the diagnostic output.

### Registry

```bash
nodmix plugins registry
nodmix plugins registry --refresh
nodmix plugins registry --json
```

The local plugin registry is Nodmix's persisted cold read model for installed plugin identity, enablement, source metadata, and contribution ownership. Normal startup, provider owner lookup, channel setup classification, and plugin inventory can read it without importing plugin runtime modules.

Use `plugins registry` to inspect whether the persisted registry is present, current, or stale. Use `--refresh` to rebuild it from the persisted plugin index, config policy, and manifest/package metadata. This is a repair path, not a runtime activation path.

`nodmix doctor --fix` also repairs registry-adjacent managed npm drift: if an orphaned or recovered `@nodmix/*` package under a managed plugin npm project or the legacy flat managed npm root shadows a bundled plugin, doctor removes that stale package and rebuilds the registry so startup validates against the bundled manifest. Doctor also relinks the host `nodmix` package into managed npm plugins that declare `peerDependencies.nodmix`, so package-local runtime imports such as `nodmix/plugin-sdk/*` resolve after updates or npm repairs.

<Warning>
`NODMIX_DISABLE_PERSISTED_PLUGIN_REGISTRY=1` is a deprecated break-glass compatibility switch for registry read failures. Prefer `plugins registry --refresh` or `nodmix doctor --fix`; the env fallback is only for emergency startup recovery while the migration rolls out.
</Warning>

### Marketplace

```bash
nodmix plugins marketplace list <source>
nodmix plugins marketplace list <source> --json
```

Marketplace list accepts a local marketplace path, a `marketplace.json` path, a GitHub shorthand like `owner/repo`, a GitHub repo URL, or a git URL. `--json` prints the resolved source label plus the parsed marketplace manifest and plugin entries.

## Related

- [Building plugins](/plugins/building-plugins)
- [CLI reference](/cli)
- [skills.nodmix.com](/clawhub)
