toone

Feature · Browser work

Browser sessions

Let agents work through websites with a browser session you are already signed into, follow the pages they use, and step in when a task needs you.

Product guide · Browser sessions

Work beyond the chat window

Many useful processes depend on websites rather than APIs. Browser sessions give agents a way to work through those interfaces while keeping the browser context connected to the project. The shared routine Launch Content Production, for example, checks its sources in Toone's browser and only reads what it finds.

In the App Store edition, agents browse only after you allow it, in tabs with their own website data.

Use an authenticated session

Bring a session from your default browser into Toone when a task depends on an account you have already signed into. This avoids treating every browser task as a fresh, disconnected environment. Bringing in a session from your default browser is not available in the Mac App Store edition.

The first time you open the browser, choose how Toone may reuse the logins from your own browser.

Keep the context visible

Browser work should remain understandable to the person responsible for the project. Follow which session and page are involved, then intervene when a step requires judgment, approval, or corrected input.

A tab an agent works in carries its name, and a dot pulses while it acts there in the background.

Use deliberate boundaries

Connect only the browser context needed for the task. An authenticated session can expose sensitive capabilities, so its scope should match the agent’s role and the outcome you asked it to produce. Launch Surface Preparation works this way: it researches launch sites and prepares only the accounts you authorize for each one.

An agent can ask for one site's login. Nothing is copied from Safari unless you approve it.

Next: Routines.