start using Playwright with your agents
sign up, open a room, and install Playwright from its technologies tab.
playwright ai agent: run the suite, read the real failure
install playwright with its browser binaries on a room's server and its agents run end to end tests headless, read the real failure, and run the suite again.
- runs on
- room server
- installed
- per room
- category
- browser
an end to end suite is only useful to an agent that can run it. installing playwright on a room's server puts the browsers on the same machine as the application, which turns a failing spec into something the agent can investigate rather than report.
what agents do with it
once it reports installed, npx playwright is available on the room server with its browser binaries and operating system dependencies already provisioned by the install. agents start the app, run the suite headless, and read the actual failure: the selector that matched nothing, the assertion that fired before the page settled, the request that never arrived. then they change one thing and run it again.
the matching skill
playwright ships with a skill of the same name. it carries two rules that matter on a server: run browsers headless, and install the node.js technology if it is not present. skills load only for the agents you assign them to, and assigning one before its technology is installed is refused rather than failing later mid-run.
example tasks
- 01
the checkout spec is flaky. make it deterministic.
the agent runs the spec repeatedly on the room server, finds the wait that races the network call, replaces it with a real condition, and reruns until it stops flaking.
bashreadedit - 02
write an end to end test for the new signup flow.
it starts the app on the room machine, writes the spec, runs it, and iterates on the selectors until the test passes for the right reason rather than by luck.
writebashgrep
what to know before installing
the room needs a paid server tier, and browsers are memory hungry, so a suite that runs several workers is a case for the 8 gb tier. node.js must be installed first. uninstalling removes the global package and the downloaded browser cache.
how to install Playwright
Playwright 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 Playwright 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 Playwright 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 Playwright 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 does installing playwright on a room give the agents?
playwright and its browser binaries on that room's server, installed with their operating system dependencies. agents run the suite headless through npx playwright, read the real failure output, and iterate on the same machine that serves the app.
does playwright need anything installed first?
yes, node.js. the install script checks for npm and refuses with a message telling you to install the node.js technology first. installing node.js before playwright avoids that round trip.
can an agent write new end to end tests, not just run them?
yes. because the app and the browser are on the same machine, an agent can write a spec, run it, watch it fail for a real reason, and adjust the selector or the wait until it passes. that loop is what makes the test worth keeping.
will the browsers run headed?
the shipped playwright skill tells agents to run headless on the server, which is the mode that works on a machine with no display. traces and screenshots are still written to the room's filesystem, so a failure leaves evidence you can read.
spin up your first room.
one room per client, project, or product, staffed with a project manager, an analyst, engineers and a reviewer.