32 / 168 · 01 Agent Skills for Browser Automation · Playwright Test Agents: Planner, Generator, Healer← prev⊞ allnext →☰ Read as one page
5.1What Shipped
With v1.56 (and maturing through 1.61, current as of July 2026), Playwright gained three first-party test agents — not a bolted-on AI product, but agent definitions that plug into whatever coding agent you already run:
| Agent | Input | Output | Job |
|---|---|---|---|
| 🎭 Planner | A seed test, optional PRD, your request | specs/*.md — human-readable Markdown test plans |
Explores the app, decides what to test |
| 🎭 Generator | A Markdown plan | tests/**/*.spec.ts — executable Playwright tests |
Converts scenarios to code, verifying selectors and assertions live against the running app |
| 🎭 Healer | A failing test | A patched test (or a verdict that the app itself is broken) | Replays the failure, inspects the UI, updates locators/waits/data, reruns until green |
Scaffolding is one command, rerun whenever Playwright updates:
npx playwright init-agents --loop=claude # Claude Code
npx playwright init-agents --loop=vscode # VS Code (v1.105+, Oct 2025 or later)
npx playwright init-agents --loop=codex # Codex CLI
npx playwright init-agents --loop=opencode # opencode
Note the --loop flag: the agent definitions are portable across agent runtimes. This is the skills thesis from Foundations applied by the biggest player in the ecosystem — write instructions once, run them under any capable coding agent.