hanzo — AI engineer in your terminal

The Hanzo CLI. One binary to code with an AI agent, sign in, and deploy, manage, and interact with the Open AI Cloud — plus run the network. Written in Rust: a single static binary, rustls TLS, no runtime, no daemon.

hanzo "add pagination to the /v1/orders endpoint and write the tests"

Install

curl -fsSL https://raw.githubusercontent.com/hanzoai/cli/main/install.sh | sh

The installer resolves the release asset for your platform (linux · macOS · Windows, amd64 · arm64), verifies its sha256, and drops the hanzo binary in ~/.local/bin.

While hanzoai/cli is private the installer needs a GitHub token — gh auth login first, or GH_TOKEN=… sh install.sh. Public curl | sh self-service works the moment the repo is public; nothing else changes.

From source (Rust toolchain):

git clone https://github.com/hanzoai/cli && cd cli
cargo install --path .

Quick start

# Sign in — interactive picker: Hanzo (OIDC) · OpenAI · Anthropic · paste a key
hanzo auth login

# Bare `hanzo` IS an AI engineer in your terminal — an interactive coding session,
# linked to your cloud (mission-control) when you're signed in.
hanzo

# Or run a task headless
hanzo "fix the failing test in api/handlers.go"

# Who am I, and what's left in the tank
hanzo auth show
hanzo usage

Coding — bare hanzo

hanzo wraps a local coding agent (Claude Code or dev) as a session-aware, resumable, portable object: the Hanzo MCP toolset is attached, model calls route through your metered Hanzo cloud, and a signed-in session streams live to mission-control. Auto-approve is on by default; the repo's own .mcp.json is trust-gated off unless you opt in.

hanzo --model enso-ultra "refactor the auth middleware"
hanzo --backend dev "port this module to async"
hanzo --resume <session-id>          # continue a prior session
hanzo --ask "…"                      # confirm each action (alias: --safe)
hanzo --no-link "…"                  # keep it local, don't stream to cloud
hanzo --no-route "…"                 # use the backend's own model account

Zen models (enso, enso-ultra, enso-flash, zen5-coder, …) are Hanzo's own family; the gateway is the sole authority on the model catalog.

Commands

The CLI is a resource-noun tree — hanzo <resource> <command>. Cloud capabilities beyond the hand-written resources appear as first-class generated product subcommands (hanzo <product> <resource…> <verb>, typed from the OpenAPI specs) — the one interface to api.hanzo.ai/v1. There is no hanzo api verb and no raw-path escape.

Identity & billing

Multi-identity, like gh auth switch — hold many principals at once and switch between them; a second login never clobbers the first.

hanzo auth login [--provider hanzo|openai|anthropic] [--token -]
hanzo auth show                 # the active identity
hanzo auth list                 # every identity, active one marked
hanzo auth use [owner/name]     # switch active identity
hanzo auth logout [identity] [--all]
hanzo usage                     # stacked per-account balances, each read with its own token
hanzo billing balance | deposit
hanzo connector add|list|verify|rm --provider cloudflare

Secrets arrive on stdin only, never argv (--token -) — nothing lands in shell history, ps, or CI logs. Credentials live in the OS keychain (macOS / Windows) or an owner-only 0600 file otherwise.

Cloud

hanzo agent run …                        # run managed AI tasks
hanzo cluster create|list|show|use|delete
hanzo model serve <model>                # serve a model locally via the Hanzo engine (/v1 endpoint)
hanzo serve cloud|iam|kms|gateway|storage|pubsub   # run a Hanzo service on your machine

Network & wallet

hanzo network list|current|use <name>|add <name> …   # sovereign L1: network_id == chain_id
hanzo wallet show|address|create [--local]|import|use|list   # PQ cloud custody (KMS/MPC) or local keychain

Fabric & fleet — hanzo.network

hanzo fabric …                  # run/join the L1 fabric with hanzod, query its model cluster
hanzo node join|leave|list|show # your machine in the compute fleet
hanzo runner …                  # provide this machine as a CI runner

Build & ship

hanzo init [template]           # scaffold a new project
hanzo dev [--port <n>] [--hot]  # local development server
hanzo share <port|host:port|url># public https://<token>.share.hanzo.ai URL on the zero-trust fabric
hanzo secret scan <path>        # find exposed secrets before you commit

SDK tooling

hanzo docs   # @hanzo/docs-cli
hanzo mdx    # @hanzo/mdx
hanzo ui     # @hanzo/ui
hanzo mcp    # @hanzo/mcp

Configuration

• hanzo config list | get <key> | set <key> <value> — non-secret local settings, stored at ~/.config/hanzo/config.toml (network selection, active identity index, custom networks). Never holds token material.
• ~/.hanzo/settings.json — coding-agent defaults: model, smallFastModel, autoApprove, mcp, contextWindow. Every key is optional; an explicit CLI flag or process env always wins.

Global flags valid on any subcommand: --config <file>, --verbose.

Build from source

cargo build            # build gate
cargo test             # full suite: unit tests + shipped-binary tests (assert_cmd)
cargo clippy --bin hanzo

tests/cli.rs runs the real binary with real argv and exit codes; state is isolated behind --config <tempdir>. The live auth flow is gated on HANZO_E2E_TOKEN (a real hanzo.id bearer) and honestly skips when absent.

Contributing

Issues and PRs welcome — see CONTRIBUTING.md.

License

MIT © Hanzo AI

Support

• Docs: https://docs.hanzo.ai
• Issues: https://github.com/hanzoai/cli/issues
• Email: support@hanzo.ai

Hanzo — the Open AI Cloud

Open source · every language · on-chain settlement. hanzo.ai · docs.hanzo.ai

SDKs in every language — Python (flagship) · TypeScript · Go · Rust · C++ · Swift · Kotlin · umbrella