mirror of
https://github.com/hanzoai/helper.git
synced 2026-09-30 22:42:13 +00:00
zeekayandHanzo Dev
ccdef7d8fb
@hanzo/[email protected] declared `"bin": {"hanzo": "dist/cli.js"}`, so `npm i -g @hanzo/helper` put a second program named `hanzo` on PATH next to the Hanzo CLI (v1.9.18, from hanzo.sh / brew). Whichever came first on PATH won, and the two disagree about every verb: in the real CLI signing in is `hanzo auth login`, and a bare `hanzo login` is swallowed as an AI task. Renamed to `hanzo-helper`, and the same for the white-label builds: lux-helper / zoo-helper / zen-helper. @hanzo/kms keeps `kms` — no collision. Nothing is unpublished; 1.0.7 stays on npm. The README's command table was the old bin name throughout, and its "smart tiers" table documented `zen-auto` / `zen-normal` / `zen-pro` / `zen-max` / `zen-code` / `zen-agent` as models you can ask for. The live catalog has none of them — the authenticated /v1/models returns 105 ids whose Zen family is zen5, zen5-coder, zen5-flash, zen5-mini, zen5-pro, enso, enso-flash, enso-ultra plus the zen-<modality> models. Table cut; the README now says to read the catalog. (`models.ts` already checks aliases against the live catalog before printing them, so the code was honest and only the prose was not.) `use --model` help stopped advertising the same six words. In-program prose said `hanzo login` / `hanzo status` / `hanzo kms` in 15 files — all now `hanzo-helper`, verified by running the built CLI. Also dropped "every model (Claude, GLM, GPT, DeepSeek, Kimi, ...)" from the opening: we describe our own catalog. Naming Claude Code and Codex stays — this program's whole job is configuring them, which is a fact about the tool, not a benchmark. Left alone, for the model-routing owner: DEFAULT_MODEL is still the upstream id `glm-5.2`, which commander prints as the advertised default of `--model`. Co-authored-by: Hanzo Dev <[email protected]>