Playwright

Playwright MCP or Playwright CLI: pick either, your agent gets all of this 🎭

🧰 WebMCP: pages hand the agent their own tools
🔎 Find: grep the page instead of reading all of it
🪶 Leaner snapshots, fewer tokens on every step
🔴 Do it by hand once, get Playwright code back
🗣️ Codegen in TypeScript, Python, Java and C#
🔌 Your real Chrome, logins included
🎬 60 fps video with an animated cursor and chapters
📱 Mobile and device emulation
🌗 Light/dark flipped mid-session
🌐 Mock any request, or pull the plug and go offline
📸 Hi-res screenshots
🩹 Crashed tab or dropped connection? It'll recover

npx @playwright/mcp@latest
github.com/microsoft/play…

npm i -g @playwright/cli@latest
github.com/microsoft/play…

Playwright and browser security reminder.

We saw a post suggesting that you delete Playwright because it bundles browsers with CVEs. That is a misconception. Do not delete Playwright🙃. Here is how it works and what you should do.

No Playwright package bundles a browser. Agents on Playwright MCP or CLI run your stable Chrome, which gets Chrome's security updates, with the sandbox on.

🤖 If you use Playwright MCP or the Playwright CLI

They use the stable Chrome / Edge on your machine, so it gets its normal updates. No config edit is needed.

🧪 If you use the test runner

When you run npx playwright install, Playwright downloads Chrome for Testing, pinned to the build we tested that release against. The pin is on purpose. Your tests run on the same browser on every laptop and CI machine, and a browser
update cannot suddenly break your suite. You choose when to move by upgrading Playwright. New releases usually pin a build ahead of stable Chrome, so you see breakage before your users do.

We recommend this for full e2e test suites on your own trusted app. This build can miss Chrome security fixes until the next Playwright release, and by default it runs with the sandbox off. Do not use it on the hostile web.

📚 If you use the library API

chromium.launch() has the same defaults: the pinned build with the sandbox off. If your code visits pages you don't control (scrapers, agent scripts), max out protection:

chromium.launch({ channel: 'chrome', chromiumSandbox: true })

🔒 Always keep Chrome / Edge updated. Some bugs can escape a sandbox.

Happy testing!

🧱 Component testing in Playwright has a new shape: stories & galleries.

✍️ A story wraps your component in one scenario — props, providers, mock data — in a *.story.tsx file next to the component.
🖼️ A gallery page, served by your own dev server, renders stories on demand — React, Vue, Svelte, Solid, anything.

Using @playwright/experimental-ct-*? Give the new model a try and tell us how it goes:
👉 github.com/microsoft/play…

Docs: playwright.dev/docs/test-comp…

🎭 Catching up on Playwright releases — v1.60, v1.61 and v1.62 are out!

Highlights:

🔑 WebAuthn passkeys — a virtual authenticator lets you test passkey sign-in in every browser, no hardware key needed
🛑 AbortSignal support — cancel actions, navigations and assertions with a standard AbortController
🪝 locator.drop() — simulate external drag-and-drop of files onto upload zones, cross-browser
🗃️ page.localStorage / page.sessionStorage — read and write web storage directly
🖼️ WebP screenshots for visual comparisons — just name your snapshot .webp
🔁 retryStrategy: 'isolated' — run retries at the end, one by one, free of interference
🤖 Playwright MCP server and CLI now ship in the box: npx playwright mcp

Full release notes: playwright.dev/docs/release-n…

🛠️ playwright-cli v0.1.9 — sharper tools for coding agents:

🎯 highlight + show --annotate for visual confirmation
📦 drop files & clipboard data
🧭 generate-locator for stable refs
🧱 snapshot --boxes with bounding boxes
📤 --raw and --json everywhere

github.com/microsoft/play…