playwriter

Why we included this project

Many browser automation setups spin up a fresh Chrome, which means none of your saved logins or extensions carry over. Playwriter goes the other way: a small Chrome extension connects the tool to the browser you already use, so the sessions and cookies you already have are there when Playwright code runs against the page. Runs happen in a stateful sandbox with isolated per-session state, and you can drive it from the CLI or wire it into an agent via MCP using the full Playwright API. Teams automating workflows that touch logged-in services skip the usual re-authentication for every run. For developers building agentic browser workflows, it lands as a practical middle ground between scripted Playwright and fully headless agents.