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

Files

T

zeekay 08582cc303 Rebrand OpenClaw → Hanzo Bot across entire codebase

Complete rename of all OpenClaw/OPENCLAW/openclaw references to
Hanzo Bot/BOT/bot naming convention:

- Env vars: OPENCLAW_* → BOT_* (18 patterns)
- Config: ~/.openclaw/ → ~/.bot/, openclaw.json → bot.json
- Packages: @openclaw/* → @hanzo/bot-*
- Domains: openclaw.ai → hanzo.bot
- Mobile: OpenClawKit → BotKit, bundle IDs ai.openclaw → ai.hanzo.bot
- mDNS: _openclaw-gw._tcp → _bot-gw._tcp
- Docker: CMD hanzo-bot.mjs, BOT_PREFER_PNPM, BOT_DOCKER_APT_PACKAGES
- CI: docker-release.yml adds :latest tag on main branch

2026-02-11 11:13:08 -08:00

2.1 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

PeekabooBridge integration for macOS UI automation

Hosting PeekabooBridge in Hanzo Bot.app

Integrating Peekaboo via Swift Package Manager

Changing PeekabooBridge protocol/paths

Peekaboo Bridge

Peekaboo Bridge (macOS UI automation)

Hanzo Bot can host PeekabooBridge as a local, permission‑aware UI automation broker. This lets the peekaboo CLI drive UI automation while reusing the macOS app’s TCC permissions.

What this is (and isn’t)

Host: Hanzo Bot.app can act as a PeekabooBridge host.
Client: use the peekaboo CLI (no separate hanzo-bot ui ... surface).
UI: visual overlays stay in Peekaboo.app; Hanzo Bot is a thin broker host.

Enable the bridge

In the macOS app:

Settings → Enable Peekaboo Bridge

When enabled, Hanzo Bot starts a local UNIX socket server. If disabled, the host is stopped and peekaboo will fall back to other available hosts.

Client discovery order

Peekaboo clients typically try hosts in this order:

Peekaboo.app (full UX)
Claude.app (if installed)
Hanzo Bot.app (thin broker)

Use peekaboo bridge status --verbose to see which host is active and which socket path is in use. You can override with:

export PEEKABOO_BRIDGE_SOCKET=/path/to/bridge.sock

Security & permissions

The bridge validates caller code signatures; an allowlist of TeamIDs is enforced (Peekaboo host TeamID + Hanzo Bot app TeamID).
Requests time out after ~10 seconds.
If required permissions are missing, the bridge returns a clear error message rather than launching System Settings.

Snapshot behavior (automation)

Snapshots are stored in memory and expire automatically after a short window. If you need longer retention, re‑capture from the client.

Troubleshooting

If peekaboo reports “bridge client is not authorized”, ensure the client is properly signed or run the host with PEEKABOO_ALLOW_UNSIGNED_SOCKET_CLIENTS=1 in debug mode only.
If no hosts are found, open one of the host apps (Peekaboo.app or Hanzo Bot.app) and confirm permissions are granted.

2.1 KiB Raw Permalink Blame History Unescape Escape