Product guide · Browser sessions
Start here
OverviewGetting startedGetting started
Install and connectCreate a projectCreate an agentCreate a routineRun and debugUnderstand Toone
Core conceptsFeatures
OverviewExperience
Agent SpotlightWorkspace windowsZen modeProject switcherProject ExplorerWorkflows
Browser sessionsRoutinesAgent orchestrationWorkflow libraryCalendarBackground threadsControl and safety
Project HistorySafe ModeConnect
Live ShareVoice and meetingsMobile companionMCPs and integrationsAI providersWork 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.
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.
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.
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.
Next: Routines.