hanzoai/docs
2
0
Fork 0
mirror of https://github.com/hanzo-docs/docs.git synced 2026-10-24 20:09:02 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Coding agents: hanzo upgrade runs each agent's own updater, uv for Aider and OpenHands
Hanzo CI/CD / test (linux-amd64) (push) Skipped
Details
Hanzo CI/CD / test (linux-arm64) (push) Skipped
Details
Hanzo CI/CD / test-advisory (push) Skipped
Details
Hanzo CI/CD / test-amd64 (push) Successful in 13m15s
Details
Hanzo CI/CD / cicd (push) Successful in 1h14m14s
Details
CI/CD / cicd (push) Successful in 1h27m34s
Details

Browse Source 
Claude-Session: https://claude.ai/code/session_01M8RoubcPN71KgJuZ8LdBUL
This commit is contained in:
zeekay
2026-10-14 23:26:58 -07:00
parent 200e317789
commit f5db8298f8
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/content/docs/guides/coding/agents.mdx
+1 -1
View File
@@ -5,7 +5,7 @@ description: "Gemini CLI, Qwen Code, OpenCode, Kilo Code, Crush, Pi, GitHub Copi
Each agent here keeps its own login, settings and sessions. For one run, `hanzo --<agent>` hands it the Hanzo toolset the way that agent reads servers, and under `--cloud` it points the agent's model calls at api.hanzo.ai. Nothing is written into the agent's own configuration. Your Hanzo token reaches the agent through its environment, never its arguments.
Install any of them with `hanzo upgrade <agent>`. It runs `npm install` under `~/.hanzo`, so the binary lands in `~/.hanzo/bin`, and `hanzo upgrade` with no arguments keeps them current. This needs Node.js 20 or newer. An agent you already installed elsewhere is found on your PATH.
Install an npm agent with `hanzo upgrade <agent>`. It runs `npm install` under `~/.hanzo`, so the binary lands in `~/.hanzo/bin`, and `hanzo --<agent>` runs that copy before one on your PATH. This needs Node.js 20 or newer. An agent with its own installer is installed once with it, and then `hanzo upgrade <agent>` runs its own updater. `hanzo upgrade` with no arguments keeps every installed agent current.
## Gemini CLI
apps/docs/content/docs/guides/coding/index.mdx
+3 -3
View File
@@ -97,11 +97,11 @@ Every number Hanzo publishes about Kai and the toolset is a research run, with e
## Keep everything up to date
```bash
hanzo upgrade # hanzo, hanzo-mcp, dev and zt, and every agent installed under ~/.hanzo
hanzo upgrade mcp qwen # just these
hanzo upgrade # hanzo, hanzo-mcp, dev and zt, and every coding agent installed
hanzo upgrade mcp qwen claude # just these
```
`hanzo upgrade` runs [hanzo.sh](https://hanzo.sh) into the directory `hanzo` lives in, so the build that answers `hanzo` is the one that was upgraded. Every Hanzo tool is a native binary for Linux and macOS on amd64 and arm64. `hanzo`, `dev` and `zt` also ship for Windows on amd64, from their GitHub release pages. `hanzo-mcp` does not: its browser bridge speaks a Unix socket, so on Windows `hanzo` runs each agent without the toolset and says so.
`hanzo upgrade` runs [hanzo.sh](https://hanzo.sh) into the directory `hanzo` lives in, so the build that answers `hanzo` is the one that was upgraded. Each agent upgrades its own way: an npm agent is installed again under `~/.hanzo`, one with an updater of its own runs it (`claude update`, `codex update`, `cursor-agent update`, `agy update`, `goose update`, `grok update`, `hermes update`, `interpreter update`), and Aider and OpenHands are upgraded with `uv tool upgrade`. With nothing named, every agent installed that way is upgraded. Every Hanzo tool is a native binary for Linux and macOS on amd64 and arm64. `hanzo`, `dev` and `zt` also ship for Windows on amd64, from their GitHub release pages. `hanzo-mcp` does not: its browser bridge speaks a Unix socket, so on Windows `hanzo` runs each agent without the toolset and says so.
## Options that apply to every agent