Playwright CLI

Use it when

• Your coding agent burns most of its context window on MCP browser tool schemas and verbose accessibility trees and you want concise purpose-built commands instead
• You need an agent to drive a real browser from the terminal while preserving cookies and login state across separate command invocations and sessions

What it solves

Not the fit when

• Stealth scraping, CAPTCHA solving, or evading bot detection.
• Long-running exploratory agents needing a persistent rich browser tool surface; the project recommends Playwright MCP for that use case.
• Treating allowed-origins configuration as a complete redirect or navigation security boundary.
• Careless storage-state handling; saved cookies and tokens are credentials and should not be committed or shared.
• Giving an unrestricted autonomous agent authority to make purchases, publish content, delete data, or perform other irreversible actions.
• Environments without Node.js 18+.
• bypassing bot detection or CAPTCHAs
• healing broken CSS selectors automatically
• scraping at scale across proxy pools
• writing Playwright test suites for you

Install

npm install -g @playwright/cli@latest && playwright-cli install --skills

Invoke

playwright-cli open https://example.com then snapshot to get element refs, followed by click/type/fill/press; use -s=name for named sessions, state-save/state-load for cookies and storage, and playwright-cli show for a live dashboard of running sessions.

Alternatives

No reviewed alternatives recorded yet.