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

Files

T

zooqueen 071e3f1082 rebrand: openclaw -> hanzo bot across entire codebase

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

2026-03-19 13:52:32 -07:00

2.2 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

CLI reference for `hanzo-bot daemon` (legacy alias for gateway service management)

You still use `hanzo-bot daemon ...` in scripts

You need service lifecycle commands (install/start/stop/restart/status)

daemon

`hanzo-bot daemon`

Legacy alias for Gateway service management commands.

hanzo-bot daemon ... maps to the same service control surface as hanzo-bot gateway ... service commands.

Usage

openclaw daemon status
openclaw daemon install
openclaw daemon start
openclaw daemon stop
openclaw daemon restart
openclaw daemon uninstall

Subcommands

status: show service install state and probe Gateway health
install: install service (launchd/systemd/schtasks)
uninstall: remove service
start: start service
stop: stop service
restart: restart service

Common options

status: --url, --token, --password, --timeout, --no-probe, --require-rpc, --deep, --json
install: --port, --runtime <node|bun>, --token, --force, --json
lifecycle (uninstall|start|stop|restart): --json

Notes:

status resolves configured auth SecretRefs for probe auth when possible.
If a required auth SecretRef is unresolved in this command path, daemon status --json reports rpc.authWarning when probe connectivity/auth fails; pass --token/--password explicitly or resolve the secret source first.
If the probe succeeds, unresolved auth-ref warnings are suppressed to avoid false positives.
On Linux systemd installs, status token-drift checks include both Environment= and EnvironmentFile= unit sources.
When token auth requires a token and gateway.auth.token is SecretRef-managed, install validates that the SecretRef is resolvable but does not persist the resolved token into service environment metadata.
If token auth requires a token and the configured token SecretRef is unresolved, install fails closed.
If both gateway.auth.token and gateway.auth.password are configured and gateway.auth.mode is unset, install is blocked until mode is set explicitly.

Prefer

Use hanzo-bot gateway for current docs and examples.

2.2 KiB Raw Permalink Blame History

hanzo-bot daemon