Barista Cloud¶
Sessions that sleep. Barista Cloud runs long-lived compute sessions — agent workspaces, dev environments, interactive processes — that pause with their memory intact when idle and wake on the next request. You stop paying for compute the moment a session rests, and it resumes as the same live process, not a reconstruction.
This site documents the hosted service at beta.barista.sh. The open-source engine underneath — the node, the pause/resume mechanics, the snapshot model — has its own documentation at barista.sh docs.
Where to go¶
- New here? Getting started — feel a session survive a nap in the console, no installs; then the SDK and CLI.
- Want to see the point? Tutorial 1 · Counter — a number that survives pause→resume. Then the full tutorial series: Claude Code and Codex sessions, MCP, Zed over ACP, templates, the Python SDK.
- Building against it? The CLI reference and the
Python SDK (
barista_sdk, with an E2B-compatible adapter).
The model in one paragraph¶
A session is a named, digest-pinned OCI workload owned by your tenant. You
talk to it by name: exec/attach create it if it doesn't exist (from a
template or the platform default) and wake it if it's
parked. It auto-pauses after an idle timeout you control — memory kept,
compute released — and the next exec, attach, or request to its published
URL wakes it. State lives in the process, so an agent's context, a REPL's
variables, or a build's warm caches survive the nap.