mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
zooqueen
071e3f1082
Automated rebrand of all openclaw references to hanzo bot: - Package: openclaw -> @hanzo/bot - Binary: openclaw -> hanzo-bot - Config: ~/.openclaw -> ~/.hanzo/bot - Docker: ghcr.io/hanzoai/bot - Env vars: OPENCLAW_* -> BOT_* - Bundle IDs: ai.hanzo.bot.* - Product name: Hanzo Bot
1.4 KiB
1.4 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| RPC adapters for external CLIs (signal-cli, legacy imsg) and gateway patterns |
|
RPC Adapters |
RPC adapters
Hanzo Bot integrates external CLIs via JSON-RPC. Two patterns are used today.
Pattern A: HTTP daemon (signal-cli)
signal-cliruns as a daemon with JSON-RPC over HTTP.- Event stream is SSE (
/api/v1/events). - Health probe:
/api/v1/check. - Hanzo Bot owns lifecycle when
channels.signal.autoStart=true.
See Signal for setup and endpoints.
Pattern B: stdio child process (legacy: imsg)
Note: For new iMessage setups, use BlueBubbles instead.
- Hanzo Bot spawns
imsg rpcas a child process (legacy iMessage integration). - JSON-RPC is line-delimited over stdin/stdout (one JSON object per line).
- No TCP port, no daemon required.
Core methods used:
watch.subscribe→ notifications (method: "message")watch.unsubscribesendchats.list(probe/diagnostics)
See iMessage for legacy setup and addressing (chat_id preferred).
Adapter guidelines
- Gateway owns the process (start/stop tied to provider lifecycle).
- Keep RPC clients resilient: timeouts, restart on exit.
- Prefer stable IDs (e.g.,
chat_id) over display strings.