Keeping OpenClaw Up to Date

I hate it when a tool update breaks my entire configuration. It usually happens right when I’m in the middle of something important. Getting stuck on an old version because I’m afraid to run a command is a common headache for most of us.

I want to show you how to handle updates safely using the openclaw update command. Whether you want to stay on the stable path or try out the latest features in the dev channel, the CLI handles the heavy lifting for you.

What You’ll Need

• An existing OpenClaw installation.
• A clean git worktree (if you are updating from a source checkout).

Quick Start

If you want the latest version immediately, run this command in your terminal:

openclaw update

I usually check my current version and channel before I do anything else. You can do that with the status command:

openclaw update status

If you prefer a guided approach, the wizard will walk you through picking a channel and deciding whether to restart the Gateway:

openclaw update wizard

Switching Channels

You can switch between stable, beta, and dev versions easily. When you switch, OpenClaw keeps your install method aligned. For example, the dev channel ensures you have a git checkout, while stable uses npm.

To switch to the beta channel:

openclaw update --channel beta

To switch to the dev channel:

openclaw update --channel dev

If you just need a specific version or tag for one update without changing your saved config, use the --tag flag:

openclaw update --tag beta

Other Useful Options

Sometimes you don’t want the Gateway to restart after the update. You can skip that part with this flag:

openclaw update --no-restart

If you are writing scripts, the --json flag is helpful for getting machine-readable output:

openclaw update --json

You can also use this shorthand if it’s easier to remember:

openclaw --update

Troubleshooting

Uncommitted Changes

The update process requires a clean worktree. If you have uncommitted changes in your git directory, the update will stop. You need to commit or stash your work before trying again.

Downgrade Warnings

If you try to install a version that is older than your current one, the CLI will ask for confirmation. I recommend being careful here because older versions can sometimes break your existing configuration.

Build Failures in Dev

When using the dev channel, the tool runs a preflight check. It builds the project in a temporary area to make sure it works. If the latest commit on main fails to build, the tool will walk back up to 10 commits to find the newest stable build for you.

Timeouts

If your network is slow, the update might time out. The default is 1200 seconds, but you can increase it:

openclaw update --timeout 2000

Still have questions? Chat with the AI Setup Assistant.

What’s Next

• openclaw doctor
• Development channels
• Updating
• CLI reference