Try Hanzo
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.

Read the Docs →
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.

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.
Dev

Our agent.

The coding agent Hanzo builds, with Kai deciding each step. It is the agent Gen opens when none is named.

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
  • OpenCode--opencode
  • Kilo Code--kilo
  • Crush--crush
  • Pi--pi
  • GitHub Copilot CLI--copilot
  • Amp--amp
  • Grok Build--grok
  • Goose--goose
  • Aider--aider
  • Hermes Agent--hermes
  • Cline--cline
  • Continue CLI--continue
  • Oh My Pi--omp
  • Letta Code--letta
  • Kode--kode
  • OpenHands--openhands
  • Open 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 <session-id>           # 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

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.

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.

Gen · Agentic Harness

Universal coding agent harness. Tools, models, and sessions unified.

Run Claude Code, Codex, Dev, and Cursor with the full Hanzo MCP tool suite attached. Route model calls across Hanzo metered models or the agent's native account.

Model Card Specifications
gen
Wire EndpointCLI / Terminal Harness · api.hanzo.ai
Harness Type
Universal coding agent CLI runtime
Supported Agents
Claude Code · Codex · Cursor · Dev · Amp
Tool Attachment
260+ Hanzo MCP tools attached automatically
Cloud Metering
--cloud routes through api.hanzo.ai via Enso
Session Persistence
Linked to your Hanzo account with --resume
Sandbox Fencing
--ask approval gate or microVM isolation
License
MIT Open Source on GitHub
Multi-Language SDKs & OSS Examples
Runnable examples across all tier-one runtimes. Zero-install authentication with hanzo auth login or environment variable HANZO_API_KEY.
bash
# Install Gen and run any coding agent on Hanzo rails
curl -fsSL https://hanzo.sh | sh -s gen

# Run Claude Code with Hanzo MCP tools and metered Enso routing
gen --claude --cloud --model enso-ultra "fix the failing test in api/users"

Enterprise Solutions

Battle-tested universal coding agent harness for engineering organizations.

Bring any agent into production with enterprise MCP tool integration, cloud session telemetry, and zero provider lock-in.

04HARNESS OPS
Stack: Kata + Gen + Enso

Universal Agent Deployment & Fleet Management

Standardizes Claude Code, Codex, Cursor, and Dev behind one CLI. Equips agents with 260+ Hanzo MCP tools and automatically links session telemetry to your enterprise account.
Value Impact:$55M–$552M capacity value
05BATCH REFACTOR
Stack: Gen + Kata

Headless Monolith Modernization & Code Migration

Executes long-running headless refactoring jobs with `gen --codex "migrate auth" --cloud`. Runs inside isolated microVMs with strict approval boundaries and PR verification.
Value Impact:10x refactor velocity
07INTERNAL TOOLING
Stack: Gen + Zen + Kai

Associate & Engineer Copilot Terminal Gateway

Single-binary distribution via `hanzo.sh`. Connects terminal developers to sovereign cloud LLMs and private DGX clusters without managing local virtualenvs or API key drift.
Value Impact:Zero setup friction

Read

The harness, the agent, the CLI.

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

Paste and ship

Paste this into any agent. It reads the skill manifest and calls Gen from there.

Agent prompt
Read https://hanzo.ai/skill.md and use Hanzo Gen in my project. Start with: gen

Bring any coding agent onto Hanzo rails. MCP tools, cloud telemetry, and zero lock-in.