- Teams evaluating browser agents for complex web workflows
- Researchers benchmarking long-horizon web task performance
- Developers who want a browser automation framework with agent-oriented primitives
MIT · Agents
Webwright
Microsoft's open-source browser agent framework for long-horizon web tasks.
5.2K stars 0.3K forks MIT license 2026-06-09 verified
$
# Webwright$
pip install webwright$
npx webwright --help Open source
Overview
What is Webwright?
Webwright is an open-source browser agent framework from Microsoft that targets SWE-style, long-horizon web tasks. It is useful for teams comparing browser-use style agents, Playwright-based automation, and agent frameworks that need repeatable web task execution.
Long-horizon browser focus
Webwright is positioned around multi-step web tasks rather than isolated browser commands.
Long-running workflows need state tracking, retries, and task decomposition that basic automation scripts often lack.Research-friendly surface
The project is useful for comparing browser agent performance across repeatable tasks.
Teams can use it as a benchmarkable alternative to ad hoc browser agent demos.Microsoft backing
The repository is maintained under the Microsoft GitHub organization.
A major maintainer increases the odds of documentation, issue visibility, and ecosystem attention. Use cases
What teams use it for
Ecosystem
Tags & capabilities
Comparison
How it stacks up
Choose Webwright for long-horizon experiments
vs browser-usebrowser-use is a popular practical browser agent library. Webwright is especially interesting when the test workload resembles SWE-style long web tasks.
FAQ
Questions
Is Webwright open source?
Yes. The GitHub repository is listed under the MIT license.
Who should evaluate Webwright?
Teams researching or prototyping long-horizon browser agents should put Webwright on the shortlist.
Decision brief
JSON
Should you use Webwright?
- Teams that only need a simple scraper
- Users looking for a no-code browser automation product
- Verified 2026-06-09
- License: MIT
- Repo: microsoft/Webwright
- Open-source signal
Deployment
Check source
Permission surface
browser
Decision signals
No extra signals recorded
Agent packet
Structured decision data for Webwright
This packet is the compact machine-readable view agents should use before following source links or taking action.
Capabilities
workflow orchestration
Constraints
open source
Deployment
Check source
Permission surface
browser
Recommended workflows
Browser automation, Coding agent workflow, Evaluation and observability, Reusable skill workflow
Overview
What Webwright does
What it is
It is a developer framework for evaluating and building agents that operate websites across multiple steps.
Why it matters
Browser automation is one of the clearest places where agents can turn language instructions into real work, but long tasks need more than a simple click loop.
How to evaluate it
Start with the official repository, run the examples, and measure completion rate on a small set of workflows before connecting sensitive accounts.
Facts
Known metadata and operating surface
These fields are separated from editorial interpretation so agents can reason over facts and missing checks.
Resource type agent
Category Agents
Maturity active
Difficulty Unknown
License MIT
Pricing open source
Verified 2026-06-09
Source confidence medium
Risk level moderate
Fit matrix
Where Webwright fits in an agent stack
strong
Browser automation
Webwright has multiple signals for browser automation, including matching tags, capabilities, category, or positioning.
- Run one non-sensitive website task and inspect clicks, waits, retries, and changed URLs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Coding agent workflow
Webwright has multiple signals for coding agent workflow, including matching tags, capabilities, category, or positioning.
- Run a small repository change and inspect the diff, tests, and rollback path.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Evaluation and observability
Webwright has multiple signals for evaluation and observability, including matching tags, capabilities, category, or positioning.
- Add one repeatable test case and confirm results can run again in review or CI.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
strong
Reusable skill workflow
Webwright has multiple signals for reusable skill workflow, including matching tags, capabilities, category, or positioning.
- Run one skill end to end and check whether it produces evidence or structured output.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
weak
Connector or protocol layer
Webwright is not primarily positioned for connector or protocol layer in the current metadata.
- Connect one low-risk service, then inspect schemas, auth scope, errors, and logs.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
weak
Local or private AI stack
Webwright is not primarily positioned for local or private ai stack in the current metadata.
- Verify hardware requirements, data path, storage, and whether all calls stay in your environment.
- Confirm official docs, current maintenance, license, and runtime constraints before production use.
Inputs and outputs
What an agent should inspect
Likely inputs
- Web pages, DOM state, screenshots, forms, or browser sessions
- Repositories, files, issues, terminal output, and test results
- Official setup instructions and a small real workflow
Likely outputs
- Action traces, changed pages, extracted data, or completed browser steps
- Diffs, commits, explanations, test results, or review notes
- Scores, traces, regression results, dashboards, or failure cases
- A decision on whether this resource fits the target workflow
Evidence
Sources, claims, and missing checks
Claims are marked separately from source links so future crawlers and reviewers can update them without rewriting the page.
Webwright is listed as open source.
License metadata: MITWebwright has a recorded GitHub repository: microsoft/Webwright.
Resource facts and GitHub source link.Webwright is tagged with workflow orchestration capabilities.
OpenAgent capability taxonomy.- Dedicated docs link is missing.
- Repository freshness has not been recorded.
Next action
How to start evaluating Webwright
Inspect repository
Check license, recent activity, issues, examples, and security-sensitive code paths.
Open source Compare
Alternatives and nearby resources
Use related resources to compare category fit, license, deployment model, and first-workflow behavior.
FAQ
Common questions about Webwright
Is Webwright open source?
Yes. The GitHub repository is listed under the MIT license.
Who should evaluate Webwright?
Teams researching or prototyping long-horizon browser agents should put Webwright on the shortlist.