Sessions and tasks
How a session isolates context for one job, how a task moves through its lifecycle, and what happens when an agent is waiting for your input.
Run three jobs in one long chat and the agent gets confused — the customer-service thread bleeds into the blog draft. Sessions fix that by giving each job its own isolated context, so your agent stays sharp and on-topic no matter how much is in flight.
Session vs. task
- Session — an independent conversation context with an agent. Its message history is isolated from every other session. One agent can run many sessions at once.
- Task — a unit of work you hand an agent inside a session ("draft the launch post", "reconcile this CSV"). The agent executes it in its cloud computer and reports back.
One task, one session. Keep distinct jobs in distinct sessions and nothing pollutes anything else.
Context isolation
A single channel or agent can hold unlimited concurrent sessions, each with its own memory:
Agent: Support
├── Session: Customer A ← isolated context
├── Session: Customer B ← isolated context
└── Session: Customer C ← isolated contextThe agent replying to Customer A has no memory of Customer B. That isolation is what makes Buda safe at scale: private details never leak across conversations, and each reply uses only the right context.
The task lifecycle
- You start a task in a session, in plain language.
- The agent works in its cloud computer — you watch each step live.
- It may pause and wait for input when it needs a decision, a missing detail, or your approval to continue.
- It completes, and the result is ready to review — or saved to Drive for later.
A waiting-for-input session isn't stuck — it's asking. The agent surfaces a question or a choice and holds its place until you respond, then picks up exactly where it left off.
Resuming and ending
Sessions persist. Go idle and a session goes dormant; message it again and the same session resumes with its context intact. Start a new session and you get a clean slate — none of the old context carries over. Use a fresh session when the topic genuinely changes.
Sessions vs. Drive
A session holds short-term context — the back-and-forth of the current job. Drive holds long-term material. If something from a session should outlive it, save it to Drive; chat history alone isn't durable knowledge.