# Hanzo Gen — any coding agent, on Hanzo’s rails

> Gen runs the coding agent you already use — Claude Code, Codex, Cursor and more — with the Hanzo toolset attached, on Hanzo’s metered models or the agent’s own account, every session linked to your Hanzo account. One line installs it: curl -fsSL https://hanzo.sh | sh -s gen. Open source, MIT.

Hanzo Gen · Agentic harness

# Any agent.Our rails.

Gen runs the coding agent you already use — Claude Code, Codex, Cursor and more — with Hanzo’s tools attached and every session linked to your Hanzo account: on Hanzo’s models, metered, or on the agent’s own account.

[Install gen](#install)[View on GitHub](https://github.com/hanzoai/gen)

[Hanzo Dev, our agent →](https://hanzo.ai/dev)

terminal

$curl -fsSL https://hanzo.sh | sh -s gen

$gen

no agent named: Hanzo Dev

$gen --claude

Claude Code, with the Hanzo toolset attached

$gen --codex "add a test"

Codex, run headless on the task

$gen --claude --cloud

its model calls on Hanzo’s, metered on your account

$

Install

## One line, then any agent.

Linux and macOS. hanzo.sh downloads gen’s native build and checks it: its checksum always, its provenance with a signed-in gh. Run it again to upgrade.

bash

```
curl -fsSL https://hanzo.sh | sh -s gen # gen alone curl -fsSL https://hanzo.sh | sh # or every Hanzo tool, gen included
```

bash

```
gen # Hanzo Dev, the default gen --claude # Claude Code; any agent is a flag gen --codex "add a test" # a task, run headless
```

Sign in once with the Hanzo CLI, hanzo auth login, and every session is linked to your account.

[Every build →](https://github.com/hanzoai/gen/releases)

Gen and Dev

## One runs agents. One is an agent.

Gen

### The harness. Any agent, our rails.

It launches the coding agent you name with Hanzo’s tools attached, routes its model calls through Hanzo when you ask, and links the session to your account.[hanzoai/gen →](https://github.com/hanzoai/gen)

Dev

### Our agent.

The coding agent Hanzo builds, with Kai deciding each step. It is the agent Gen opens when none is named.[Hanzo Dev →](https://hanzo.ai/dev)

Agents

## The agent you use is a flag.

Each launches as itself, with its own interface and its own habits, and Gen around it. gen --help lists every one.

- Hanzo Dev--dev
- Claude Code--claude
- Codex--codex
- Cursor--cursor
- Antigravity--agy
- Gemini CLI--gemini
- oOpenCode--opencode
- kKilo Code--kilo
- cCrush--crush
- pPi--pi
- GitHub Copilot CLI--copilot
- aAmp--amp
- Grok Build--grok
- gGoose--goose
- aAider--aider
- Hermes Agent--hermes
- cCline--cline
- cContinue CLI--continue
- oOh My Pi--omp
- lLetta Code--letta
- kKode--kode
- oOpenHands--openhands
- iOpen Interpreter--interpreter

Our rails

## What Gen puts around it.

Tools, models, sessions and fences, each set by a flag.

### Tools

The Hanzo MCP toolset rides along on every agent that can take a server for one run.--no-mcp

### Models

Its model calls go to api.hanzo.ai, metered on your account, for an agent that can name another endpoint. Without the flag, an agent uses the account it is signed in to.--cloud --model

### Sessions

Signed in, a session is linked to your Hanzo account and streams to mission control as it runs, so it can be followed and picked back up.--resume --no-link

### Fences

Sessions are approved inside a sandbox; ask before each action instead. A repository’s own .mcp.json stays off until you trust it.--ask --project-mcp

bash

```
gen --claude --cloud # its model calls through api.hanzo.ai gen --claude --cloud --model enso-ultra gen --codex --no-link # keep the session on this machine gen --resume # pick a linked session back up gen --claude -- -c # after --, the agent's own arguments
```

In the Hanzo CLI

## The same harness, as hanzo dev.

The Hanzo CLI links Gen, so hanzo dev takes the same flags and runs the same session. Use whichever is on your path.

bash

```
hanzo dev # gen hanzo dev --claude # gen --claude hanzo dev --codex --cloud # gen --codex --cloud
```

[The Hanzo CLI →](https://hanzo.ai/cli)

Open source

## MIT, in the open.

The harness, every agent's launcher and how its output is read are on GitHub, one file an agent.

[The source →](https://github.com/hanzoai/gen)

Questions

## Asked plainly.

How do I install it?

curl -fsSL https://hanzo.sh | sh -s gen installs gen alone; curl -fsSL https://hanzo.sh | sh installs every Hanzo tool, gen and the Hanzo CLI included. Run either again to upgrade. On Windows, take the build from the release page.

Is gen the same as hanzo dev?

The same harness. The Hanzo CLI links it, so gen --claude and hanzo dev --claude take the same flags and run the same session. Bare gen, like bare hanzo dev, opens Hanzo Dev.

Does every agent run on Hanzo’s models?

Only when you pass --cloud, and only an agent that can name another endpoint. Without it, each agent keeps the account it is signed in to.

What does Hanzo bill?

On --cloud, the agent’s model calls, on your Hanzo account. On the agent’s own account, only what Hanzo’s tools handled for it.

Does Gen change the agent?

No. Each agent runs as itself — its own interface and its own commands — and anything after -- goes to it untouched.

What license is it under?

MIT. The source is hanzoai/gen on GitHub.

Read

## The harness, the agent, the CLI.

Where to get Gen, what it runs, and the same harness in the CLI.

### Gen

[hanzoai/genMIT.](https://github.com/hanzoai/gen)[The agents](#agents)[Installcurl -fsSL https://hanzo.sh | sh -s gen](#install)[Releases](https://github.com/hanzoai/gen/releases)

### Dev

[Hanzo DevOur agent, Gen’s default.](https://hanzo.ai/dev)[KaiDev’s controller.](https://hanzo.ai/kai)

### Models

[Enso](https://hanzo.ai/enso)[Every model](https://hanzo.ai/models)[Hanzo CLI](https://hanzo.ai/cli)

## Bring your agent. Keep your habits.

[Try Hanzo](https://hanzo.ai/login)[View on GitHub](https://github.com/hanzoai/gen)