> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wednesdayai.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# update

# `wednesdayai update`

Safely update WednesdayAI and switch between stable/beta/dev channels.

If you installed via **npm/pnpm** (global install, no git metadata), updates happen via the package manager flow in [Updating](https://docs.wednesdayai.dev/next/admin/install/updating.md).

## Usage

```bash theme={"dark"}
wednesdayai update
wednesdayai update status
wednesdayai update wizard
wednesdayai update --channel beta
wednesdayai update --channel dev
wednesdayai update --tag beta
wednesdayai update --dry-run
wednesdayai update --no-restart
wednesdayai update --json
wednesdayai --update
```

## Options

* `--no-restart`: skip restarting the Gateway service after a successful update.
* `--channel <stable|beta|dev>`: set the update channel (git + npm; persisted in config).
* `--tag <dist-tag|version>`: override the npm dist-tag or version for this update only.
* `--dry-run`: preview planned update actions (channel/tag/target/restart flow) without writing config, installing, syncing plugins, or restarting.
* `--json`: print machine-readable `UpdateRunResult` JSON.
* `--timeout <seconds>`: per-step timeout (default is 1200s).

Note: downgrades require confirmation because older versions can break configuration.

## `update status`

Show the active update channel + git tag/branch/SHA (for source checkouts), plus update availability.

```bash theme={"dark"}
wednesdayai update status
wednesdayai update status --json
wednesdayai update status --timeout 10
```

Options:

* `--json`: print machine-readable status JSON.
* `--timeout <seconds>`: timeout for checks (default is 3s).

## `update wizard`

Interactive flow to pick an update channel and confirm whether to restart the Gateway
after updating (default is to restart). If you select `dev` without a git checkout, it
offers to create one.

## What it does

When you switch channels explicitly (`--channel ...`), WednesdayAI also keeps the
install method aligned:

* `dev` → ensures a git checkout (default: `~/openclaw`, override with `OPENCLAW_GIT_DIR`),
  updates it, and installs the global CLI from that checkout.
* `stable`/`beta` → installs from npm using the matching dist-tag.

The Gateway core auto-updater (when enabled via config) reuses this same update path.

## Git checkout flow

Channels:

* `stable`: checkout the latest non-beta tag, then build + doctor.
* `beta`: checkout the latest `-beta` tag, then build + doctor.
* `dev`: checkout `main`, then fetch + rebase.

High-level:

1. Requires a clean worktree (no uncommitted changes).
2. Switches to the selected channel (tag or branch).
3. Fetches upstream (dev only).
4. Dev only: preflight lint + TypeScript build in a temp worktree; if the tip fails, walks back up to 10 commits to find the newest clean build.
5. Rebases onto the selected commit (dev only).
6. Installs deps (pnpm preferred; npm fallback).
7. Builds + builds the Control UI.
8. Runs `wednesdayai doctor` as the final “safe update” check.
9. Syncs plugins to the active channel (dev uses bundled extensions; stable/beta uses npm) and updates npm-installed plugins.

## `--update` shorthand

`openclaw --update` rewrites to `wednesdayai update` (useful for shells and launcher scripts).

## Shell completion

`wednesdayai update` reconciles shell completion for `wednesdayai`. It silently upgrades legacy OpenClaw
completion lines, regenerates missing caches, and prompts to enable completion if missing. It never prompts with
`--yes`, in `--json` mode, or without a TTY; PowerShell requires manual setup. See [Shell completion](https://docs.wednesdayai.dev/next/users/cli/completion.md).

## See also

* `wednesdayai doctor` (offers to run update first on git checkouts)
* [Development channels](https://docs.wednesdayai.dev/next/admin/install/development-channels.md)
* [Updating](https://docs.wednesdayai.dev/next/admin/install/updating.md)
* [CLI reference](https://docs.wednesdayai.dev/next/users/cli)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.