remorses/playwriter

Chrome extension & CLI to let agents control your browser. Runs Playwright snippets in a stateful sandbox. Available as CLI or MCP

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on June 11th, 2026
Created on November 13th, 2025
Open Issues & Pull Requests: 30 (+0)
GitHub issues: Enabled
Number of forks: 178
Total Stargazers: 3,881 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.8 hours
Mean response time: 4.1 days
90th percentile: 9.0 days
Tracked items: 74

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 14% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 88 days
Stale 30+ days: 14
Stale 90+ days: 12

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 2
Events in 7 days: 4

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

Playwriter is a browser automation tool that lets agents control your Chrome browser via CLI or MCP server.

The problem Playwriter solves is that existing browser automation solutions spawn fresh Chrome instances without login state, extensions, or cookies, making them detectable by bot defenses and memory-inefficient. Playwriter instead connects to your running browser through a Chrome extension, giving agents access to the full Playwright API while preserving your existing logins, extensions, and browser state. The extension turns green when connected, and you execute Playwright snippets through the CLI or MCP interface in an isolated, stateful sandbox where variables like page, context, and state persist between calls.

Playwriter suits developers and AI agents that need to automate real-world browser tasks without the overhead of spawning new browser instances. It works well for scenarios where you want to reuse your existing authentication and extensions, bypass bot detection, or collaborate with agents in the same browser window. Compared to Playwright MCP, which spawns a fresh Chrome, Playwriter uses your existing browser and avoids bot detection flags. Against the standard Playwright CLI, it offers the full Playwright API with raw CDP access and native tab capture for video recording at 30-60fps, far more efficient than Playwright's base64 frame-by-frame approach. Versus BrowserMCP's 12+ dedicated tools, Playwriter provides a single execute tool that leverages the Playwright API developers already know, reducing context usage and eliminating the need to learn tool-specific commands.

The project maintains a substantial base of adopters, with almost all open issues raised by outside users rather than the core team. Maintainers typically respond to new issues and pull requests within hours.