vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 20:10:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(plugins): clarify clawhub npm migration

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-29 06:09:27 +01:00
parent 8d78451e8b
commit 2b0b614417
20 changed files with 145 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/cli/plugins.md
View File

@@ -79,6 +79,16 @@ openclaw plugins install <plugin> --marketplace https://github.com/<owner>/<repo
Bare package names are checked against ClawHub first, then npm. Treat plugin installs like running code. Prefer pinned versions.
</Warning>
<Note>
ClawHub is the primary distribution and discovery surface for most plugins. Npm
remains a supported fallback and direct-install path. During the migration to
ClawHub, OpenClaw still ships some OpenClaw-owned `@openclaw/*` plugin packages
on npm; those package versions can lag the bundled source between plugin release
trains. If npm reports an OpenClaw-owned plugin package as deprecated, that
published version is an old external artifact; use the plugin bundled with
current OpenClaw or a local checkout until a newer npm package is published.
</Note>
<AccordionGroup>
<Accordion title="Config includes and invalid-config recovery">
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 `openclaw.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.