playwriter
Playwriter is a Chrome extension and CLI tool that lets AI agents control your existing browser session with full Playwright API support, preserving your logins, extensions, and cookies. It avoids spawning fresh browser instances and bot-detection flags by integrating directly into your running Chrome.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | remorses/playwriter |
| Owner | remorses |
| Primary language | HTML |
| License | MIT — OSI-approved |
| Stars | 3.7k |
| Forks | 161 |
| Open issues | 20 |
| Latest release | [email protected] (2026-06-25) |
| Last updated | 2026-07-03 |
| Source | https://github.com/remorses/playwriter |
What playwriter is
Playwriter provides a stateful sandbox execution model via MCP (Model Context Protocol) or CLI, exposing the full Playwright API plus raw Chrome DevTools Protocol (CDP) access through a single `execute` tool. Sessions maintain isolated state while sharing browser tabs; the extension communicates with agents via JSON-RPC without requiring special browser startup flags.
Get the playwriter source
Clone the repository and explore it locally.
git clone https://github.com/remorses/playwriter.gitcd playwriter# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires a running Chrome for Testing or Chromium binary; bundle or provide installation instructions for consistent CI/CD environments.
- CLI usage always requires a session ID (`-s` flag); design automation scripts to create/manage sessions programmatically or via state files.
- State persistence is per-session; establish clear cleanup policies to avoid memory bloat over long-running agent workflows.
- Multiline CLI commands require shell escaping (`$'...'` syntax); consider wrapping in scripts or using the MCP server approach for complex workflows.
- Network interception and CDP debugging are powerful but can interfere with page logic; test thoroughly before deploying to production.
When to avoid it — and what to weigh
- Headless-Only Deployments — Playwriter requires a running Chrome/Chromium instance with a display (GUI). Not suitable for pure headless server environments without X11/Wayland forwarding or similar workarounds.
- Complete Process Isolation Required — If you need strict isolation between agent tasks (separate browser processes, no shared state), Playwriter's shared-browser model may introduce unwanted cross-session coupling.
- High-Volume Parallel Tasks — Playwriter sessions share one browser instance. Scaling to hundreds of concurrent operations may hit browser resource limits; consider multiple independent browser instances instead.
- Enterprise Bot-Detection Evasion Expectations — While Playwriter can mask some bot signals by reusing logins and extensions, there is no guarantee against sophisticated detection. Do not rely on it for high-risk evasion scenarios.
License & commercial use
MIT License: permissive, allows commercial use, modification, and distribution with attribution. No restrictions on proprietary or closed-source applications.
MIT is a permissive OSI license that permits commercial use without royalties or restrictions. You may use Playwriter in proprietary products and services; include the license text and attribution in your code. Verify compliance with any GPL dependencies (if present, requires review).
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Playwriter runs with access to your active browser session, including all logged-in credentials, extensions, and cookies. Threats: (1) malicious agent code can steal session data or execute actions as the user; (2) the extension runs in your browser process and could be exploited; (3) network interception and CDP debugging features expose sensitive request/response payloads. Mitigations: restrict agent execution to trusted code, use OS-level browser profiles for sensitive work, audit extension permissions, isolate agent environments. No security audit or CVE history provided.
Alternatives to consider
Playwright MCP
Official Playwright browser automation for MCP. Spawns fresh Chrome instances (no login state, higher memory, detected by bot defenses). Better for disposable, isolated tasks; worse for authenticated workflows.
BrowserMCP
12+ dedicated tools (click, scroll, fill, etc.) instead of raw Playwright API. Simpler for LLMs but less expressive. Higher token usage due to tool schemas; no raw CDP or live debugging.
Claude Browser Extension (built-in)
Claude-specific, uses screenshots for context (larger tokens). No Playwright API or debugging. Suitable for Claude-only workflows; not portable to other MCP clients.
Build on playwriter with DEV.co software developers
Start with the Chrome Web Store extension and CLI (`npm i -g playwriter`). Ideal for authenticated RPA, multi-agent collaboration, and debugging. Reserve for desktop/WSL environments; not headless-first. Review security and session isolation for your use case.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
playwriter FAQ
Do I need to change how I start Chrome to use Playwriter?
Can multiple agents use the same Playwriter session?
Does Playwriter work on Windows WSL or in Docker?
What if the extension loses connection?
Custom software development services
DEV.co helps companies turn open-source tools like playwriter into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your mcp servers stack.
Evaluate Playwriter for Your Workflow
Start with the Chrome Web Store extension and CLI (`npm i -g playwriter`). Ideal for authenticated RPA, multi-agent collaboration, and debugging. Reserve for desktop/WSL environments; not headless-first. Review security and session isolation for your use case.