Skip to content

docs: install leads with npm i -g hanzo, then hanzo dev #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zooqueen merged 1 commit into from
Nov 5, 2026
Merged

docs: install leads with npm i -g hanzo, then hanzo dev #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,18 +10,22 @@ repository you point it at, and runs commands in a sandbox. It reaches every
model [Hanzo AI](https://hanzo.ai) serves — hundreds of them, `enso` and the
`zen5` family included — through one metered gateway at `api.hanzo.ai`.

It ships inside the Hanzo CLI. `hanzo dev` is the command, or install standalone via `npm i -g @hanzo/dev`. Web portal: [https://hanzo.ai](https://hanzo.ai).
It ships inside the Hanzo CLI: `npm i -g hanzo`, then `hanzo dev`. Web portal: [https://hanzo.ai](https://hanzo.ai).

## Install

Any OS, Windows included:

```bash
curl -fsSL https://hanzo.sh | sh
npm i -g hanzo # or, on macOS/Linux: curl -fsSL https://hanzo.sh | sh
hanzo auth login
```

That fetches one prebuilt native binary per tool and verifies its checksum.
`npm i -g @hanzo/dev` installs the agent on its own if you would rather have it
from npm; both give you the same build.
`npm i -g hanzo` installs a small launcher. The native binaries are fetched on
first use and their SHA-256 checked: `hanzo dev` downloads the agent (`dev`) and
the Hanzo MCP server it attaches (`hanzo-mcp`).

Standalone alternative: `npm i -g @hanzo/dev` installs just the agent (`dev`), same build.

`hanzo auth login` signs you in through Hanzo IAM and links the machine to your
account. Then, from any repository:
Expand Down
7 changes: 5 additions & 2 deletions docs/advanced.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,11 +7,14 @@ Run Hanzo Dev headless in pipelines. Example GitHub Action step:
```yaml
- name: Update changelog via Dev
run: |
npm install -g @hanzo/dev
npm i -g hanzo
export HANZO_API_KEY="${{ secrets.HANZO_API_KEY }}"
dev exec --full-auto "update CHANGELOG for next release"
hanzo dev "update CHANGELOG for next release"
```

With the standalone agent instead: `npm i -g @hanzo/dev`, then
`dev exec --full-auto "update CHANGELOG for next release"`.

### Resuming non-interactive sessions

You can resume a previous headless run to continue the same conversation context and append to the same rollout file.
Expand Down