42 / 168 · 01 Agent Skills for Browser Automation · Under the Hood: How Playwright Became Agent-Native← prev ⊞ all next →☰ Read as one page

6.5What This Means for the Rest of This Module

Everything downstream of this chapter — framework architecture, CI integration, self-healing — assumes this stack:

Coding agent (Claude Code / VS Code / Codex)
    │  reads SKILL.md, runs commands via shell
    ▼
playwright-cli  ──  snapshots/screenshots/traces → disk
    │
    ▼
Playwright engine (auto-wait, actionability, cross-browser)
    │
    ▼
Chromium / Firefox / WebKit

A standards note for the protocol-curious: Playwright still drives Chromium via CDP with custom paths for Firefox/WebKit, while the W3C's cross-vendor answer — WebDriver BiDi — is covered in its own part of this module. Both matter: Playwright for what you'll use daily, BiDi for where the standard is heading and for every conversation that starts with "but what about vendor lock-in?"