Browser Automation · Public

playwright

Browser automation project for web operations, testing, extraction, and permission-boundary checks.

Browser automationWeb tasksTest accountsCookie boundariesPermission control

Best fitDevelopers who need AI-assisted web tasks, browser testing, page extraction, or structured web operations.

Check whether this project matches your task before installing it.

What it can doBrowser automation task planning, permission boundaries, recovery steps, and acceptance checks

Review the portable capability path.

Before continuingVerify in a sandbox

Do not treat a preview pack as a proven local install.

GitHub snapshot89k stars

5.7k forks · 744 contributors

Official first step Read manual preview Source repository

Publication status · 2026-05-25

What is playwright?

playwright supports browser task automation, web operations, or web data workflows.
Best fit: Developers who need AI-assisted web tasks, browser testing, page extraction, or structured web operations.
Not for: Not for workflows that cannot isolate browser state, account permissions, cookies, or real user data.
Capability added to an AI workflow: Browser automation task planning, permission boundaries, recovery steps, and acceptance checks
First safe verification step: Verify one minimal web task with an isolated browser profile and test account first.
Verification state: source, Quick Start, and sandbox install checks are recorded as passed.
Top risk: The main risk is misusing browser state, account permissions, cookies, or real data during automation.
Evidence base: https://github.com/microsoft/playwright, https://github.com/microsoft/playwright#readme, Human Manual, Pitfall Log

Quick decision

Use this section to decide whether the project is worth a deeper read.

Best forDevelopers who need AI-assisted web tasks, browser testing, page extraction, or structured web operations.

Match the project to your task before installing it.

CapabilityBrowser automation task planning, permission boundaries, recovery steps, and acceptance checks

Browser automation project for web operations, testing, extraction, and permission-boundary checks.

Repositorymicrosoft/playwright

89k stars · 5.7k forks

What it can do

Translate the upstream project into concrete capabilities the user can judge before installing.

Playwright Introduction and Project Overview

Related topics: Package Ecosystem and Monorepo Structure, Test Runner and Execution Engine

Sources: [packages/playwright-core/src/tools/cli-client/skill/SKILL.md](https://github.com/microsoft/playwright/blob/main/packages/playwright-core/src/tools/cli-client/skill/SKILL.md)

Package Ecosystem and Monorepo Structure

Related topics: Playwright Introduction and Project Overview, Client-Server Communication Architecture

Sources: [packages/playwright-core/src/client/connection.ts:10-35]()

Client-Server Communication Architecture

Related topics: Package Ecosystem and Monorepo Structure, Browser Launch and Process Management

Sources: [packages/playwright-core/src/client/channelOwner.ts]()

Browser Launch and Process Management

Related topics: Client-Server Communication Architecture, Browser Implementations and Protocol Support

Sources: [packages/playwright-core/src/server/browserType.ts:1-50]()

Test Runner and Execution Engine

Related topics: Playwright Introduction and Project Overview, Locators, Selectors, and Element Interaction, Assertions, Matchers, and Expect API

Sources: [packages/playwright/src/runner/testRunner.ts:1-50]()

Sources: https://github.com/microsoft/playwright, Human Manual, Project Pack evidence, and downstream validation signals.

Community Discussion Evidence

Project-level external discussion stays visible on the detail page, not only inside the manual.

Stars89k stars

Forks5.7k forks

Contributors744 contributors

Licenseunknown

Community Discussion Evidence

12 source-linked items

Review these external discussions before using playwright with real data or production workflows. They are review inputs, not standalone proof that the project is production-ready.

01
[Feature]: Expose securityDetails() on APIResponse for HTTPS monitoring
github / github_issue
02
[Bug]: Reporter ignores NO_COLOR — colors and cursor codes still emitted
github / github_issue
03
[Bug]: Unable to Listen to Download Event While Using window.showSaveFil
github / github_issue
04
[Feature]: Fail tests on page errors
github / github_issue
05
[Feature]: trace correlation hooks for external observability/replay sys
github / github_issue
06
[Bug]: Trace viewer does not capture some dynamically added CSS classes
github / github_issue
07
[Regression]: install-deps --dry-run can no longer be used to generate i
github / github_issue
08
[Feature]: Trace viewer: Add timeout-risk highlighting for actions in Pl
github / github_issue
09
[Bug]: In VS Code, tests are not displayed in the Testing section.
github / github_issue
10
[Bug]: playwright-cli open fails with EINVAL when session name is long o
github / github_issue
11
[BUG] "NS_BINDING_ABORTED" error in Firefox
github / github_issue
12
[Feature]: Ubuntu 26.04 LTS support
GitHub / issue

How to start

Only source-backed commands are shown here. Verify them in an isolated environment first.

Try the prompt first

Test the workflow without installing the upstream project.

preview

Read the Human Manual

Understand inputs, outputs, limits, and failure modes.

manual

Take context to your AI host

Use the compiled assets in your preferred AI environment.

context

Run sandbox verification

Confirm install commands and rollback before using a primary environment.

verify

npm i -g @playwright/cli@latest

Official start command · https://github.com/microsoft/playwright#readme · verified: yes

Human Manual

The English page must expose the real manual, not a short placeholder.

8+ sections · Human Manual

playwright Manual

Related topics: Package Ecosystem and Monorepo Structure, Test Runner and Execution Engine

Open the full manual

playwright Human Manual
Table of Contents
Playwright Introduction and Project Overview
Related Pages
1. Overview
2. Project Architecture
2.1 Core Packages
2.2 High-Level Architecture

Playwright Introduction and Project Overview

Related topics: Package Ecosystem and Monorepo Structure, Test Runner and Execution Engine

Sources: [packages/playwright-core/src/tools/cli-client/skill/SKILL.md](https://github.com/microsoft/playwright/blob/main/packages/playwright-core/src/tools/cli-client/skill/SKILL.md)

Package Ecosystem and Monorepo Structure

Related topics: Playwright Introduction and Project Overview, Client-Server Communication Architecture

Sources: [packages/playwright-core/src/client/connection.ts:10-35]()

Client-Server Communication Architecture

Related topics: Package Ecosystem and Monorepo Structure, Browser Launch and Process Management

Sources: [packages/playwright-core/src/client/channelOwner.ts]()

Browser Launch and Process Management

Related topics: Client-Server Communication Architecture, Browser Implementations and Protocol Support

Sources: [packages/playwright-core/src/server/browserType.ts:1-50]()

Test Runner and Execution Engine

Related topics: Playwright Introduction and Project Overview, Locators, Selectors, and Element Interaction, Assertions, Matchers, and Expect API

Sources: [packages/playwright/src/runner/testRunner.ts:1-50]()

AI Context Pack and portable assets

After deciding to continue, take the project context into your own AI host.

Complete pack plus user-owned assets

These files are planning and verification assets for Claude Code, Codex, Gemini, Cursor, ChatGPT, and other AI hosts.

Download complete pack Read Human Manual

BundleComplete Project Pack AssetAI Context Pack AssetBoundary & Risk Card AssetHuman Manual AssetPitfall Log AssetPrompt Preview AssetQuick Start ManifestPROJECT_PACK.json

Preflight checks

Treat this page as a planning asset, not proof that your local environment is ready.

The manual is generated from source-linked project files and Doramagic validation signals.
Community evidence warnings stay visible instead of being converted into marketing claims.
This English page is indexable because the locale quality gate passed and explicit English index approval is enabled.
Use the upstream repository as the final authority for installation commands, license, and version-specific behavior.