chore(sync): mirror docs from openclaw/openclaw@3147efbed4

This commit is contained in:
openclaw-docs-sync[bot] 2026-05-03 20:25:17 +00:00
parent 3bb4746320
commit df681bb996
3 changed files with 17 additions and 2 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "62fb50d7fc5d8451852526a29814ccec619c4dcf",
"syncedAt": "2026-05-03T19:42:42.125Z"
"sha": "3147efbed40babd3a36eba6a4ea4bad3e56073a6",
"syncedAt": "2026-05-03T20:23:15.441Z"
}

View File

@ -2,6 +2,7 @@
summary: "CLI reference for `openclaw update` (safe-ish source update + gateway auto-restart)"
read_when:
- You want to update a source checkout safely
- You are debugging `openclaw update` output or options
- You need to understand `--update` shorthand behavior
title: "Update"
---
@ -42,6 +43,14 @@ openclaw --update
- `--timeout <seconds>`: per-step timeout (default is 1800s).
- `--yes`: skip confirmation prompts (for example downgrade confirmation).
`openclaw update` does not have a `--verbose` flag. Use `--dry-run` to preview
the planned channel/tag/install/restart actions, `--json` for machine-readable
results, and `openclaw update status --json` when you only need channel and
availability details. If you are debugging Gateway logs around an update,
console verbosity and file log level are separate: Gateway `--verbose` affects
terminal/WebSocket output, while file logs require `logging.level: "debug"` or
`"trace"` in config. See [Gateway logging](/gateway/logging).
<Warning>
Downgrades require confirmation because older versions can break configuration.
</Warning>

View File

@ -25,6 +25,12 @@ openclaw update --tag main
openclaw update --dry-run # preview without applying
```
`openclaw update` does not accept `--verbose`. For update diagnostics, use
`--dry-run` to preview the planned actions, `--json` for structured results, or
`openclaw update status --json` to inspect channel and availability state. The
installer has its own `--verbose` flag, but that flag is not part of
`openclaw update`.
`--channel beta` prefers beta, but the runtime falls back to stable/latest when
the beta tag is missing or older than the latest stable release. Use `--tag beta`
if you want the raw npm beta dist-tag for a one-off package update.