How Buda works
The end-to-end loop — you direct, the Organizer coordinates, and Claws execute in cloud computers. Read this first.
If you treat Buda as a chat box, the pieces feel confusing — Space, Agent, Session, Drive, Skill, Channel. The shortcut is simple: Buda is not a chat box, it's a company you run. You set direction; your AI workforce does the work.
The loop in one sentence
Humanity leads · Buda manages · Claws execute.
- You are the CEO — you state the outcome you want and review what comes back.
- Buda is the manager — the Organizer decides what runs, when, and which agent handles it.
- Claws are the workforce — agents that actually do the work, in parallel, in the cloud.
Each agent runs inside its own isolated, long-running cloud computer — files, browser, terminal, and Git — backed by a persistent Drive and memory. Nothing runs on your laptop.
The end-to-end loop
- You give a task in plain language inside a Session.
- The Organizer plans it and routes it to the right agent.
- A Claw executes in its cloud computer — reading files, browsing, running code — while you watch every step live.
- Results land in Drive so the next task can build on them.
- You review and iterate, or turn the workflow into a reusable Skill or Automation.
The building blocks
| Concept | Think of it as | What it's for |
|---|---|---|
| Space | The company / workspace | Members, roles, shared Drive, shared credits, billing |
| Agent / Claw | An AI employee | The unit that does the work; owns identity, instructions, and a cloud computer |
| Cloud computer | The agent's machine | Isolated, long-running sandbox with files, browser, terminal, Git |
| Session & Task | A meeting / work item | Isolated context for one job or conversation |
| Drive | The file cabinet | Durable, versioned storage and knowledge base |
| Skill & Automation | An SOP | Reusable workflows, run on demand or on a schedule |
| Channel | A reception desk | How outside users reach an agent (WhatsApp, Slack, Telegram…) |
The point of these layers is management boundaries: what's shared at the company level, what belongs to one agent, what's only valid in the current session, and what's worth saving for reuse.
One agent, many sessions
The most common beginner mistake is creating too many agents. Start with one agent and several sessions — same employee, different jobs — and only split into a new agent when identity, permissions, tools, or knowledge truly need to be isolated.
Decide structure with one question per layer: just this task? → stay in the Session. New platform style? → new Session. Need it later? → save to Drive. Keeps repeating? → make a Skill. Different permissions or knowledge? → new Agent.