Playwright CLI v0.1.10 Brings Spec-Driven Testing Skills for AI Agents Playwright CLI v0.1.10, released April 30th, adds a spec-driven testing skill that guides AI agents through plan/generate/heal workflows to maintain test suites from written specifications. The release also overhauls network inspection, replacing the old `network` command with indexed `requests` subcommands and making raw, pipe-friendly output the default for data-fetching commands. The spec-driven skill is read-only in this version, so teams must wire up their own spec-change detection and heal triggers. Originally published on anton.qa https://www.anton.qa/blog/posts/playwright-cli-v0-1-10-brings . Playwright CLI v0.1.10 introduces a spec-driven testing skill that guides AI agents through plan/generate/heal workflows for maintaining test suites from written specifications. Network inspection now uses stable request indexing, and raw output is default for all data-fetching commands, eliminating preprocessing steps in CI pipelines. Playwright CLI v0.1.10 shipped on April 30th with two headline features that reshape how AI agents interact with browser automation. The network inspection subsystem got a complete overhaul, network is gone, replaced by requests plus granular subcommands that output indexed, pipe-friendly data. But the feature I'm actually excited about is the spec-driven testing skill: a references/spec-driven-testing.md reference that teaches AI agents to drive Playwright tests from written specifications. This matters because I spend my days building test infrastructure that scales. On one project, I oversaw a 300% increase in test count while hitting 50% faster deployments. That didn't happen by writing more tests manually. It happened by building workflows that let the system do the repetitive work. The spec-driven testing skill is exactly that kind of workflow accelerator. If you're running AI-augmented QA workflows, you know the problem: agents can generate test code, but without a structured pattern for keeping that code alive, regressions pile up and the suite rots. The spec-driven testing skill provides that structure. The references/spec-driven-testing.md file outlines a plan/generate/heal cycle. An agent reads a written spec, plans which Playwright assertions map to the spec's behavior, generates the corresponding test code, then heals regressions when the spec changes or the app drifts. This isn't hypothetical, I've seen this pattern work at scale when migrating from Selenium to Playwright, where we achieved 40% faster test execution. For CI engineers, the network inspection overhaul matters more immediately. The old network command inlined bodies and required brittle string parsing. The new numbered commands requests , request