Skip to content
Ask Claude about any Chrome extension, answered with Ext Watch data. See how →
Developer Tools extension

Playwriter

Automate your Browser using Cursor, Claude, VS Code. More capable and context efficient than Playwright MCP.

by Notaku · 2 listings

Add to RadarChrome Web Store Free plan tracks 1 extension · no card
extwatch.com/extensions/playwriter-jfeammnjpkecdekppnclgkkffahnhfhe
PlaywriterNotaku · Developer ToolsHigh access
Users
10K+
#648 of 31,192 in category
Rating
4.76
17 ratings · median 4.63
Version
0.0.174
126 KiB · Manifest V3
Access
High65/100
10 permissions + every website
From the store listing

Screenshots

2 images from the publisher · use the arrows or pick one · swipe or pick one

Playwriter screenshot 1Playwriter screenshot 2
1 / 2

Description

As written by the publisher on the store

Control your real Chrome browser with AI agents, CLI commands, or any MCP client. Full Playwright API access through your existing browser with all your logins, extensions, and cookies already there.

Other browser automation tools spawn a fresh Chrome instance. That means no login state, no extensions, instant bot detection, and double the memory usage. Playwriter connects to your running browser instead. Click the extension icon on any tab to start automating it.

HOW IT WORKS

Click the Playwriter extension icon on any tab you want to control
The icon turns green when connected

Your AI agent, CLI, or MCP client can now control that tab through the full Playwright API

The extension creates a local WebSocket relay on localhost:19988. Your automation tools connect to this relay and send Playwright commands. The extension forwards them to Chrome via the DevTools Protocol. Everything runs locally on your machine.

WHAT YOU CAN DO

Browser automation with full Playwright API. Navigate pages, click buttons, fill forms, take screenshots, intercept network requests, set breakpoints, live-edit page code, record videos, and more. All through a single execute tool that accepts any Playwright code.

Accessibility snapshots give your agent a text representation of every interactive element on the page. 5-20KB instead of 100KB+ for a screenshot. Faster, cheaper, and the agent can parse them without vision capabilities.

Visual labels overlay Vimium-style colored labels on interactive elements for agents that need spatial context. Yellow for links, orange for buttons, coral for inputs, pink for checkboxes.

Session isolation lets multiple agents work in the same browser without interference. Each session has its own sandbox with persistent state.
Network interception captures API calls behind JavaScript-rendered pages. Agents can reverse-engineer APIs, inspect schemas, and replay requests with different parameters.

JavaScript debugger sets breakpoints, steps through code, inspects variables at runtime. Full Chrome DevTools Protocol access, not a limited subset.

Live code editor views and edits page scripts and CSS in memory without reloading. Toggle debug flags, patch code, search across all loaded scripts.

Screen recording captures the browser tab as MP4 video at 30-60fps using chrome.tabCapture. Recordings survive page navigation. Built-in ghost cursor overlay for creating demo videos.

Cloud browsers run stealth Chromium instances in the cloud with automatic CAPTCHA solving

Headless mode launches a headless Chrome automatically for CI, servers, and fully autonomous automation without a visible browser.

Direct CDP connection bypasses the extension entirely to connect to Chrome instances with remote debugging enabled, Docker containers, or cloud browser providers via WebSocket.

Remote access controls Chrome on another machine over the internet using secure tunnels. No VPN, no firewall rules, no port forwarding needed.

USE CASES

Web development: your coding agent verifies its own work in a real browser, checks rendered pages, takes screenshots, inspects CSS, sets breakpoints, and fixes issues in one loop.

QA testing: run tests against your real Chrome profile with real login state. No test accounts or mock authentication needed.

Task automation: automate repetitive browser tasks that need your logged-in session. Bulk fill forms, export data from dashboards, download files from authenticated sites.
Scraping JavaScript-heavy sites: Instagram, Twitter, Facebook, and other SPAs return empty HTML to curl and fetch. Playwriter renders them in a real browser with your session cookies.

API reverse engineering: capture network requests behind client-side rendering. Discover undocumented APIs, inspect their schemas, replay calls with different parameters.

Remote support: control a user's browser remotely to fix issues. The user starts a tunnel, shares the URL, and you can see exactly what they see.

Screen recording and demos: record browser automation as polished MP4 videos with cursor overlay. Speed up idle sections automatically for demo videos.

WHY PLAYWRITER INSTEAD OF OTHER TOOLS

vs Playwright MCP: Playwright MCP spawns a new Chrome with no logins, no extensions, and gets flagged by bot detectors. Playwriter uses your existing Chrome.

vs BrowserMCP and other browser MCPs: other tools expose 12+ dedicated tools with high context window overhead. Playwriter uses one execute tool with the full Playwright API. Less context usage, more capabilities.

vs Chrome CDP mode: Chrome's remote-debugging-port flag requires restarting Chrome and shows persistent "controlled by automated software" banners that interrupt your workflow. Playwriter runs silently with no confirmation dialogs.

vs Claude Browser Extension: Playwriter works with any MCP client, not just Claude. Uses text snapshots (5-20KB) instead of screenshots (100KB+). Full CDP access including debugger, network interception, and live code editing.

COLLABORATION

Because the agent works in your browser, you can collaborate in real time. See everything the agent does. Solve captchas when it gets stuck. Click through consent walls. Disable the extension temporarily to bypass bot detection, then re-enable to continue automation.

SECURITY AND PRIVACY

Local only: the WebSocket server binds to localhost. Nothing leaves your machine. No remote servers, no accounts, no telemetry.
Origin validation: only the Playwriter extension origin is accepted. Browsers cannot spoof the Origin header, so malicious websites cannot connect.

Explicit consent: only tabs where you clicked the extension icon are controlled. No background access to other tabs.

Visible automation: Chrome shows an automation banner on controlled tabs so you always know when a tab is being automated.

No data collection: no analytics, no tracking, no telemetry. All browser control happens locally through Chrome DevTools Protocol.

SUPPORTED MCP CLIENTS

Works with Claude Desktop, Cursor, Windsurf, VS Code, OpenCode, and any other MCP-compatible AI assistant. Install the CLI with npm install -g playwriter, add the skill with npx skills add remorses/playwriter, and your agent is ready.

PERMISSIONS

debugger: attach Chrome DevTools Protocol to tabs you select
activeTab: access only the tab you click the extension icon on

scripting: inject the in-page toolbar on connected tabs

webNavigation: detect popup windows opened by connected tabs

host_permissions: allow debugger attachment on any domain you choose to automate

Open source: https://github.com/remorses/playwriter
Documentation: https://playwriter.dev/

Ratings and reviews

Split of the 7 written reviews we hold
Reviews on the store
4.7617 ratings on the store
7 written reviews we hold
5 ★71.4%5
4 ★14.3%1
3 ★0.0%0
2 ★14.3%1
1 ★0.0%0
Erik Novikov

Incredible how a 30K users extension has so little ratings. Awesome app, thanks!

frank liu

It works. Claude can control my browser using this extension.

Peter Cox

I can't believe I haven't left a review yet. I use this tool every single day and it never lets me down. Thank you. A shortcut to turn it on would be handy otherwise perfect

Sean Moore

Best browser tool out there. Dev is 🐐'd

Austin Mudd

I am very happy using Playwriter, I use it a lot! I've tried a small handful of other SKILL.md based browser tools and have felt that playwriter remains quicker and less token hungry, especially compared to something like claude code's extension. Suggestion: Often times playwriter spends a small amount of turns trying to get itself situated... maybe this is because I'm using pi and have to use mcporter, but the age…

jorge m

App is working amazingly. I just need a way to do some kind of reset or reboot because it does lose connectivity pretty often. Maybe to restart the service or something like that from the command line or the MCP Chrome extension.

Radar

Track Playwriter on Radar

This page shows the listing as it is today. Add it to Radar and get one email when it changes.

  • Users and rating
  • Store text and screenshots
  • Permissions it asks for
Free plan tracks 1 extension · no card
Ext Watch Radar watchlist cards showing tracked extensions with users, rating, version and latest store change
Guide

Playwriter, in plain words

What it is, what to use instead, what it can access and how to fix it.

At a glance

Playwriter at a glance

Playwriter is a Developer Tools extension by Notaku with 10K users. Chrome Web Store users rate it 4.76 out of 5 from 17 ratings, which is still a small sample. By users it sits in the top 5% of Developer Tools extensions.

By users
#648of 31,192 in Developer Tools
Rating
4.76category median 4.63
Access
High65 of 100

Playwriter alternatives

Closest by what they do · users as the store shows them · bars on a log scale
Playwriter10K4.76 ★
Browser MCP - Let AI use your real browser100K4.7 ★Playwright Extension100K4.8 ★OpenCode Browse60K4.7 ★Page Agent Ext20K4.3 ★Web MCP: Browser MCP Service, AI Automated Operations2K3.8 ★
Permissions

Is Playwriter safe?

Playwriter asks for 10 permissions and access to every website. 5 of them give wide access.

Permissions show what it could do, not what it does. See the full permission list.

65/ 100High access
Playwriter10 permissions · 5 wide
  • <all_urls>Read and change data on every website
  • debuggerTake full control of pages through the debugger
  • identityAsk for your Google account sign-in
  • identity.emailSee your Google account email
  • webNavigationFollow every page you open

Every permission Playwriter asks for

10 permissions + every website · 5 sensitive · High access overall

Sites

  • Read and change data on every website<all_urls>

Browser permissions · 10

  • Take full control of pages through the debuggerdebugger
  • Ask for your Google account sign-inidentity
  • See your Google account emailidentity.email
  • Follow every page you openwebNavigation
  • Run its code on pages it can accessscripting
  • Organize tab groupstabGroups
  • Add items to the right-click menucontextMenus
  • Run hidden helper pagesoffscreen
  • Copy text to your clipboardclipboardWrite
  • Save its own settingsstorage

Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.

Troubleshooting

Playwriter not working?

What recent reviews say

Store reviews from the last 90 days
2recent reviews, none with 1 or 2 stars
1–2 stars 3–5 stars

Common fixes

Try them in this order
  1. 1Update Chrome and the extension
  2. 2Turn it off and on in chrome://extensions
  3. 3Reload the page
  4. 4Turn other extensions off in case two clash

Still stuck? Contact the maker or try an alternative.

298,549 Chrome extensions in one place

Know when a listing changes

Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.

No credit card neededFree ExplorerAsk Claude about any extension