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

4.1 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Troubleshoot node pairing, foreground requirements, permissions, and tool failures

Node is connected but camera/canvas/screen/exec tools fail

You need the node pairing versus approvals mental model

Node Troubleshooting

Node troubleshooting

Use this page when a node is visible in status but node tools fail.

Command ladder

hanzo-bot status
hanzo-bot gateway status
hanzo-bot logs --follow
hanzo-bot doctor
hanzo-bot channels status --probe

Then run node specific checks:

hanzo-bot nodes status
hanzo-bot nodes describe --node <idOrNameOrIp>
hanzo-bot approvals get --node <idOrNameOrIp>

Healthy signals:

Node is connected and paired for role node.
nodes describe includes the capability you are calling.
Exec approvals show expected mode/allowlist.

Foreground requirements

canvas.*, camera.*, and screen.* are foreground only on iOS/Android nodes.

Quick check and fix:

hanzo-bot nodes describe --node <idOrNameOrIp>
hanzo-bot nodes canvas snapshot --node <idOrNameOrIp>
hanzo-bot logs --follow

If you see NODE_BACKGROUND_UNAVAILABLE, bring the node app to the foreground and retry.

Permissions matrix

Capability	iOS	Android	macOS node app	Typical failure code
`camera.snap`, `camera.clip`	Camera (+ mic for clip audio)	Camera (+ mic for clip audio)	Camera (+ mic for clip audio)	`*_PERMISSION_REQUIRED`
`screen.record`	Screen Recording (+ mic optional)	Screen capture prompt (+ mic optional)	Screen Recording	`*_PERMISSION_REQUIRED`
`location.get`	While Using or Always (depends on mode)	Foreground/Background location based on mode	Location permission	`LOCATION_PERMISSION_REQUIRED`
`system.run`	n/a (node host path)	n/a (node host path)	Exec approvals required	`SYSTEM_RUN_DENIED`

Pairing versus approvals

These are different gates:

Device pairing: can this node connect to the gateway?
Exec approvals: can this node run a specific shell command?

Quick checks:

hanzo-bot devices list
hanzo-bot nodes status
hanzo-bot approvals get --node <idOrNameOrIp>
hanzo-bot approvals allowlist add --node <idOrNameOrIp> "/usr/bin/uname"

If pairing is missing, approve the node device first. If pairing is fine but system.run fails, fix exec approvals/allowlist.

Common node error codes

NODE_BACKGROUND_UNAVAILABLE → app is backgrounded; bring it foreground.
CAMERA_DISABLED → camera toggle disabled in node settings.
*_PERMISSION_REQUIRED → OS permission missing/denied.
LOCATION_DISABLED → location mode is off.
LOCATION_PERMISSION_REQUIRED → requested location mode not granted.
LOCATION_BACKGROUND_UNAVAILABLE → app is backgrounded but only While Using permission exists.
SYSTEM_RUN_DENIED: approval required → exec request needs explicit approval.
SYSTEM_RUN_DENIED: allowlist miss → command blocked by allowlist mode. On Windows node hosts, shell-wrapper forms like cmd.exe /c ... are treated as allowlist misses in allowlist mode unless approved via ask flow.

Fast recovery loop

hanzo-bot nodes status
hanzo-bot nodes describe --node <idOrNameOrIp>
hanzo-bot approvals get --node <idOrNameOrIp>
hanzo-bot logs --follow

If still stuck:

Re-approve device pairing.
Re-open node app (foreground).
Re-grant OS permissions.
Recreate/adjust exec approval policy.

4.1 KiB Raw Permalink Blame History