Work
Computer mode
Multi-step execution with your connected tools, sandboxed code, and durable outputs.
Computer mode is how Aghata does work with tools, files, and code. A request becomes an execution session: a plan, a sequence of steps, and a deliverable that outlives the conversation.
What it can use
Section titled “What it can use”- Connected apps — the integrations you’ve enabled under Connections. Aghata only sees tools you’ve connected; there’s no ambient access.
- MCP servers — your own remote Model Context Protocol servers, added in Connections, appear as tools alongside connected apps.
- Sandboxed code — Python and shell in an isolated sandbox. See Sandboxed code and files.
- Web research — search and reading with sources kept for citation.
What it produces
Section titled “What it produces”Outputs, not just answers: documents, spreadsheets and datasets, generated files, updates to your native Tables, and — with your approval — sent emails. Everything lands in Library with its sources attached.
When it asks for you
Section titled “When it asks for you”Computer mode pauses rather than guessing:
- Approval before sends, purchases, and anything irreversible.
- Input when your intent is ambiguous or a fact is missing.
Both show up in the session and in your notifications; the task waits as long as you need. Details in Approvals, input & authentication.
When to use something else
Section titled “When to use something else”- You want an answer in conversation → Chat.
- The work lives behind a website login → Browser mode (details).
Failure and recovery
Section titled “Failure and recovery”- A tool call fails → the step shows the error in the session; Aghata retries or re-plans, and tells you if it can’t proceed.
- A provider is down or unconfigured → the session says which one and the task pauses instead of failing silently.
- Wrong direction mid-run → reply in the session; guidance lands between steps and redirects the plan.