ChangeGamer

browser-use vs Playwright MCP vs Stagehand: Which Open Browser Harness to Pick

Part 2 of Browser agents and agentic browsing in production · 1,592 words · ~7 min read · published · updated · Markdown variant

browser-use vs Playwright MCP vs Stagehand compared as of 13 November 2026: how each exposes the browser to the model, grounding, language, session handling, the security caveats the READMEs state, hosted options and a decision table.

In short

  • As of 13 November 2026, Playwright MCP gives an MCP client browser tools over accessibility snapshots, browser-use 1.0 lets the model write Python against raw Chrome DevTools Protocol, and Stagehand v4 gives act, observe and extract primitives in TypeScript, Python or Go.
  • Playwright MCP and browser-use carry explicit security caveats in their READMEs, the Stagehand README has none beyond a secrets-handling pattern, and none of the three presents its restrictions as a sandbox, so isolation must come from a container or VM that you provide.
  • Playwright MCP is Apache-2.0 and both browser-use and Stagehand are MIT, so licence does not separate these three; language, how the model drives the browser, and session handling do.
  • The Playwright MCP README says coding agents may prefer Playwright CLI plus skills because CLI calls avoid loading large tool schemas and verbose accessibility trees, which makes token cost a real argument against MCP for that case.
  • ChangeGamer runs no browser harness, not even in CI, because its accessibility gate is a static lint over generated HTML, which shows that checking your own HTML may not need a browser agent at all.

Part of the Agentic Browsing in Production: Building, Securing and Preparing for Browser Agents guide.


For the choice between browser-use, Playwright MCP and Stagehand, our reading as of 13 November 2026 is this: take Playwright MCP when an MCP client should drive a browser through accessibility snapshots, browser-use 1.0 when you want the model to write Python against the browser, and Stagehand v4 when you want natural-language primitives inside your own TypeScript, Python or Go code. Every fact about the three projects below comes from their READMEs, fetched on 13 November 2026, except where we say otherwise, and all three move fast, so re-read them before you commit. The wider decision order is in the agentic browsing pillar; the vendor model loop is in how the computer use API loop works.

How does each harness expose the browser to the model?

Each harness exposes the browser differently: Playwright MCP as fixed MCP tools, browser-use as a Python REPL, and Stagehand as SDK primitives. The design difference decides who writes the control code.

Harness What the model sees (README, 13 November 2026) Who writes the control code
Playwright MCP MCP tools over structured accessibility snapshots; browser_click takes an element reference from the snapshot; coordinate tools are opt-in via --caps=vision The MCP client's model picks from fixed tools
browser-use 1.0 One persistent Python REPL, the browser-harness helpers and raw Chrome DevTools Protocol (CDP); mode='ultrafast' acts on accessibility-tree ids The model writes Python
Stagehand v4 act, observe and extract primitives plus Playwright-style methods such as goto, click and locator You write the flow; the model fills in single steps (our reading)

The browser-use README puts its design in one line: the model, a REPL and CDP are "the whole agent".

How do grounding, language and runtime compare?

Grounding is accessibility-tree based in Playwright MCP, accessibility-tree ids in browser-use's ultrafast mode (the README does not describe default mode's grounding), and a trimmed accessibility tree in Stagehand's own description, while runtimes differ by language.

How does each harness handle sessions and profiles?

Each harness defaults differently on persistence: Playwright MCP keeps a persistent per-workspace profile, browser-use defaults to a Browser Use Cloud browser (with a fresh temporary local profile via Browser('chromium')), and Stagehand launches with a userDataDir you choose. Persistence decides how much of your logged-in state the agent can touch.

Mode Playwright MCP browser-use 1.0 Stagehand v4
Persistent Default: a per-workspace profile, usable by only one browser instance at a time Browser('chromium', user_data_dir='~/bu-profile') keeps its own logins between runs; profile='Work' uses a temporary copy localBrowser.launch({ userDataDir })
Isolated --isolated keeps the profile in memory; --storage-state loads cookies and local storage into it Browser('chromium'): a fresh temporary profile, deleted afterwards Not described in the README text we read
Attach to your Chrome --extension connects to a running Edge or Chrome through the Playwright Extension Browser('chrome'): "the Chrome you have open, with your logins" Not described in the README text we read

The row to worry about is the last one. A harness attached to your real browser acts with your accounts, which is the blast-radius problem the pillar covers under logged-in sessions. For parallel Playwright MCP clients, the README says to use --isolated or distinct --user-data-dir values.

What do the projects say about their own security limits?

The Playwright MCP and browser-use READMEs are blunt about their limits, and neither offers a sandbox; the Stagehand README has no security section, only the secrets pattern below. These are the projects' words, not ours.

The common lesson is to treat every restriction flag as hygiene and put the real boundary underneath. Sandbox choice is covered in how to choose a sandbox.

What hosted options exist for each harness?

Browserbase and Browser Use Cloud host browsers; Playwright MCP you host yourself.

Which harness for which situation?

The table is our reading of the READMEs, not a benchmark.

Situation Our pick Why (our reading)
An MCP client such as an IDE agent needs to drive a browser Playwright MCP It is an MCP server over accessibility snapshots, with Node and any client
You want the model to improvise with code on varied sites, in Python browser-use 1.0 The model writes Python in a REPL; plan for a container because its guards are not a sandbox
You own the flow and want natural-language steps that return selectors Stagehand v4 act, observe and extract sit inside your own TypeScript, Python or Go code
Checking HTML you generate yourself No browser agent A static lint can decide it, as below
Credentials must stay out of the prompt Stagehand v4 pattern observe returns selectors, and your code fills the secret
Parallel runs on one machine Playwright MCP with --isolated A persistent profile allows one browser instance at a time

Should a coding agent use Playwright MCP at all?

Our reading: maybe not. The Playwright MCP README itself says a coding agent might benefit from Playwright CLI plus skills instead, "because CLI invocations are more token-efficient". It cites avoiding large tool schemas and verbose accessibility trees in the model context. The README says MCP remains relevant for specialized loops that benefit from persistent state and rich introspection, such as exploratory automation, self-healing tests or long-running autonomous workflows where continuous browser context outweighs token cost.

Where does this differ from the corpus reference?

The reference at computer use and browser automation, updated 22 July 2026, differs from the READMEs we read on 13 November 2026. It describes browser-use as screenshots plus accessibility information with a v0.13+ beta on a Rust core, and Stagehand as v3. The browser-use README now describes 1.0, a REPL and raw CDP, and no longer mentions a Rust core. The Stagehand README documents v4 with TypeScript, Python and Go SDKs. Treat the READMEs as newer, and expect the reference to be refreshed separately.

Do you need a browser agent at all?

Often not, and ChangeGamer is a small example: it runs no browser harness anywhere, not even in CI. Its accessibility gate, scripts/verify-a11y.mjs, describes itself as a "Static accessibility lint over dist HTML ... No dependencies, no browser". That fits because the pages are generated HTML that a regular expression can check deterministically. This is a design choice, not a harness test. The lesson is narrow: if the job is checking HTML you generate yourself, start without a browser agent.

One pointer beyond the three

Skyvern is the open option outside this comparison: its README describes automating browser workflows with LLMs and computer vision, and its core is licensed AGPL-3.0 (anti-bot measures excepted), which matters if you embed it in a product.

Frequently asked questions

Is browser-use better than Playwright MCP?
Choosing between browser-use and Playwright MCP has no general winner, because they hand the model different things: as of 13 November 2026 browser-use 1.0 lets the model write Python against raw CDP in a persistent REPL, while Playwright MCP gives an MCP client fixed browser tools over accessibility snapshots. Pick by who writes the control code, not by a benchmark, because we know of no published head-to-head.
Does Playwright MCP need a vision model?
Playwright MCP does not need a vision model: its README says it uses the accessibility tree rather than pixel input and needs no vision model. Coordinate-based mouse tools exist, but they are opt-in through the --caps=vision flag, so a default install works purely on structured snapshots.
Is Stagehand the same as Browserbase?
Stagehand and Browserbase are different things: Stagehand is an MIT-licensed SDK published by Browserbase Inc., and it runs on a local Chrome as well as on Browserbase. Browserbase is the hosted browser service, which adds a model gateway and server-side caching when Stagehand runs there.
Can browser-use, Playwright MCP or Stagehand safely run untrusted tasks?
None of the three should run untrusted tasks on its own restrictions. browser-use calls its domain limits a guard for an aligned model, not a sandbox, and Playwright MCP says its origin lists are not a security boundary. Run untrusted tasks in a container or VM, as the browser-use README advises.

#browser-agents #browser-use #playwright-mcp #stagehand #harness #accessibility-tree #cdp

Put this corpus inside your own agents

This guide is free and stays free. The reference corpus behind it — machine-readable contracts, verified primary sources, continuously refreshed — is the paid product: a €5 starter key unlocks every premium reference for one agent via API; a €25 corpus license delivers the full corpus as RAG / fine-tuning data with an explicit AI-use grant; the €150 enterprise license adds commercial redistribution rights.

Agents: this page as Markdown · JSON · offers at /api/pricing.json · payment methods at /api/payment.json · single-resource access via HTTP 402 (how that works)