Three coordinated things:
1. Resolve the committed upstream/main merge conflicts. 94 files were
sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
by keeping HEAD everywhere — 540 conflict blocks.
2. Rewrite remaining OpenClaw text refs.
OPENCLAW → HANZO_BOT
OpenClaw → HanzoBot (PascalCase type identifiers)
openclaw → bot (codebase convention — botToken,
botUsername etc.; avoids invalid
hyphenated JS identifiers)
openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z] (compound)
ai.openclaw.x → ai.hanzo.bot.x (JVM package path)
3. Delete or rename openclaw-named file paths (116 of them). Dead
duplicates with a Bot-named canonical from the partial migration:
deleted. Otherwise renamed.
ai/openclaw/** → deleted (ai/hanzo/bot/** canonical)
Sources/OpenClaw*/ → deleted (Sources/Bot* canonical)
Tests/OpenClawIPCTests/ → deleted (Tests/BotIPCTests canonical)
OpenClawKit/ → deleted (BotKit canonical)
openclaw-tools.*.ts → deleted (bot-tools.*.ts canonical)
openclaw-root.ts etc. → deleted (bot-root.ts canonical)
types.openclaw.ts → deleted (types.bot.ts canonical)
extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
docs/start/openclaw.md → renamed hanzo-bot.md (+ zh-CN)
docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
scripts/.../openclaw-* → deleted (bot/hanzo-bot parallels)
openclaw.mjs → deleted (hanzo-bot.mjs is package.bin)
Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).
Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.
The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.
Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.
3.4 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| CLI reference for `hanzo-bot update` (safe-ish source update + gateway auto-restart) |
|
update |
hanzo-bot update
Safely update HanzoBot 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
hanzo-bot update
hanzo-bot update status
hanzo-bot update wizard
hanzo-bot update --channel beta
hanzo-bot update --channel dev
hanzo-bot update --tag beta
hanzo-bot update --dry-run
hanzo-bot update --no-restart
hanzo-bot update --json
hanzo-bot --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-readableUpdateRunResultJSON.--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.
hanzo-bot update status
hanzo-bot update status --json
hanzo-bot 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 ...), HanzoBot also keeps the
install method aligned:
dev→ ensures a git checkout (default:~/hanzo-bot, override withBOT_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-betatag, then build + doctor.dev: checkoutmain, then fetch + rebase.
High-level:
- Requires a clean worktree (no uncommitted changes).
- Switches to the selected channel (tag or branch).
- Fetches upstream (dev only).
- 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.
- Rebases onto the selected commit (dev only).
- Installs deps (pnpm preferred; npm fallback).
- Builds + builds the Control UI.
- Runs
hanzo-bot doctoras the final “safe update” check. - Syncs plugins to the active channel (dev uses bundled extensions; stable/beta uses npm) and updates npm-installed plugins.
--update shorthand
hanzo-bot --update rewrites to hanzo-bot update (useful for shells and launcher scripts).
See also
hanzo-bot doctor(offers to run update first on git checkouts)- Development channels
- Updating
- CLI reference