◉
Sessions outlive the window
Long-running work lives in zumithd, a local daemon. Close Studio, reopen it, and the agent is still where you left it — streaming, interruptible, steerable.
Zumith Studio runs side by side — each session in its own worktree, with goals, accounts, a daemon that outlives the window, and a browser and simulator the agent can actually see.
Zumith Studio is written in Rust on GPUI, the same GPU-accelerated UI framework behind Zed. No Electron, no Chromium tab per agent. The whole app idles in less memory than one browser tab — and it stays responsive with twenty sessions streaming at once.
Measured on an M4 Pro, unoptimized debug binary. Release builds are faster. Performance is an acceptance criterion, not a promise — the probe ships in the app.
Long-running work lives in zumithd, a local daemon. Close Studio, reopen it, and the agent is still where you left it — streaming, interruptible, steerable.
Every session is born in its own git worktree cut from a freshly resolved origin/main. Agents never step on each other; archived worktrees clean themselves up.
Diff, terminal, PR status and CI live next to the chat. Review comments become findings the agent can act on. The loop ends at a green, mergeable pull request.
Register as many accounts per provider as you own — work, personal, a team seat, an API key. Studio reads who each one is straight from the provider's own config, offline, and shows their quota and spend side by side.
A goal is not a note — it is a native object with a plan, phases, decisions, findings and evidence. Studio prepends the active goal to a session's first prompt, so every agent starts knowing what "done" means, and what was already decided.
Every session can bind a Stage: a browser or an iOS simulator the agent Observes and Acts on — structured tree, stable refs, host-taken pixels. It is not your desktop and it never touches your windows. No Chromium, no Playwright, no Appium: a small native host that outlives Studio.
The agent changes a view, looks at its own Stage, and fixes what it sees before it reports back. Screenshots of your real display go through Studio's capture grant only — the Stage is a surface the session owns.
Your Mac and Linux VPS form a single-owner Compute Fabric in My Compute. Every zumithd connects outbound to optional Zumith Cloud, and a fenced Handoff moves the complete managed Workspace while its Conversation remains stable.
Studio is the place where several agents work on one project at once — and where you can still tell what each of them is doing.
Hand a phase to a worker in its own worktree, gate it, merge it back. A mission runs the whole graph — spawn on ready, merge on green — and wakes you only when something blocks.
Claude, Codex, Cursor and OpenCode sessions talk to each other through Zumith’s own MCP server: ask, reply, hand off, warn before touching a shared file.
Fork any session to another model or provider with a native resume and an enriched handoff. Keep the one that is right.
The daemon measures context weight and compacts after the turn ends, before the window dies. Configurable threshold, never a steer.
A spoken orchestrator that opens chats, delegates to workers, asks how they are doing, and tells you when something is ready. It delegates; it never writes code.
Every failure is classified — auth, quota, network, provider, interrupted — and stored with the turn. No phantom error banners, no eternal spinners.