playwright cli Playwright CLI with SKILLS Playwright CLI vs Playwright MCP This package provides CLI interface into Playwright. If you are using coding agents , that is the best fit. CLI : Modern coding agents increasingly favor CLI–based workflows exposed as SKILLs over MCP because CLI invocations are more token efficient: they avoid loading large tool schemas and verbose accessibility trees into the model context, allowing agents to act through concise, purpose built commands. This makes CLI + SKILLs better suited for high throughput coding agents that must balance browser automation with large codebases, tests, and reasoning within limited context windows. MCP : MCP remains relevant for specialized agentic loops that benefit from persistent state, rich introspection, and iterative reasoning over page structure, such as exploratory automation, self healing tests, or long running autonomous workflows where maintaining continuous browser context outweighs token cost concerns. Learn more about Playwright MCP. Key Features Token efficient . Does not force page data into LLM. Requirements Node.js 18 or newer Claude Code, GitHub Copilot, or any other coding agent. Getting Started Installation [安装/使用命令见下方] Installing skills Claude Code, GitHub Copilot and others will use the locally installed skills. [安装/使用命令见下方] Skills less operation Point your agent at the CLI and let it cook. It'll read the skill off playwright cli help on its own: [安装/使用命令见下方] Demo [安装/使用命令见下方] Your agent will be running commands, but it does not mean you can't play with it manually: [安装/使用命令见下方] Headed operation Playwright CLI is headless by default. If you'd like to see the browser, pass headed to open : [安装/使用命令见下方] Sessions Playwright CLI keeps the browser profile in memory by default. Your cookies and storage state are preserved between CLI calls within the session, but lost when the browser closes. Use persistent to save the profile to disk for persistence across browser restarts. You can use d