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

Files

T

zeekay 4bdc9ee3e4 chore: rebrand openclaw → hanzo-bot for bridge merge

Comprehensive rename of all openclaw references to hanzo-bot equivalents:
- Package: openclaw → @hanzo/bot
- Binary: openclaw → hanzo-bot
- Types: OpenClaw* → Bot*
- Env vars: OPENCLAW_* → BOT_*
- Android: ai.openclaw.android → ai.hanzo.bot.android
- iOS/macOS: ai.openclaw.* → ai.hanzo.*
- Swift modules: OpenClaw* → Bot*
- Plugins: openclaw.plugin.json → bot.plugin.json
- Paths: .openclaw/ → .hanzo/bot/
- URLs: github.com/openclaw → github.com/hanzoai

2026-02-26 22:36:01 -08: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