forked from Selig/openclaw-skill
Selig
4c966a3ad2
6 custom skills (assign-task, dispatch-webhook, daily-briefing, task-capture, qmd-brain, tts-voice) with technical documentation. Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
# update
|
|
|
|
# `openclaw update`
|
|
|
|
Manage OpenClaw updates across stable, beta, and development channels.
|
|
|
|
## Overview
|
|
|
|
The `openclaw update` command manages OpenClaw updates across stable, beta, and development channels. This tool handles version switching while maintaining configuration integrity.
|
|
|
|
## Key Capabilities
|
|
|
|
The update system supports multiple installation methods. When switching channels explicitly, OpenClaw also keeps the install method aligned with your chosen channel - dev uses git checkouts, while stable/beta use npm distribution tags.
|
|
|
|
## Primary Commands
|
|
|
|
```bash
|
|
openclaw update
|
|
openclaw update status
|
|
openclaw update wizard
|
|
openclaw update --channel beta
|
|
openclaw update --channel dev
|
|
```
|
|
|
|
## Important Safeguards
|
|
|
|
The update process includes verification steps:
|
|
|
|
* For git-based installations, the system requires a clean worktree (no uncommitted changes) before proceeding.
|
|
* Downgrades require confirmation because older versions can break configuration.
|
|
|
|
## Update Workflow Details
|
|
|
|
For dev channel users, the system performs preflight checks in a temporary workspace and can walk back up to 10 commits to find the newest clean build if the latest version has issues. All update paths conclude with running `openclaw doctor` as a validation step.
|
|
|
|
## Additional Options
|
|
|
|
* `--no-restart`: Skip Gateway service restart
|
|
* `--json`: Output machine-readable results for automation purposes
|