Install Zeno in one paste.
Copy the ready prompt into Claude Code. It installs the Zeno CLI, wires the cognition HUD line into your statusline, and verifies the setup - then tells you if anything failed. Prefer to drive it yourself? Three commands are right below.
The one-paste install
Already running Claude Code? Paste this in. Claude Code reads it as instructions and runs the whole install for you, dry-run-gated so nothing touches your config without showing you the diff first.
Install the zeno CLI and its Claude Code cognition HUD add-on for me. Steps: (1) install the CLI with `uv tool install zeno-cli` (fall back to `pipx install zeno-cli` if `uv` is missing); (2) run `zeno hud install` to auto-detect my statusline (ccstatusline or claude-hud) and wire the `zeno-hud-bar` cognition line - use `--dry-run` first and show me the diff before writing; (3) run `zeno doctor` and `zeno hud status` to verify; (4) confirm the att/eff/drv line renders and tell me if anything failed.
- 01
Installs the
zenoCLI from PyPI withuv, falling back topipx. - 02
Detects your statusline (ccstatusline or claude-hud) and stacks the
zeno-hud-barcognition line under it - or runs it standalone if you have neither. - 03
Previews every change with
--dry-runand waits for your go-ahead before writing. - 04
Runs
zeno doctor+zeno hud statusand reports the result.
Prefer to run it yourself
Same three steps, by hand. Each block copies with one click.
-
Install the CLI
One command. Python ≥ 3.12. The CLI talks to your private endpoint, never the public internet.
uv tool install zeno-cli
-
Wire the HUD add-on
Auto-detects your statusline and stacks the cognition line under it.
--dry-runprints the diff and writes nothing.zeno hud install --dry-run zeno hud install
-
Verify
Confirm the daemon reaches your endpoint and the
att/eff/drvline is wired in.zeno doctor zeno hud status
zeno-cli on PyPI is rolling out to invitees. Until your invite lands, install from the wheel - uv tool install ./dist/zeno_cli-*.whl from the monorepo (see apps/cli/README.md). The HUD steps are unchanged.What lands in your statusline
One differentiated line, stacked under whatever HUD you already run. It updates every turn from your real Claude Code activity.
- att
Composite attention - the headline read, with its nudge and the most-deviant driver tagged when it matters.
- eff
How hard you are driving this turn (the effort driver).
- drv
How hands-on you are versus delegating - the operator's share of the wheel.
Requirements
- Python ≥ 3.12 - the CLI installs cleanly under
uvorpipx. - Claude Code - the cognition line reads your live session activity. A bridge hook feeds it automatically; no manual session start.
- A statusline, or none -
zeno hud installstacks under ccstatusline or claude-hud, or runs the bar standalone. - Local-first - capture stays on your machine and your private tailnet. Nothing leaves your network during early access.
Questions
Do I need ccstatusline or claude-hud?
No. zeno hud install auto-detects either and stacks the cognition line under it. If you run neither, the zeno-hud-bar is a perfectly good standalone statusline on its own.
Will it overwrite my statusline config?
Not without showing you first. Run zeno hud install --dry-run to print the exact diff and write nothing. The one-paste prompt always runs the dry-run before applying.
Is anything sent off my machine?
No. Capture is local-first - it stays on your machine and your private tailnet. The dashboard reads your sessions over your own network during early access.
How do I remove it?
Run zeno hud uninstall (add --restore for a byte-for-byte revert of your statusline config).
Next
Installed? See the signal calibrate on your real work.