Playwriter
Let agents control your own running Chrome through an extension, with the full Playwright API via CLI or MCP.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Automating tasks that depend on your real, logged-in browser state.
You want isolation; the agent acts inside your real browser profile.
About Playwriter
Playwriter connects agents to the Chrome you already run, with your logins, extensions and cookies, through a Chrome extension, instead of spawning a fresh browser. Agents run Playwright snippets in a stateful sandbox from a CLI or over MCP, with isolated sessions, shared tabs and tab groups for concurrent agents; the browser can also be reached from another machine through a tunnel.
Playwriter is listed in this index written primarily in TypeScript, with 4.0k stars on GitHub. Its latest recorded repository push was in October 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
npm i -g playwriter