start here

start using Playwright with your agents

sign up, open a project, and add Playwright to its setup script in settings → server.

Start 7-day trial with Playwright
integrationstechnologyupdated
schematic diagram of the work aldena agents do through Playwright
Playwright

playwright ai agent: run the suite, read the real failure

add playwright with its browser binaries to a project's setup script and its agents run end to end tests headless, read the real failure, and run the suite again.

runs on
conversation sandbox
installed by
setup script
category
browser

an end to end suite is only useful to an agent that can run it. installing playwright in each conversation's sandbox 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 the setup script has run, npx playwright is available in the conversation's sandbox with its browser binaries and operating system dependencies already installed by the setup script. 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 add node.js to the setup script if it is not there. skills load only for the agents you assign them to.

example tasks

  • 01

    the checkout spec is flaky. make it deterministic.

    the agent runs the spec repeatedly in the conversation's sandbox, 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 in the conversation's sandbox, 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 project needs a sandbox, and browsers are memory hungry, so a suite that runs several workers is a case for the standard size or larger. node.js must come earlier in the setup script.

how to install Playwright

Playwright goes in the project's setup script, not once per team and not on your laptop.

  1. give the project a sandbox

    Playwright runs in each conversation's sandbox, on your team's own sandbox provider account. an owner or admin connects a provider once on the team's providers page, then picks it and a default size for the project, at creation or later in settings → server. a project with no sandbox has nowhere to run it.

  2. add it to the setup script

    settings → server holds the project's setup script, a bash script that runs once on each new sandbox, in /project, with sudo. add Playwright's install commands there and save.

  3. the next sandbox runs it

    the script runs when a conversation's sandbox is created or reused, on the conversation's first turn. settings shows the last run with its exit code and output, and a failed run leaves the sandbox usable rather than blocking the project.

  4. agents use it through bash

    from then on every agent in the project reaches Playwright with the bash tool, on the same filesystem as the checkout they are working in. the conversation's sandbox keeps it between turns, sleeping when idle and waking with the next one.

where Playwright actually lives

each conversation in a project gets its own sandbox on your team's sandbox provider account, and the project's setup script in settings → server decides what is on it. two projects never share a filesystem, so a version pinned for one client cannot collide with another's.

the sandbox provider bills its machine time to your team's account while it runs, and aldena adds nothing. the sizes are on isolated projects, and what agents may run in the sandbox is governed by the project's tool permissions.

faq

what does installing playwright on a project give the agents?

playwright and its browser binaries in each conversation's sandbox, 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. playwright installs through npm, so node.js has to come earlier in the project's setup script. the script runs top to bottom, so ordering its lines that way is all it takes.

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 in the sandbox, which is the mode that works on a machine with no display. traces and screenshots are still written to the sandbox's filesystem, so a failure leaves evidence you can read.

ready when you are

spin up your first project.

one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.