Skip to main content

Agent browser

A hosted browser your agents can use, and you can take over

Give your workspace a Chromium running on TOSE that a person or an AI agent drives through typed actions: navigate, snapshot, click, fill, press, extract, wait, screenshot and tabs. There is no arbitrary script, no shell and no raw DevTools access. Each session runs in its own isolated pod, reaches only the sites your workspace allows, and is billed for the time it runs.

What you get

  • Isolated sessions, typed actions

    One disposable Chromium pod per session, under gVisor with Chromium’s own sandbox on, non-root and with no exposed debugging port. Snapshots list elements as role, name and position, so every action names an element a person can read, and errors come with a next step.

  • Human takeover and approvals

    A person always outranks an agent: a signed-in person takes over at any time, for example to log in or solve a challenge, then hands back. Click, fill and press run by an agent need a signed-in owner or admin to approve that exact action; an agent can never approve its own action.

  • A site allow-list per workspace

    Browsers reach only origins your workspace confirmed. Agents may propose an origin, but only a signed-in owner or admin confirms or removes one, and every change is audited. Internal and private addresses are refused.

  • Profiles

    Sign in once and open sessions that start signed in. A profile’s login state is encrypted in the platform’s credential store, never returned by an API or tool, and used only through a grant that names the profile and its origins. Import a login through a secure form or from your own Chrome with the companion extension. TOSE does not bypass CAPTCHA or MFA.

  • Recipes and public recipes

    An agent that finished a task saves its steps as a versioned recipe and runs it again without a model; if the page has changed, the run stops instead of guessing. Public recipes are read-only, for public sites that need no login, reviewed before listing, and run in your own session under your own allow-list.

  • Site API map and the fetch action

    Enabled on TOSE cloud; needs per-workspace admin setup. On origins your workspace confirmed, the browser records the read endpoints a site’s own pages call, with a response schema and a redacted sample. After a signed-in owner or admin enables a GET endpoint, an agent calls it with the fetch action from inside the tab, so the page’s cookies never reach TOSE or the agent. On REST and the CLI; agents look it up over MCP with browser_knowledge_lookup.

  • Write Action Maps, browserless replay and self-heal

    Enabled on TOSE cloud; needs per-workspace admin setup. A verified Action Map calls a site’s write endpoint with typed parameters, each call with a single-use approval, and can replay without a browser. When a recipe step or an endpoint drifts, self-heal proposes a patch with daily limits, audit and rollback, once a signed-in owner or admin turns on the workspace switch and the workspace has a decision provider. Action Map self-heal is on REST only for now.

  • MCP tools with a live view in the chat

    Connect ChatGPT, Claude or another MCP client to https://app.tose.sh/mcp. Browser tools return a live view that hosts with MCP Apps show inside the chat; “Take over in TOSE” opens the dashboard session page. Other hosts get a plain link.

MCP tools

Your agent sees these tools once you approve the browser scopes. Sessions, actions and the live view need browser:control; looking up saved recipes for a site needs browser:read.

ToolScope
browser_session_createbrowser:control
browser_snapshotbrowser:control
browser_actbrowser:control
browser_extractbrowser:control
browser_screenshotbrowser:control
browser_live_viewbrowser:control
browser_session_closebrowser:control
browser_knowledge_lookupbrowser:read

A click, fill or press through browser_act returns an approval link until a signed-in owner or admin approves it. All MCP tools →

From the terminal: tose browser

The tose browser command group opens, drives and closes sessions, proposes origins and works with profiles and recipes, including finding public recipes. Every subcommand supports --json. It ships in the TOSE CLI release after 0.2.0; until then, build the CLI from source.

tose browser open web --server <server-id> --wait --url https://example.com
tose browser snapshot web
tose browser click web --role link --name "More information"
tose browser allowlist propose https://docs.example.com
tose browser close web

Billing by runtime

  • A session is billed at the standard compute rate, $0.02 per vCPU-hour and $0.01 per GB of RAM per hour, for the time its pod runs. A session of 1 core and 2 GiB costs about $0.04 an hour.
  • Prepaid only: a session cannot start with an empty wallet, and every browser is suspended when the wallet runs out.
  • An idle session is suspended after about 10 minutes, so idle time is not billed. A suspended session keeps no tabs or cookies; use a profile to start signed in.

See pricing →

Not on TOSE cloud yet

  • Pairing a device with the Chrome companion; the companion imports a login from the dashboard today.

Documentation