Build
CLI
The same presence you raised in the app — now in your terminal, and in your scripts.
The CLI does not create a different agent. It authenticates as you and talks to your one presence over the same API. A memory pinned from the terminal is in the browser a second later — there is only ever the one.
Install
npm i -g yuzu
# or, no install
npx yuzu --helpNode 20+. The package is self-contained; it needs no local chain or model — all of that is server-side.
Sign in
yuzu login # opens the browser, device code
yuzu whoami
yuzu logout| Where | Token | Use |
|---|---|---|
| interactive | ~/.yuzu/config | Written by yuzu login. The normal path on your machine. |
| CI / scripts | YUZU_TOKEN | Set the env var and skip login entirely. A scoped key from API · Authentication. |
The shape of it
Every command is a verb on the presence. Interactive where you want a conversation, one-shot where you want a pipe:
yuzu chat # interactive, stays in thread
yuzu say "what changed on Base overnight?"
git log --oneline -20 | yuzu say "flag anything risky"yuzu say reads stdin and writes plain stdout, so the presence composes like any other Unix tool. Add --json for machine output.