OpenClaw Old Version NPM Migration Fix

Start with the official update flow. openclaw update is the safest first command because it handles the update path and can restart the Gateway after updating.

If you want to check the update before changing anything, run:

If the version is still old after this, the issue is usually not the package update itself. It is usually a wrong binary path, old package name, stale Gateway service, or Node version problem.

• Old clawdbot package is still installed
• Old moltbot package is still installed
• Terminal PATH points to an older openclaw binary
• npm installed OpenClaw into a different global folder
• Shell command cache still remembers the old command path
• Gateway service is still running old code
• Multiple Gateway services are installed
• Node.js version is too old
• Docker/container install is being confused with host npm install

Before reinstalling everything like a caveman with admin access, check which OpenClaw command your system is actually using.

macOS and Linux

Windows PowerShell

If which -a openclaw or where openclaw shows more than one path, your system may be running an older binary before the updated npm one.

If npm updated /home/user/.npm-global/bin/openclaw but your terminal runs /usr/local/bin/openclaw, the terminal will still show the old version.

If your setup still uses clawdbot or moltbot, remove them and install the current openclaw package.

Check npm cache safely first:

Only force-clean cache if you have a real cache problem:

Do not keep running this:

That can keep you tied to the old package path instead of the current OpenClaw install.

Check your npm global folder and current PATH:

Add npm’s global bin folder to PATH:

For bash:

For zsh:

Verify again:

If the version is now correct, the problem was PATH order. Humanity survives another environment-variable incident.

Some shells remember command locations even after you update the package.

For bash:

For zsh:

Then verify:

If it still shows the old version, close the terminal and open a new one.

Sometimes the CLI updates correctly, but the Gateway still runs old code.

Check Gateway status:

If the Gateway still looks stale, reinstall the Gateway service:

Use gateway status --deep when you suspect stale services, duplicate services, or service metadata problems.

Most users should run only one OpenClaw Gateway per machine. Multiple Gateways can cause confusion unless you intentionally separate ports, config paths, state directories, and workspaces.

Run:

If OpenClaw reports extra services or stale clients, follow the cleanup hints from the command output. Gateway troubleshooting docs also mention using gateway status --deep or doctor --deep to identify stale OpenClaw client processes after updates or rollbacks.

Check your Node.js and npm versions:

Use Node 24 if possible:

Then update OpenClaw again:

On Windows, first check which OpenClaw command is active:

If old Gateway service data is stuck, run:

If Windows shows multiple openclaw.cmd paths, fix PATH order or remove the old global install. Do not assume the first openclaw.cmd is the newest one. Computers do not reward optimism.

Run these checks:

Then run the clean update flow:

If the service metadata is still stale:

On macOS and Linux, stale launchd or systemd service data can keep pointing to old runtime paths. OpenClaw docs mention openclaw doctor --fix and openclaw gateway install --force for service repair cases. (OpenClaw)

If OpenClaw runs in Docker, this command updates the host CLI only:

It does not update the running container.

Check Docker:

Update the Docker setup:

Then verify:

If the Gateway runs inside Docker, check the version inside the container or update the container image. Host npm and Docker are separate worlds, because apparently one runtime universe was too merciful.

Use this only after checking PATH, old packages, Gateway status, and Node version.

Do not delete ~/.openclaw just because the CLI version is old. That directory can contain config, credentials, sessions, and workspace data.

If the npm update is partially broken, you can also rerun the installer:

OpenClaw installer docs say the installer can run openclaw gateway install --force, restart the Gateway, and probe Gateway health when a Gateway service is already loaded from the same prefix. (OpenClaw)

Avoid these mistakes:

• Do not keep installing clawdbot@latest
• Do not delete ~/.openclaw just because the CLI version is old
• Do not mix npm, pnpm, bun, source, Docker, and installer paths without checking PATH
• Do not assume host npm updates Docker containers
• Do not ignore openclaw gateway status --deep
• Do not use openclaw update --verbose
• Do not use npm cache clean --force before trying npm cache verify

If you keep losing time to npm paths, Node versions, stale Gateway services, and local update issues, run OpenClaw on Ampere.sh instead.

Ampere.sh gives you managed OpenClaw hosting so you can deploy, connect your model, add channels, and keep the Gateway running without babysitting the machine.