coderClaw

coderclaw update

Safely update CoderClaw 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.

Usage

coderclaw update
coderclaw update status
coderclaw update wizard
coderclaw update --channel beta
coderclaw update --channel dev
coderclaw update --tag beta
coderclaw update --no-restart
coderclaw update --json
coderclaw --update

Options

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.

coderclaw update status
coderclaw update status --json
coderclaw update status --timeout 10

Options:

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 ...), CoderClaw also keeps the install method aligned:

Git checkout flow

Channels:

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 coderclaw 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

coderclaw --update rewrites to coderclaw update (useful for shells and launcher scripts).

See also