mirror of https://github.com/hanzoai/bot.git synced 2026-10-30 17:24:26 +00:00

Files

T

zeekay acaeda400a Eradicate OpenClaw — resolve merge conflicts and finish the rebrand

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.

2026-05-11 17:56:29 -07:00

2.0 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Gateway runtime on macOS (external launchd service)

Packaging HanzoBot.app

Debugging the macOS gateway launchd service

Installing the gateway CLI for macOS

Gateway on macOS

Gateway on macOS (external launchd)

HanzoBot.app no longer bundles Node/Bun or the Gateway runtime. The macOS app expects an external hanzo-bot CLI install, does not spawn the Gateway as a child process, and manages a per‑user launchd service to keep the Gateway running (or attaches to an existing local Gateway if one is already running).

Install the CLI (required for local mode)

You need Node 22+ on the Mac, then install hanzo-bot globally:

npm install -g hanzo-bot@<version>

The macOS app’s Install CLI button runs the same flow via npm/pnpm (bun not recommended for Gateway runtime).

Launchd (Gateway as LaunchAgent)

Label:

ai.hanzo.bot.gateway (or ai.hanzo.bot.<profile>; legacy com.hanzo-bot.* may remain)

Plist location (per‑user):

~/Library/LaunchAgents/ai.hanzo.bot.gateway.plist (or ~/Library/LaunchAgents/ai.hanzo.bot.<profile>.plist)

Manager:

The macOS app owns LaunchAgent install/update in Local mode.
The CLI can also install it: hanzo-bot gateway install.

Behavior:

“HanzoBot Active” enables/disables the LaunchAgent.
App quit does not stop the gateway (launchd keeps it alive).
If a Gateway is already running on the configured port, the app attaches to it instead of starting a new one.

Logging:

launchd stdout/err: /tmp/hanzo-bot/hanzo-bot-gateway.log

Version compatibility

The macOS app checks the gateway version against its own version. If they’re incompatible, update the global CLI to match the app version.

Smoke check

hanzo-bot --version

BOT_SKIP_CHANNELS=1 \
BOT_SKIP_CANVAS_HOST=1 \
hanzo-bot gateway --port 18999 --bind loopback

Then:

hanzo-bot gateway call health --url ws://127.0.0.1:18999 --timeout 3000

2.0 KiB Raw Permalink Blame History Unescape Escape