Skip to content
Open Aghata

Start

Chat vs Computer vs Browser

Three ways to work, one simple boundary — answers, tool-and-code execution, or operating real websites.

Aghata’s composer offers three ways to work. Picking the right one is the single highest-leverage habit in the product.

Chat is conversation with model routing: ask, discuss, draft, think. Auto picks the best model for each message (you’ll see which one it chose and why on the response). Use Chat when the result you want is words in this conversation.

Computer mode turns your request into an execution session: it plans, calls your connected apps and MCP servers, runs code in a sandbox, and produces durable outputs — documents, datasets, files, table changes, sent emails.

Use it when the result should exist after the conversation: “build me a comparison table”, “reconcile these exports”, “draft and send the weekly update after I approve it”.

Browser mode — when the work lives behind a login

Section titled “Browser mode — when the work lives behind a login”

Browser mode operates a real browser on real websites: dashboards without APIs, supplier portals, admin consoles. It uses credentials from your vault — the agent can use them, but never read or display them — and shows a live view where you can watch every click or take over.

If a site demands a human (a captcha, a 2FA prompt), the session enters paused for authentication and asks you to log in through the live view. Your keystrokes there are never seen by the agent.

Use it when the task starts with “log in to…” or when the data has no export button.

Words → Chat. Tools, files, and code → Computer. Websites behind a login → Browser.

Aghata will also tell you when you’ve picked the wrong one — a Computer-mode request that needs a logged-in website will propose switching rather than guessing.