fix(plugins): keep bare installs on npm for launch

This commit is contained in:
Vincent Koc
2026-05-02 11:57:07 -07:00
parent a7a6d24147
commit cf21bcf9bf
14 changed files with 64 additions and 286 deletions

View File

@@ -66,16 +66,15 @@ Site: [clawhub.ai](https://clawhub.ai)
```
`plugins search` queries the ClawHub plugin catalog and prints install-ready
package names. Bare npm-safe plugin specs use ClawHub only after package
readiness says the package is install-ready for OpenClaw; otherwise OpenClaw
preserves npm fallback:
package names. Use `clawhub:<package>` when you want ClawHub resolution.
Bare npm-safe plugin specs install from npm during the launch cutover:
```bash
openclaw plugins install openclaw-codex-app-server
```
Use `npm:<package>` when you want npm-only resolution without a
ClawHub lookup:
`npm:<package>` is also npm-only and is useful when a spec could otherwise
be ambiguous:
```bash
openclaw plugins install npm:openclaw-codex-app-server

View File

@@ -90,7 +90,7 @@ If you prefer chat-native control, enable `commands.plugins: true` and use:
The install path uses the same resolver as the CLI: local path/archive, explicit
`clawhub:<pkg>`, explicit `npm:<pkg>`, explicit `git:<repo>`, or bare package
spec (ClawHub first, then npm fallback).
spec through npm.
If config is invalid, install normally fails closed and points you at
`openclaw doctor --fix`. The only recovery exception is a narrow bundled-plugin
@@ -467,7 +467,7 @@ openclaw plugins registry # inspect persisted registry state
openclaw plugins registry --refresh # rebuild persisted registry
openclaw doctor --fix # repair plugin registry state
openclaw plugins install <package> # install (readiness-gated ClawHub, then npm)
openclaw plugins install <package> # install from npm by default
openclaw plugins install clawhub:<pkg> # install from ClawHub only
openclaw plugins install npm:<pkg> # install from npm only
openclaw plugins install git:<repo> # install from git