#How do I set this:

1 messages · Page 1 of 1 (latest)

grim vortex
#

OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1

I need to downgrade to 5.12 because of a "⚠️ Requested agent harness "claude-cli" is not registered." error.

smoky bayBOT
inland isleBOT
inland isleBOT
# grim vortex OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 I need to downgrade to 5.12 b...
export OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1
pnpm add -g openclaw@2026.5.12
openclaw doctor
openclaw gateway restart

That said, the specific error Requested agent harness "claude-cli" is not registered usually means claude-cli is being used as an embedded harness/runtime. In current docs, claude-cli is a CLI backend/provider path, not an embedded harness id. Valid embedded harness runtime values are things like auto, pi, or registered harness ids like codex.

So also check/remove this if you have it set:

unset OPENCLAW_AGENT_RUNTIME
# or force built-in runner:
OPENCLAW_AGENT_RUNTIME=pi openclaw gateway restart
inland isleBOT
grim vortex
#

Ubuntu, OC 5.19.

inland isleBOT
# grim vortex Ubuntu, OC 5.19.

Got it. On Ubuntu + 2026.5.19, I’d check the harness setting before downgrading. That error is very likely from OPENCLAW_AGENT_RUNTIME=claude-cli or config embeddedHarness.runtime: "claude-cli".

Run:

printenv OPENCLAW_AGENT_RUNTIME
openclaw config get agents.defaults.embeddedHarness

If either says claude-cli, change it to auto or pi:

unset OPENCLAW_AGENT_RUNTIME
openclaw config set agents.defaults.embeddedHarness.runtime auto
openclaw gateway restart
inland isleBOT
# grim vortex Ubuntu, OC 5.19.

If you’re running it as a systemd user service and had put the env var in the service environment, check:

systemctl --user show openclaw-gateway.service -p Environment

If you still want to pin 2026.5.12, use:

OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 pnpm add -g openclaw@2026.5.12
openclaw doctor
openclaw gateway restart

But I’d fix the runtime value first; claude-cli is the CLI backend/provider route, not an embedded harness runtime.

grim vortex
#

Your OpenClaw config was written by version 2026.5.19, but this command is running 2026.5.12.
Check: openclaw --version, which openclaw, and openclaw gateway status --deep.
If unexpected, update PATH so openclaw points to the version you want, or reinstall the Gateway service from that same OpenClaw install.

inland isleBOT
inland isleBOT
# grim vortex Your OpenClaw config was written by version 2026.5.19, but this command is runni...
which openclaw
openclaw gateway status --deep

If you really want to stay on 2026.5.12, run the follow-up commands with the same break-glass env var too:

OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 openclaw doctor
OPENCLAW_ALLOW_OLDER_BINARY_DESTRUCTIVE_ACTIONS=1 openclaw gateway restart

If the gateway is installed as a systemd user service, also make sure the service is using the same binary you just installed:

which openclaw
inland isleBOT
grim vortex
#

ERR_PNPM_NO_GLOBAL_BIN_DIR  Unable to find the global bin directory

inland isleBOT
inland isleBOT