Microsoft Playwright Cli
microsoft-playwright-cli is a Claude Code plugin for the Ship phase that wires Microsoft’s Playwright CLI into your agent so you can record, generate, and inspect browser automation from the terminal.
by microsoft · github.com/microsoft/playwright-cli
Install when you need a fast terminal workflow to record, generate, and debug Playwright browser automation without wiring the full test harness first.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install microsoft-playwright-cli@microsoft/playwright-cliBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:microsoft/playwright-cli") and the paste-ready config with skillselion.get_install_config("plugin:microsoft/playwright-cli").
What it does
microsoft-playwright-cli is a Claude Code plugin that exposes Microsoft’s Playwright CLI for everyday browser automation tasks. Solo builders shipping web apps use it to record interactions, emit Playwright code, inspect locators, and grab screenshots when Cursor or Codex need grounded context about how the UI actually behaves. It fits indie workflows where you cannot afford a dedicated QA team but still need reliable click paths before deploy. Compared with only writing tests by hand in the editor, the CLI shortens the loop from “something broke in Chrome” to a reproducible script you can check in. It complements agent skills that generate tests but does not replace a full CI matrix or visual regression suite. Pair it with your staging URL and Node toolchain; stars on the upstream repo reflect broad adoption among frontend teams.
Highlights
- Record browser sessions and generate Playwright test code from the command line.
- Inspect selectors, pages, forms, and elements without running a full GUI recorder.
- Navigate pages, click controls, and capture screenshots for bug reports or docs.
- Observe network traffic and page behavior while iterating on flows.
- Single-plugin bundle from the official microsoft/playwright-cli repository (plugin count: 1).
Why builders use it
You know a flow is broken in the browser but translating what you clicked into stable Playwright selectors and scripts eats hours you do not have.
After you add the plugin, you get repeatable CLI commands for navigation, recording, screenshots, and selector inspection that your agent can invoke while you ship E2E coverage.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 7k stars, 0 votes.
FAQ
Who is microsoft-playwright-cli for?
It is for solo builders and small teams using Claude Code who automate browsers with Playwright and want record, inspect, and screenshot commands on tap.
When should I use microsoft-playwright-cli?
Use it when you are validating prototypes, authoring E2E tests, or debugging selectors and network behavior before or right after a release.
How do I add microsoft-playwright-cli to my agent?
Register the microsoft/playwright-cli Claude Code plugin from Skillselion, ensure Node and Playwright browsers are installed locally, then invoke CLI actions from your agent session.
Comments
Share how you use microsoft-playwright-cli, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.