Files
bot/docs/help/scripts.md
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

898 B
Raw Permalink Blame History

summary, read_when, title
summary read_when title
Repository scripts: purpose, scope, and safety notes
Running scripts from the repo
Adding or changing scripts under ./scripts
Scripts

Scripts

The scripts/ directory contains helper scripts for local workflows and ops tasks. Use these when a task is clearly tied to a script; otherwise prefer the CLI.

Conventions

  • Scripts are optional unless referenced in docs or release checklists.
  • Prefer CLI surfaces when they exist (example: auth monitoring uses hanzo-bot models status --check).
  • Assume scripts are host‑specific; read them before running on a new machine.

Auth monitoring scripts

Auth monitoring scripts are documented here: /automation/auth-monitoring

When adding scripts

  • Keep scripts focused and documented.
  • Add a short entry in the relevant doc (or create one if missing).