mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
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.1 KiB
1.1 KiB
summary, read_when, title
| summary | read_when | title | |
|---|---|---|---|
| CLI reference for `hanzo-bot agent` (send one agent turn via the Gateway) |
|
agent |
hanzo-bot agent
Run an agent turn via the Gateway (use --local for embedded).
Use --agent <id> to target a configured agent directly.
Related:
- Agent send tool: Agent send
Examples
openclaw agent --to +15555550123 --message "status update" --deliver
openclaw agent --agent ops --message "Summarize logs"
openclaw agent --session-id 1234 --message "Summarize inbox" --thinking medium
openclaw agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
Notes
- When this command triggers
models.jsonregeneration, SecretRef-managed provider credentials are persisted as non-secret markers (for example env var names,secretref-env:ENV_VAR_NAME, orsecretref-managed), not resolved secret plaintext. - Marker writes are source-authoritative: Hanzo Bot persists markers from the active source config snapshot, not from resolved runtime secret values.