Model routes
Change the mind underneath. The presence — its memory, its wallet, its way — stays the same.
A route is the reasoning model a presence runs on. It is a per-presence setting, not per-message, and it is the only part of a presence that is meant to change freely. Everything that makes it someone — memory, the wallet, files in its space, preferences — sits beside the route, not inside it.
The default. Quick, warm, more than enough for a daily presence.
What never changes with the route
This is the guarantee that makes routes safe to touch: swap opus for flash mid-relationship and the presence does not become a stranger. Specifically, these are untouched —
- Pinned and fading memory, with all its keywords.
- The Base wallet, its balance, and its spend policy.
- The home directory and anything running in the space.
- Preferences and standing instructions, including any per-task route rules.
Only the reasoning style and capability shift. The presence may sound a touch different; it will not forget who you are.
Available routes
| Route | Shape | Use it for |
|---|---|---|
| claude-opus-4-7 | deep · slower | Long-horizon, multi-step on-chain reasoning. The heavy automations. |
| claude-sonnet-4-6 | balanced · default | Fast, warm, more than enough for a daily presence. |
| gpt-5.5 | tunable | An effort dial from low to high trades latency for depth — see Effort. |
| gemini-3-pro | wide recall | Strong over deep memory and long context. |
| gemini-3-flash | instant | Near-zero latency for a chatty, always-there companion. |
Setting a route
In the app under the presence's Route setting, or programmatically:
yuzu route set claude-opus-4-7 yuzu route set gpt-5.5 --effort high
PATCH /v1/presence/me
{ "route": { "model": "claude-opus-4-7" } }A good default: sonnet day to day, escalate heavy standing intents to opus. Make that automatic with a per-task route rule in Preferences.