Browser

A local browser an agent can drive. Real Chrome (or Brave, Comet, Arc) with your real cookies, addressed by element refs instead of selectors.

Why it exists

Most "agent runs the browser" tools spin up a fresh Playwright instance. Two things go wrong: you have to sign in from scratch every run, and the major sites detect the automation and block you within seconds. agents browser uses a real Chromium binary pointed at a persistent profile directory, so the agent inherits your real logged-in state and looks like any other tab.

The model

• Profiles — named, persistent identities. Cookies and login state live here. Two profiles = two browsers that can't see each other.
• Tabs — per-task tabs inside a profile. One agent can drive several tabs of one profile; many agents can drive many profiles concurrently.

Quickstart

agents browser profiles create work --browser chrome
agents browser start --profile work --url https://linear.app
agents browser refs           # numbered list of clickable elements
agents browser click 14
agents browser screenshot
agents browser done

Surface

• start / done — open and close a task tab against a profile.
• navigate / refs / click / type / screenshot — drive the focused tab.
• console / network — read DevTools messages and network log.
• tab open / focus / close — multi-tab per task.
• record / replay — capture a video of the run for debugging.

Related

• Secrets — attach a credential bundle so the agent can sign into sites without ever seeing the password.
• Teams — when several agents need their own browser at the same time.