For a normal, supported OpenClaw installation, run openclaw update. OpenClaw identifies whether it is installed through npm, pnpm, Bun, or a Git checkout, checks for an available candidate while the existing Gateway continues serving, applies the update, and verifies the result.
Antihost offers VPS plans with one-click OpenClaw, NVMe storage and a 14-day free trial.
Before a significant update, make a verified backup. Keep the same account that owns the installation, installation prefix, profile, and state/configuration paths. OpenClaw currently requires Node 24.16 or newer on the 24.x line, or Node 26.1 or newer.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
The safest default update path
The built-in updater is the right first choice when OpenClaw is a regular package installation or a source checkout. It is designed to preserve the installation context instead of making you guess which package-manager command applies.
- Create and verify a backup of your OpenClaw state and configuration, especially before a significant version change.
- Confirm that the update will run as the same user and under the same installation prefix, profile, and state/configuration paths used by the current installation.
- Check that the active Node runtime is supported: Node 24.16 or later within the 24.x series, or Node 26.1 or later.
- Optionally rehearse the operation with
openclaw update --dry-run. A dry run lets you inspect the candidate and intended action without activating it. - Run
openclaw updateand allow the updater to complete its candidate check, activation, and verification. - If the command reports migration or configuration problems, run
openclaw doctor --fix, review what it changes, and then verify the Gateway.
The updater’s ability to work while the old Gateway is serving is useful for reducing interruption, but it does not remove the need to understand how your Gateway is supervised. A manually supervised process, an app-owned process, and a containerized process each have a different restart and readiness path.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Check the installation context before changing anything
Keep the owning account and paths unchanged
OpenClaw state is tied to the account, profile, installation prefix, and state/configuration locations used by the existing installation. Running an update as a different account or with a different prefix can create a second installation, leave the Gateway unable to find its data, or make the command appear to have succeeded while the service still uses the old files.
- Use the same operating-system account that owns the current OpenClaw installation.
- Do not change the profile or state/configuration paths during the upgrade.
- Do not mix a user-level installation with a system-level prefix unless you are deliberately migrating the installation and have preserved its data.
Confirm the Node runtime
Use a supported runtime before attempting the update. The supported requirements are Node 24.16+ on the 24.x line or Node 26.1+. An older Node runtime can prevent package installation, lifecycle scripts, migration code, or the newly installed Gateway from starting even when the package manager reports success.
Make a verified backup
A backup is only useful if it can be read or restored. Confirm that the backup contains the OpenClaw state and configuration needed by your profile, and keep it available until the updated Gateway has passed its checks. If a migration reports conflicts, preserve the original state and configuration rather than deleting or overwriting them while troubleshooting.
Package-manager commands
If you need to update through the package manager instead of the built-in updater, use the command that matches both your package manager and its version. Lifecycle-script policies differ, so the flags are not interchangeable.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
| Installation method | Command | Important condition |
|---|---|---|
| npm 12 or npm 11.16+ | npm install -g openclaw@latest --allow-scripts=openclaw |
The explicit lifecycle-script allowance is required by this npm command path. |
| npm 11.15 or earlier | npm install -g openclaw@latest |
Use the command without the newer lifecycle-script flag. |
| pnpm | pnpm add -g --allow-build=openclaw openclaw@latest |
The build allowance names OpenClaw explicitly. |
| Bun | bun add -g --trust openclaw@latest |
The trust flag permits the package’s required install behavior. |
Run the package-manager command as the same account and with the same global prefix used by the current installation. After installation, use the normal OpenClaw verification and Gateway checks rather than assuming that a successful package-manager exit means the running service has changed.
Channels: stable, extended stable, beta, and dev
The updater can target a release channel explicitly:
openclaw update --channel stableselects the stable channel.openclaw update --channel extended-stableselects the extended-stable channel.openclaw update --channel betaselects the beta channel.openclaw update --channel devselects the development channel.
Use a channel deliberately. Stable is the conservative choice for a production Gateway; beta and dev can expose changes earlier and may require more active recovery when migrations or integrations change. A source checkout can use the updater as well, and the documented channel controls can switch between package and Git-oriented update paths: --channel dev moves toward the development/Git path, while --channel stable returns to the stable path.
If you are unsure what the updater recorded after a failed or interrupted attempt, inspect openclaw update status --json. The JSON status shows the recorded target and the next action, which is safer than immediately launching another update without knowing what already happened.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Updating a very old installation
Installations predating the June–July 2026 transition need an intermediate bridge rather than a direct jump to the newest release. The official guidance uses bridge version 2026.9.5 to import or repair retired task, flow, plugin, channel, credential, and configuration data before installing the current release.
For an npm-managed Gateway, use this sequence:
openclaw gateway stop
npm install -g [email protected] --allow-scripts=openclaw
openclaw --version
openclaw doctor --fix
npm install -g openclaw@latest --allow-scripts=openclaw
openclaw doctor --fix
openclaw gateway start
openclaw gateway status --deep- Stop the Gateway so the bridge can work against a quiescent installation.
- Install exactly
2026.9.5using the npm lifecycle-script allowance. - Run
openclaw --versionand confirm that the bridge version is active before continuing. - Run
openclaw doctor --fixto perform the bridge migrations and repairs. - Resolve any failed imports or conflicts while the original state and configuration are still preserved.
- Install
openclaw@latest, run Doctor again, start the Gateway, and perform a deep status check.
Do not skip the version confirmation. If the bridge is not actually active, the next Doctor run may operate on the wrong schema. If Doctor reports a conflict, keep the original state and configuration intact until you understand which data can be migrated safely.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →macOS app-owned installations
When the installation owner is owner: "macos-app", update OpenClaw.app through the app’s own updater. The app bundles the Gateway and runtime, so moving only the command-line package can leave the app and its service on different versions.
For this owner type, a CLI update request returns an owner hint instead of changing the package. Treat that message as a routing instruction: open the macOS app updater, complete the app update, and let the bundled Gateway and runtime move together. Do not force a separate global npm, pnpm, or Bun installation as a substitute for the app update.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Docker, Podman, and Kubernetes deployments
Container deployments are updated by replacing the image through the deployment tool that owns the workload. The OpenClaw CLI inside an existing container is not the authoritative way to replace the image.
- Use your Docker, Podman, or Kubernetes deployment workflow to select and roll out the new OpenClaw image.
- Allow the image entrypoint to run its documented Doctor behavior, migrations, and readiness checks.
- Wait for the deployment’s readiness condition before directing traffic to the new instance.
- Use the deployment’s service and log inspection tools to confirm that the Gateway is healthy.
Because the image entrypoint controls startup, follow its Doctor and readiness behavior rather than applying the npm bridge sequence blindly inside a running container. Keep the persistent state and configuration volumes attached to the replacement workload.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Gateway verification after an update
When OpenClaw manages the Gateway
After the updater completes, check the Gateway using the OpenClaw commands appropriate to your installation. Where supported, openclaw gateway status --deep performs a deeper health check than a superficial process check. It can reveal that a package changed while the service failed to start, loaded the wrong profile, or cannot reach a required dependency.
When another service manager owns the process
If the Gateway is manually supervised or started by another service manager, restart it through that actual owner. Examples include the operating-system service definition, a process supervisor, a container orchestrator, or a desktop app. Starting a second Gateway from a shell can produce port conflicts and makes the result harder to diagnose.
When migration or configuration checks fail
Run openclaw doctor --fix when the update reports migration or configuration issues. Review the proposed repairs, keep a copy of the pre-update state, and rerun the deep Gateway status check after the repair. Doctor is a recovery and migration tool; it is not a reason to discard a failed installation’s original data.
Choosing the right update method
| Owner or deployment | Primary update action | Lifecycle or build policy | Post-update verification |
|---|---|---|---|
| npm-managed installation | openclaw update, or the npm command matching your npm version |
npm 12 and npm 11.16+ use --allow-scripts=openclaw; npm 11.15 and earlier omit it |
OpenClaw update verification, then Gateway status; use --deep where supported |
| pnpm-managed installation | openclaw update, or the pnpm command |
--allow-build=openclaw |
Gateway status after the package update |
| Bun-managed installation | openclaw update, or the Bun command |
--trust |
Gateway status after the package update |
| Git or source checkout | openclaw update with the intended channel |
The channel determines the documented package/Git direction | Updater verification and Gateway health check |
| macOS app-owned installation | OpenClaw.app’s app updater | The app updater keeps the bundled runtime and Gateway together | App and Gateway readiness after the app restart |
| Docker, Podman, or Kubernetes | Replace the image through the deployment tooling | The image entrypoint controls Doctor and readiness behavior | Deployment readiness and Gateway logs/status |
Common failure branches
The updater says another owner must perform the update
This normally indicates an app-owned installation, especially the macOS app owner. Use the named owner’s updater instead of repeating the CLI command or installing a second global package.
The package installs but the Gateway is still old
The package and the running service may have different owners. Check the service through its actual supervisor, restart it there, and then run the deep Gateway status check. Avoid launching an additional Gateway process from a terminal.
The package manager rejects scripts or builds
Use the lifecycle or build policy for your exact package-manager version: npm 12 and npm 11.16+ need the explicit OpenClaw script allowance, older npm does not; pnpm needs the OpenClaw build allowance; Bun needs the trust flag. Do not copy a flag from one package manager to another.
Doctor reports failed imports or conflicts
For a pre-June/July 2026 installation, return to the bridge procedure and verify that 2026.9.5 was active before the first Doctor run. Preserve the original state and configuration, resolve the reported retired task, flow, plugin, channel, credential, or configuration issue, and only then continue to the latest release.
The update was interrupted or its target is unclear
Inspect openclaw update status --json before trying again. Use the recorded target and next action to decide whether to resume, repair with Doctor, or restore the verified backup. Repeating the update blindly can obscure which migration step failed.
Quick Recap
Update checklist
- Verified backup exists and remains available.
- Same owning account, prefix, profile, and state/configuration paths are in use.
- Node is 24.16+ on 24.x or 26.1+.
- Installation owner is identified: npm, pnpm, Bun, Git, macOS app, or container.
- Correct channel is selected before activation.
- Very old installations use the
2026.9.5bridge first. - Doctor issues are resolved without deleting the original state.
- Gateway is restarted by its real service owner.
openclaw gateway status --deeppasses where 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.
