iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Antihost offers VPS plans with one-click OpenClaw, NVMe storage and a 14-day free trial.
For a normal supported OpenClaw installation, run openclaw update. It identifies whether OpenClaw was installed with npm, pnpm, Bun, or a Git checkout, checks for an available update while the existing Gateway continues serving, activates the update, and verifies the result. Use openclaw update --dry-run to rehearse the operation, or add --channel stable, --channel extended-stable, --channel beta, or --channel dev to select a release channel.
Before a significant update, create and verify a backup. Keep the same account that owns the installation, the same installation prefix, and the same profile, state, and configuration paths. OpenClaw currently requires Node 24.16 or newer on the Node 24 line, or Node 26.1 or newer.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute
Before you update
Updating the package is only one part of an OpenClaw upgrade. The Gateway, configuration, credentials, plugins, channels, and task data must continue to use the same locations and permissions after the new version is installed.
- Back up first: create a backup and verify that it can be read or restored before a major update.
- Use the owning account: run the update as the account that owns the current OpenClaw installation and Gateway data.
- Preserve paths: do not change the installation prefix, profile, state directory, or configuration paths during the upgrade.
- Check Node: use Node 24.16+ on the 24.x line or Node 26.1+.
- Identify the deployment owner: a package installation, Git checkout, macOS app, and container are updated through different owners.
To see the installed version before changing anything, run:
#1 Best Overall
openclaw --versionIf you are unsure which channel or installation owner is active, first rehearse the supported updater:
openclaw update --dry-runA dry run is a planning check; it does not install the candidate version.
Standard update: the supported command
For npm, pnpm, Bun, and Git-based installations, the preferred command is:
openclaw updateOpenClaw checks the candidate while the old Gateway remains available, applies the update, and performs verification. This avoids manually guessing which package manager was used. Afterward, confirm the installed version and Gateway health:
openclaw --version
openclaw gateway status --deepThe deep status check is supported where the Gateway owner exposes it. If a manually supervised Gateway is not controlled by OpenClaw, start or restart it through its actual service owner rather than assuming that the CLI owns the process.
Choose an update channel
OpenClaw’s updater accepts four channels. The channel changes which release stream is considered a candidate; it does not change your state or configuration paths.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Channel | Command | Use |
|---|---|---|
| Stable | openclaw update --channel stable |
Normal production updates |
| Extended stable | openclaw update --channel extended-stable |
A longer-supported release stream when selected by your operating policy |
| Beta | openclaw update --channel beta |
Pre-release testing |
| Development | openclaw update --channel dev |
Development builds; a Git-based development checkout can use this channel |
You can switch a source checkout or package installation between channels with the same command. Use --channel stable to return to stable or --channel dev to move to development. Back up before switching, because a channel change can introduce migrations or configuration changes even when the command itself succeeds.
Manual package-manager commands
Use a package-manager command when the normal updater cannot run, when your operating procedure requires an explicit package operation, or when you need to control lifecycle-script approval.
Rank #3
| Installation | Command | Important condition |
|---|---|---|
| npm 12 or npm 11.16+ | npm install -g openclaw@latest --allow-scripts=openclaw |
The lifecycle script must be explicitly allowed with this npm range. |
| npm 11.15 or earlier | npm install -g openclaw@latest |
Do not add the newer lifecycle-script flag. |
| pnpm | pnpm add -g --allow-build=openclaw openclaw@latest |
Allow the OpenClaw build step. |
| Bun | bun add -g --trust openclaw@latest |
Trust the OpenClaw package during the global install. |
These commands update the global package. They do not replace the need to preserve the existing owner, prefix, profile, state, and configuration paths. If a Gateway service is running, stop it first when your service arrangement requires a stopped process for package replacement; then start it through that same service owner and verify it.
Updating a very old installation safely
The current official procedure treats installations older than June or July 2026 differently. Do not jump directly from one of those older installations to the newest package. First install bridge version 2026.9.5, run Doctor migrations, resolve failed imports, and only then install openclaw@latest.
For an npm-managed Gateway, use this sequence:
-
Stop the Gateway:
openclaw gateway stop -
Install the bridge release:
npm install -g openclaw@2026.9.5 --allow-scripts=openclawIf the machine uses npm 11.15 or earlier, omit
--allow-scripts=openclaw, as with any other install on that npm range. -
Confirm that the bridge is actually installed:
openclaw --versionIt should report
2026.9.5before you continue. -
Run the migration and repair pass:
openclaw doctor --fix -
Install the latest release:
npm install -g openclaw@latest --allow-scripts=openclaw -
Run Doctor again:
openclaw doctor --fix -
Start the Gateway:
openclaw gateway start -
Check service health deeply:
openclaw gateway status --deep
The bridge is intended to import or repair retired task, flow, plugin, channel, credential, and configuration data. If Doctor reports a conflict, preserve the original state and configuration before attempting to resolve it. Do not delete the old data to force the migration through; a retained copy is your recovery path.
macOS app installations
When the installation owner is macos-app, update OpenClaw.app through the app’s own updater. The app updater moves the bundled Gateway and runtime together. A CLI update request does not replace the package; instead, it returns an owner hint telling you that the app owns the installation.
Use the app updater rather than combining it with a separate global npm, pnpm, or Bun installation. Mixing owners can leave the app, bundled runtime, and command-line package on different versions. After the app finishes, open the app and use its normal Gateway controls, then run the available status check to confirm readiness.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Docker, Podman, and Kubernetes deployments
Container deployments are updated by replacing the image through the deployment tool that owns the workload. Do not use a host-global package command as a substitute for replacing the running image.
- Docker or Podman: update the image reference in the container definition, recreate the container, and retain the mounted state and configuration locations.
- Kubernetes: update the image through the workload’s deployment mechanism and wait for the new pod to become ready.
- After replacement: follow the image entrypoint’s Doctor and readiness behavior. The container’s entrypoint may perform migration checks before it reports ready.
Because the deployment tool owns the process, start, stop, restart, and rollback actions must also be performed there. Keep a verified backup of persistent state before replacing the image.
Best Value
- 110 Sheets Log Book: This vehicle maintenance log book includes 110 record sheets to track repairs, services, fuel costs, and other vehicle-related expenses. It also comes with 36 convenient “Service Due” stickers to help remind you of upcoming maintenance schedules. Everything you need to keep your car records organized in one place.
- Detailed Information: Each page is carefully structured with dedicated sections for date, mileage, service description, parts replaced, vehicle information, cost, and additional notes. The clear and organized format allows you to maintain accurate records, monitor repair history, and better manage long-term vehicle performance and expenses.
- Enough Writing Space: The record sheets provide ample space for clear and thorough entries. Whether you’re documenting routine oil changes or major repairs, there’s plenty of room to write detailed information without feeling cramped.
- Easy to Use: The spiral binding allows the notebook to lay flat for comfortable writing, making entries quick and convenient. The included 36 “Service Due” stickers can be placed inside the book or on visible surfaces like your windshield or dashboard, helping you keep important maintenance reminders in sight.
- Proper Size: This compact logbook measures 5.5” x 7.1”, which fits easily in your glove compartment, center console, backpack, or desk drawer. Its portable size ensures you can access and update your vehicle records anytime, whether at home, in the garage, or at the service center.
Verify the update and recover from problems
Check the recorded update state
If you need to understand what the updater attempted or what it expects next, inspect:
openclaw update status --jsonThis records the target and next action. Review it before running another update so that a second attempt does not obscure the original failure.
Repair migration or configuration issues
When the update reports migration or configuration problems, run:
openclaw doctor --fixDoctor is the appropriate repair step for failed imports and configuration adjustments. Read its output, preserve the original state when it reports a conflict, and rerun the relevant verification only after the reported issue has been addressed.
Gateway will not start
First determine who supervises the Gateway. An OpenClaw-managed Gateway can be controlled with openclaw gateway start, openclaw gateway stop, and openclaw gateway status --deep. A manually supervised Gateway must be restarted through its actual service owner. Starting a second process with the CLI can create a port or state conflict instead of fixing the original service.
The command uses the wrong installation
This usually indicates a changed account, prefix, profile, or state path. Return to the account that owns the working installation, restore the original paths, and confirm openclaw --version before making another package change. Do not use a different global prefix merely because it is writable; that can produce a second OpenClaw installation that the existing Gateway does not use.
Recommended Free Tools
Lifecycle-script or build errors
Match the command to the package manager and version shown in the package-manager table. npm 12 and npm 11.16+ require --allow-scripts=openclaw; npm 11.15 and earlier use the command without that flag. pnpm requires --allow-build=openclaw, while Bun requires --trust. Retrying with a flag from another package manager will not correct the policy error.
Quick Recap
Recommended update checklist
- Identify whether the owner is npm, pnpm, Bun, Git, the macOS app, or a container deployment.
- Confirm Node 24.16+ on Node 24 or Node 26.1+.
- Create and verify a backup.
- Keep the owning account, prefix, profile, state, and configuration paths unchanged.
- Run
openclaw update --dry-runif you want a rehearsal. - Run
openclaw update, or use the matching explicit package command. - For an installation older than June or July 2026, use bridge version
2026.9.5and both Doctor passes first. - Use the app updater for
macos-appownership and deployment tooling for Docker, Podman, or Kubernetes. - Check
openclaw update status --jsonwhen a run is incomplete or unclear. - Run
openclaw doctor --fixfor migration or configuration errors. - Start or restart the Gateway through its actual owner and run
openclaw gateway status --deepwhere supported.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
