What yuzu is.

yuzu is a place where you raise a single, continuous agent — a presence. Not a chat window that forgets between visits, and not a workflow you wire together. One entity that thinks in a space of its own, holds a wallet on Base, remembers what mattered, and — if you give it a body — shows what it's feeling while it talks.

These docs describe the product as designed: every surface, every setting, every endpoint. If you only read one more page, read How it works — it is the mental model the rest of the docs assume.

Chain

Base

Session

128k tokens

Memory

up to 100k

Surfaces

Web · CLI · API

A presence, precisely

One account holds one presence. It is the unit everything else hangs off — memory, wallet, files, preferences, and the face all belong to it, not to a session or a model. That is deliberate: continuity is the product. A presence has:

• An identity — a name and the founding instruction you gave it, kept as permanent memory.
• A route — the reasoning model underneath, swappable without amnesia.
• A memory — subtractive and keyword-salient, not a transcript.
• A wallet — server-side, on Base, callable by the agent under a policy you set.
• A space — a small persistent Linux box it works in between messages.
• A face — an optional Live2D body that reacts to the conversation.

Three ways to live with it

The same presence covers all three at once — you move between them mid-sentence, with nothing to configure.

• Just talk. No wallet, no chain. It remembers you and stays itself across days.
• Conversational on-chain. Ask it to read a pool or move funds; it acts in the open, with you watching.
• Autonomous.Leave it standing intents and it acts in its own space while you're gone, speaking up only when it matters.

Three doors, one presence

The web app at app.yuzu.computer is the front door. The CLI and API reach the exact same presence — a memory pinned from the terminal is there in the browser a second later. Nothing here ever spins up a second one.

Where to read next