Last updated: 2026-08-29
Tunbru Desktop is a workspace where AI agents do real work — building, browsing, booking, filing — on a cloud backend, inside walls that keep each person's work their own. This page takes you from installer to first result, and explains what each state means when something looks wrong.
Open Tunbru Desktop.dmg, drag the app into Applications, launch it. The app is a thin, sandboxed shell — agents, files, and providers all live on the Tunbru backend it connects to. Nothing heavy runs on your Mac.
On first launch the app probes its backend. If you see “Cannot reach Tunbru”, the endpoint isn't reachable yet — the card retries every three seconds on its own and lifts the moment the connection works. You never need to restart the app for it.
Ask the Genie for something concrete — “make a mini-app currency converter” — and watch it land in Artifacts. Every generated output opens two ways: Open runs or serves it where possible, and Browse files opens it as plain files in the explorer — that one always works, even for a heavy backend build that can't be served, so you can always inspect what was produced.
Tunbru serves every category — reasoning, multimodal, voice — out of the box, ending on a free tier. You never need to add a key. Add one only when you want runs billed to your own provider account: Settings → AI, press + on a queue, pick the provider, paste the key when asked. Keys are stored server-side; agents never see them.
Settings → Connectors → MCP servers → + Install MCP. An install goes through the orchestrator and is provisioned to every agent you run — stored in your own workspace, isolated inside the agent sandbox, never system-wide.
Put standing instructions in .tunbru/instructions.md at the root of your workspace. At every agent run it is projected into CLAUDE.md, GEMINI.md, and AGENTS.md, so whichever model serves the run reads the same configuration. A file you wrote by hand is never overwritten.
| Symptom | Meaning | Do |
|---|---|---|
| “Cannot reach Tunbru” | Backend endpoint unreachable | Wait — it retries itself. Persisting: check your network/VPN. |
| Health shows a provider unavailable but status “ok” | Your selected provider has no key; the free fallback is serving | Nothing — or add a key in Settings → AI. |
| Health shows “degraded” | No provider can serve, or the database is down | This one is real — contact support. |
| An artifact won't open | Heavy or unservable build | Use Browse files — inspection always works. |
| MCP shows “Needs keys” | Server registered, credentials missing | Open the server in Connectors and provide the named keys. |
Every claim below is enforced in code, not policy.
Tunbru opens by waitlist. Join the waitlist and we'll reach out — businesses first.