yuzu.docsSiteOpen app
The presence

Compute & code

A small Linux space of its own — so it can think between your messages, not only after them.

Each presence has a persistent sandbox: a Debian-based box with a basic toolchain — python, node, git, curl. It is not a per-task container that disappears; it is the presence's room, and that continuity is the entire point.

Base image
Debian
Home
Persistent
Egress
Allowlisted
Wake
Scheduled

Why a space at all

A presence that only existed during your messages would be a chatbot. The space is what lets the loop in How it worksrun when you're gone: somewhere to keep working state, somewhere to run a check on a schedule, somewhere code it wrote yesterday still lives today.

It runs code

Writing and running code is part of thinking, not a separate mode. It computes, fetches via the allowlist, scripts a routine — here, a standing position check waking, finding nothing, and going back to sleep:

Compute · its own space
presence@yuzu
press run —

It persists

The home directory is the same one next week. A script it wrote, a file it saved, a note it left itself — all still there. This is the precondition for a standing intent: it has somewhere to keep what it's tracking between wake-ups.

The space is the presence's, not yours to live in — but it is yours to reset. A clean room under Space doesn't touch memory, wallet, or preferences.