How to Update OpenClaw to the Latest Version

Keeping OpenClaw updated to the latest version is important for security patches, bug fixes, and new features. The update process depends on how you installed OpenClaw — this guide covers git, Docker, and nacre.sh managed updates.

Before You Update: Back Up First

Always backup your OpenClaw data before major updates:

cp -r ~/.openclaw ~/.openclaw.backup.$(date +%Y%m%d)

Check the OpenClaw changelog (github.com/openclaw/openclaw/releases) for breaking changes before upgrading across major versions.

Updating a Git Installation

cd ~/openclaw
source venv/bin/activate

# Save your config
cp ~/.openclaw/openclaw.json ~/.openclaw/openclaw.json.backup

# Pull latest changes
git pull origin main

# Check if you're on a stable release tag
git log --oneline -5

# Update Python dependencies
pip install -r requirements.txt --upgrade

# Restart OpenClaw
# If using systemd:
sudo systemctl restart openclaw

# If running manually:
python -m openclaw start

Updating to a Specific Version

# List available releases
git tag -l | sort -V | tail -20

# Checkout a specific version
git checkout v2.4.1

# Update dependencies for that version
pip install -r requirements.txt

Updating a Docker Installation

cd /path/to/your/openclaw/
docker compose pull
docker compose up -d

Docker Compose automatically pulls the latest image and restarts the container while preserving your data volume.

Checking Your Current Version

python -m openclaw --version
# Or
cat ~/.openclaw/version.json

What's New in Recent Versions

OpenClaw follows semantic versioning. Minor versions (2.3 → 2.4) add features but maintain backward compatibility. Patch versions (2.4.0 → 2.4.1) contain bug fixes and security patches only.

Key features added in 2026 releases include improved multi-agent orchestration, canvas host security hardening (CVE-2026-25253 fix), enhanced SKILL.md schema validation, and expanded OpenRouter support.

nacre.sh: Automatic Updates

On nacre.sh, OpenClaw updates are applied automatically during maintenance windows. Security patches are deployed immediately. You don't need to take any action — your instance is always running a supported, secure version.

Frequently Asked Questions

What if an update breaks my skills?

Some skill updates require corresponding OpenClaw version changes. Check your skill's SKILL.md for the minimum required OpenClaw version. If a skill breaks after update, pin OpenClaw to the previous version (git checkout <previous-tag>) while waiting for a skill update.

How often does OpenClaw release updates?

Minor releases occur approximately monthly. Security patches are released as needed, sometimes same-day for critical vulnerabilities.

Is it safe to always run the latest main branch?

The main branch is generally stable but may include experimental features. For production deployments, use the latest tagged release instead.