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

Files

T

zeekay 21c07d9112 Rename OPENCLAW_* env vars to BOT_*

The codebase already had 663 BOT_* env-var refs from a partial migration
(BOT_CONFIG_PATH, BOT_SHELL, BOT_GATEWAY_BIND, …). Finish the rename:
every remaining OPENCLAW_ prefix becomes BOT_, unifying the env-var
surface on a single brand-neutral prefix.

3493 occurrences across 684 files (src/, test/, extensions/, apps/*/,
docs/, scripts/, infra configs). Clean break — no backwards-compat
reads. Users with existing OPENCLAW_* exports need to rename those.

Out of scope (separate change):
  - the ai.openclaw.android.* Java package (partial migration to
    ai.hanzo.bot.android.* already in place; finishing it requires
    moving files + AndroidManifest + applicationId + signing)
  - __openclaw__/ HTTP path prefix served by the gateway

2026-05-11 15:40:59 -07:00

796 B

Raw Permalink Blame History

Hanzo Bot Chrome Extension (Browser Relay)

Purpose: attach Hanzo Bot to an existing Chrome tab so the Gateway can automate it (via the local CDP relay server).

Dev / load unpacked

Build/run Hanzo Bot Gateway with browser control enabled.
Ensure the relay server is reachable at http://127.0.0.1:18792/ (default).

Install the extension to a stable path:

hanzo-bot browser extension install
hanzo-bot browser extension path

Chrome → chrome://extensions → enable “Developer mode”.
“Load unpacked” → select the path printed above.
Pin the extension. Click the icon on a tab to attach/detach.

Options

Relay port: defaults to 18792.
Gateway token: required. Set this to gateway.auth.token (or BOT_GATEWAY_TOKEN).

796 B Raw Permalink Blame History

Hanzo Bot Chrome Extension (Browser Relay)

Dev / load unpacked

Options

796 B

Raw Permalink Blame History