hanzo.sh/public/llms.txt

# Hanzo CLI

> Command-line tools for the Hanzo cloud.

## About
`hanzo` is the Hanzo cloud CLI: authentication, billing, coding sessions, and
every product of the Hanzo cloud from the terminal. It is a native binary — one
download per tool, checksum-verified, no runtime and no package manager.

## Install
A single command, and it is the only one:

```sh
curl -fsSL https://hanzo.sh | sh
```

That installs every Hanzo tool published as a public native binary:

- `hanzo` — the CLI (also installed as `hanzo-node`, the same build)
- `hanzo-mcp` — the MCP server (also installed as `mcp`, the same build)
- `dev` — Hanzo Dev, the coding agent `hanzo dev` runs by default
- `gen` — Hanzo Gen, the harness that launches and routes any coding agent
- `zt` — ZT zero-trust networking: tunnel, controller and router

One tool at a time:

```sh
curl -fsSL https://hanzo.sh/cli | sh    # the CLI only
curl -fsSL https://hanzo.sh/mcp | sh    # the MCP server only
curl -fsSL https://hanzo.sh/dev | sh    # the coding agent only
```

Binaries land in `~/.local/bin`. Re-run to upgrade — installing is just
downloading the current build. Published for linux and macOS on amd64 and arm64,
and windows on amd64.

## From a coding agent
Paste this into Claude Code, Codex, Cursor or Antigravity and the agent installs
the CLI, then tells you to run `hanzo`:

```
Set up Hanzo on this machine: follow https://hanzo.sh/setup.md
```

The procedure is https://hanzo.sh/setup.md.

## Usage
Every command below exists in the shipped binary; `hanzo --help` lists them all.

```sh
# First run: signs you in through the browser, links the machine to Hanzo Tabs,
# asks once which coding agent is your favourite, adds Hanzo's tools to it and
# launches it accelerated. After that, `hanzo` alone launches your favourite.
hanzo

# Switch agent (saved as your favourite), or run Hanzo Dev
hanzo dev --claude      # --codex, --cursor, --agy; plain `hanzo dev` is Hanzo Dev
hanzo dev "fix the failing test"

# Continue the last conversation
hanzo -- -c

# Sign in on its own, and check who you are
hanzo login
hanzo auth show

# Point an agent at the desktop and browser instead of the repo
hanzo desktop

# Money and metering
hanzo billing balance
hanzo usage summary

# Bring your own cloud
hanzo cloud list
hanzo cloud accounts

# Run the MCP server
hanzo-mcp
```

A group name is not a command on its own: `hanzo usage` and `hanzo auth` print
their subcommands and stop.

`hanzo engine serve <model>` runs a model locally on an OpenAI-compatible
endpoint. It needs the Hanzo engine binary, which this installer does not ship;
with no `hanzo-engine` on PATH and no `HANZO_ENGINE_BIN` set it exits saying so.

## Models
Hanzo's own families, and the ids these tools take: `enso`, `enso-flash`,
`enso-ultra`, and `zen5`, `zen5-pro`, `zen5-coder`, `zen5-flash`, `zen5-mini`,
plus the single-purpose `zen-embedding`, `zen-rerank`, `zen-guard`, `zen-vl`,
`zen-image`, `zen-video`, `zen-voice`, `zen-music`, `zen-foley`. The live list is
`https://catalog.hanzo.ai/v1/models`, and the gateway is the sole authority on
it. `https://api.hanzo.ai/v1/models` answers the same question for a signed-in
caller and returns 401 without a bearer token.

## Links
- [Website](https://hanzo.sh)
- [Documentation](https://docs.hanzo.ai)
- [CLI source](https://github.com/hanzoai/cli)
- [MCP source](https://github.com/hanzoai/mcp)
- [Dev source](https://github.com/hanzoai/dev)
- [Gen source](https://github.com/hanzoai/gen)

## Contact
- Support: [email protected]
- Issues: https://github.com/hanzoai/cli/issues