start using Agent Browser with your agents
sign up, open a room, and install Agent Browser from its technologies tab.
agent browser: managed headless chrome your agents drive
install agent browser on a room's server and its agents drive a managed chrome from the command line: open pages, interact, and read what the browser rendered.
- runs on
- room server
- installed
- per room
- category
- browser
agent browser is the browser technology for tasks rather than test suites. installed on a room's server, it gives agents a managed headless chrome they drive from the command line, on the same machine as the checkout.
what agents do with it
once it reports installed, agent-browser is on the room server's path. agents open a page, work through a flow, and read what the browser actually rendered rather than what the markup implied. that matters for anything behind a login, anything built by javascript, and anything where the answer is what a real user would see. because it runs in the room, the pages it opens and the output it produces stay inside that room.
the matching skill
agent browser ships with a skill of the same name. it carries the practical parts: run flows from the project directory, and remember that browsers and operating system dependencies were provisioned at install time so there is nothing to set up per run. skills load only for the agents you assign them to, and assigning one before its technology is installed is refused rather than failing later.
example tasks
- 01
check the signup flow on staging still works end to end.
the agent drives the flow in a managed browser on the room server, reports where it stopped if it stopped, and captures what the page showed at that point.
bashread - 02
the docs page we link to changed. tell me what it says now.
it opens the page in a real browser rather than fetching the raw html, reads the rendered content, and reports the parts that no longer match our copy.
bashgrepedit
what to know before installing
the room needs a paid server tier, and node.js must be installed first. browsers are memory hungry, so a room doing much of this work wants the 8 gb tier. uninstalling removes the global package and the browser cache it downloaded.
how to install Agent Browser
Agent Browser is installed per room from the technologies tab, not once per team and not on your laptop.
- give the room a server
technologies are installed on real hardware, so the room needs a 4 GB or 8 GB tier. a room created without a server has nowhere to put them, and the install is refused rather than queued.
- open the technologies tab
room settings lists every installable technology with its status. pick Agent Browser and the install is queued for that room's server alone.
- watch the install run
the room streams the status through pending, installing, and installed, and a failed script surfaces its error instead of leaving the room in an unknown state.
- agents use it through bash
once it reports installed, every agent in the room reaches Agent Browser with the bash tool, on the same filesystem as the checkout they are working in. uninstalling runs the teardown script and takes it away again.
where Agent Browser actually lives
each room owns a server for its whole life, and the technologies tab is how you decide what is on it. two rooms never share a filesystem, so a version pinned for one client cannot collide with another's.
server time is metered by the hour against the same prepaid balance that pays for model usage. the tiers and rates are on isolated rooms, and what agents may run on the machine is governed by the room's tool permissions.
faq
what is agent browser?
a command line tool that drives a managed headless chrome. installing it on a room's server puts agent-browser on the path and provisions the browser and its operating system dependencies, so agents open and interact with pages without wiring up a test runner first.
how is it different from installing chrome or playwright?
chrome is the browser alone. playwright is a test framework with its own browsers and runner. agent browser is a cli built for driving a browser as a task rather than as a test, which suits checking a live page or working through a flow once.
does it need anything installed first?
yes, node.js. the install script checks for npm and stops with a message telling you to install the node.js technology first. it then installs the browser and its dependencies with agent-browser install --with-deps.
is there a matching skill?
yes. agent browser ships with a skill of the same name covering running flows from the project directory and the fact that browsers and system dependencies are provisioned at install time. skills load only for the agents you assign them to.
spin up your first room.
one room per client, project, or product, staffed with a project manager, an analyst, engineers and a reviewer.