Plugin install overrides
先看人话
这页用于补齐 OpenClaw 官方最新文档里的新增内容。先按命令和字段原样理解;如果你只是普通用户,优先看本页的标题、小节和示例命令,不需要一口气读完所有维护者细节。
Plugin install overrides let maintainers test setup-time plugin installs against a specific npm package or local npm-pack tarball. They are for E2E and package validation only. Normal users should install plugins with openclaw plugins install.
注意
Overrides execute plugin code from the source you provide. Use them only in an isolated state directory or disposable test machine.
Environment
Overrides are disabled unless both variables are set:
export OPENCLAW_ALLOW_PLUGIN_INSTALL_OVERRIDES=1
export OPENCLAW_PLUGIN_INSTALL_OVERRIDES='{
"codex": "npm-pack:/tmp/openclaw-codex-2026.5.8.tgz",
"openclaw-web-search": "npm:@openclaw/web-search@2026.5.8"
}'The override map is JSON keyed by plugin id. Values support:
npm:<registry-spec>for registry packages and exact versions or tagsnpm-pack:<path.tgz>for local tarballs produced bynpm pack
Relative npm-pack: paths resolve from the current working directory.
Behavior
When a setup-time flow asks to install a plugin whose id appears in the map, OpenClaw uses the override source instead of the catalog, bundled, or default npm source. This applies to onboarding and other flows that use the shared setup-time plugin installer.
Overrides still enforce the expected plugin id. A tarball mapped to codex must install a plugin whose manifest id is codex.
Overrides do not inherit official trusted-source status. Even when the catalog entry normally represents an OpenClaw-owned package, an override is treated as operator-supplied test input.
Workspace .env files cannot enable install overrides. Set these variables in the trusted shell, CI job, or remote test command that launches OpenClaw.
Package E2E
Use an isolated state directory so package installs and install records do not touch your normal OpenClaw state:
npm pack extensions/codex --pack-destination /tmp
OPENCLAW_STATE_DIR="$(mktemp -d)" \
OPENCLAW_ALLOW_PLUGIN_INSTALL_OVERRIDES=1 \
OPENCLAW_PLUGIN_INSTALL_OVERRIDES='{"codex":"npm-pack:/tmp/openclaw-codex-2026.5.8.tgz"}' \
pnpm openclaw onboard --mode localVerify the installed package under the state directory:
find "$OPENCLAW_STATE_DIR/npm/projects" -path '*/node_modules/@openclaw/codex/package.json' -print
grep -R '"@openclaw/codex"' "$OPENCLAW_STATE_DIR/npm/projects"/*/package-lock.jsonFor live provider E2E, source the real API key from a trusted shell or CI secret before launching the test command. Do not print keys; report only the source and whether the key was present.
