zeekay 4c0fcb9bbe dev: the session is Hanzo Gen's, with this CLI as its host ...

The coding harness moved to hanzoai/gen with its history (src/commands/
code, private, iam/native, the savings model, the Claude themes). This
CLI now depends on hanzo-gen by pinned rev and keeps what only it can
answer: commands/dev.rs is the Host (the IAM store, the provider vault,
network, org and code.* config) plus the one session launcher, and
commands/savings.rs is the meter read through the authenticated seam.

hanzo, hanzo dev, hanzo desktop and hanzo sandbox run flatten Gen's Args
unchanged, so every help screen and dispatch answer is byte-identical.
Gen's hanzo-client is this repository's crates/client by pinned commit;
a [patch] resolves it to the path, so one copy links.

link's three session tests ask the CLI's own fake control plane, since
Gen's mock cloud is Gen's to test with.

2026-10-16 10:45:00 -07:00

..

dracula.json

hanzo — the Hanzo CLI

2026-07-17 10:15:57 -07:00