Skip to Content

turno-browserMore

Browser tools compared

How turno-browser compares with Playwright MCP, chrome-devtools-mcp, browser-use, Stagehand, Steel, Browserbase and agent-browser, and when each one is the better choice.

View source

This page helps you pick a browser tool for an agent. turno-browser is the layer above the browser driver: identities, a credential vault, sessions you can move, several agents in one browser, record and replay, a live view, and limits on what Chrome keeps in memory. It runs the Playwright MCP tools on your own Chrome, so it sits next to the tools below rather than replacing Playwright.

Every claim about another project comes from its own docs or repository, checked on 2026-11-19 and listed under Sources. Projects change quickly: check their docs before you decide. Facts about turno-browser come from Browser identities, the guide, Security and Benchmarks.

At a glance

Where the browser runsHow an agent uses itLicense and cost
turno-browseryour machine: your installed Chrome, headed, one persistent profile per identityMCP server over stdio; turno-browser do from a shellApache-2.0, free
Playwright MCPyour machine: Chrome, Firefox, WebKit or Edge, headed by defaultMCP server; for coding agents, Microsoft points to its CLI and skillsApache-2.0, free
chrome-devtools-mcpyour machine: Chrome or Chrome for TestingMCP server, a CLI and skillsApache-2.0, free; sends usage statistics to Google unless you opt out
browser-useBrowser Use Cloud by default, or a local Chrome or ChromiumPython library (an agent that runs its own model), CLI, MCP server, hosted APIMIT library; models and cloud browsers are billed per use
Stagehanda local Chrome, or BrowserbaseSDK for TypeScript, Python and Go; a browse CLI for coding agentsMIT; act, extract and observe call a model you pay for, and Browserbase is billed if you run there
SteelSteel Cloud, or self-hosted with Docker or NodeREST API, Node and Python SDKs, an MCP serverApache-2.0 (steel-browser), MIT (MCP server); Steel Cloud starts with free credits, then usage
BrowserbaseBrowserbase's cloudAPI, Stagehand, a hosted MCP serverhosted service: a free plan, then plans billed per browser hour
agent-browseryour machine (Chrome for Testing by default), or a cloud providernative CLI with skills; agent-browser mcp over stdioApache-2.0, free

Signed-in sessions

How you sign in, and how it persists
turno-browserYou sign in by hand once per identity; the cookies stay in that identity's Chrome profile. An optional health check marks an identity NEEDS_AUTH when the sign-in is gone. A session can be exported, encrypted with a passphrase and an expiry, and imported on another machine. Attach mode works in the Chrome you already have open.
Playwright MCPA persistent profile by default, one per MCP client workspace; or an isolated context loaded from a storage state file; or a browser extension that connects to your open Chrome or Edge tabs.
chrome-devtools-mcpA dedicated profile that is kept between runs; or --autoConnect to the Chrome you have open (Chrome 144 or newer, after you allow it in Chrome).
browser-useLocally: the Chrome you have open with your logins, a temporary copy of one of your Chrome profiles, or a user data folder of its own kept between runs. In the cloud: cloud profiles.
StagehandA local user data folder kept between runs; on Browserbase, contexts.
SteelSessions keep cookies and local storage across requests. Saved browser profiles and managed credentials are Steel Cloud features; self-hosted Steel does not have them.
BrowserbaseContexts keep cookies, localStorage, IndexedDB and more across sessions, encrypted at rest on Browserbase's infrastructure.
agent-browserA read-only copy of a Chrome profile, a persistent profile folder, or saved state files restored per session (encrypted when you set a key). It can also attach to a running Chrome.

Credentials and what the model sees

turno-browserA vault per identity in the OS secret store (macOS Keychain or Linux Secret Service). browser_login fills the username, password and current one-time code on the origins you allowed; the agent never sees them, and they are hidden from later results, recordings and the live view.
Playwright MCPA secrets file whose values are replaced in tool responses; its docs call this a convenience, not a security feature, and say the server is not a security boundary.
chrome-devtools-mcpIts docs say it exposes the browser's content to the MCP client, and to avoid sharing what you do not want the client to see.
browser-usesensitive_data: the model types a secret by name and the value is redacted from its output. Its docs say this is not a sandbox, since the Python the model writes can read the value.
StagehandYour code fills credentials: observe() returns selectors, so the values never reach the model.
SteelThe MCP server hands the browser to a person at a login, never guesses a password, and redacts credentials before they reach a response or a log.
BrowserbaseA 1Password integration fills a login the user approves, without returning the values to your application.
agent-browserAn auth vault encrypted with AES-256-GCM; its docs say passwords in it never reach the model's context. It also has domain allowlists, action policies and confirmations.

Several agents at once

turno-browserOne session per identity at a time by default. With tab sharing on, several agent sessions work in one Chrome, each in its own tabs, with locks that keep one session out of another's tabs. They share the identity's cookies; one identity per account keeps accounts apart.
Playwright MCPA persistent profile serves one browser at a time; parallel clients need --isolated or their own profile. Over HTTP, --shared-browser-context shares one context, and a tab can open in its own named isolated context.
chrome-devtools-mcpWhen one server is shared by concurrent sessions, page ID routing lets each session work on its own tab; --isolated gives each server a temporary profile.
SteelThe MCP server allows 10 live sessions per key by default; self-hosted Steel runs one session at a time.
BrowserbaseConcurrent browsers up to your plan's limit. Its docs advise against several sessions on one context at once.
agent-browserEach --session gets its own daemon and browser. Sessions that share one Chrome can pin their tab, and another session cannot take a pinned tab.

Memory on a laptop

turno-browserChrome closes after 15 minutes without a tool call and opens again on the next one. A tab governor caps open pages (8 by default) and parks and closes unused ones. Read mode on Lightpanda measured 64 MB against 913 MB for headless Chrome on the same pages (measurement).
Playwright MCP--idle-timeout closes the browser after an hour without a call when headless; a headed browser stays open unless you set it.
chrome-devtools-mcpIt starts the browser only when a tool needs one.
agent-browserThe daemon closes a headless browser after an hour without commands (headed browsers are exempt), and it can run on Lightpanda.
browser-use, Stagehand, Steel, BrowserbaseWhen the browser runs in their cloud, it takes no memory on your machine.

Record and replay

turno-browserAn agent saves what it did as a flow and replays it later; typed text becomes parameters, and sensitive ones are asked again or read from the secret store. Playwright traces and screenshots are off by default. There is no video.
Playwright MCPRecords what you do by hand as Playwright code, and records traces and video (opt-in tools).
chrome-devtools-mcpPerformance traces with insights, and screencast video.
browser-useRecordings in Browser Use Cloud.
StagehandOn Browserbase, server-side caching returns identical calls without spending model tokens.
SteelA UI to watch sessions live and replay them.
BrowserbaseEvery session is recorded as video by default, one recording per tab.
agent-browserVideo recording (with ffmpeg) and traces; saved flows (experimental) replay a recorded task's requests.

Human take-over

turno-browserOff by default. A live view on 127.0.0.1 shows the agent's tab; pause holds the agent's next call while you act, and on resume the agent is told what changed. Pages that hold a vault value are not shown.
chrome-devtools-mcpWith --autoConnect you and the agent use the same Chrome, so you can switch between your own work and the agent's.
browser-useIn the cloud, you open the live view, act, then continue the same session.
SteelThe MCP server's handoff gives you the browser for a login or a payment and gives it back to the agent, which reads the page again.
BrowserbaseLive View lets you watch, click, type and scroll in a running session; it can be embedded read-only.
agent-browserA stream of the viewport that accepts mouse, keyboard and touch input, and a local dashboard.

Engines

turno-browserYour installed Chrome; read mode on Lightpanda; attach to your own Chrome; Camoufox.
Playwright MCPChrome, Firefox, WebKit, Edge.
chrome-devtools-mcpChrome and Chrome for Testing; other Chromium browsers are not guaranteed.
browser-useA local Chrome, Chromium or Edge, or a cloud browser.
StagehandA local Chrome, or Browserbase.
SteelChrome, driven over the Chrome DevTools Protocol.
agent-browserChrome for Testing, a running Chrome, Lightpanda, Obscura, Mobile Safari in the iOS Simulator, and several cloud providers.

Which one fits

  • Playwright MCP is the better choice when you want Microsoft's MCP server for Playwright, need Firefox or WebKit, want test assertions or Playwright code generated from a session, or work with one account per project. Its CLI and skills use fewer tokens for coding agents. turno-browser serves the same tools, so moving from one to the other keeps an agent's habits.
  • chrome-devtools-mcp is the better choice for debugging and performance work: traces with insights, Lighthouse audits, heap snapshots, console messages with source-mapped stack traces, network mocks. It is maintained in the ChromeDevTools organization.
  • browser-use is the better choice when you want a complete agent that takes a task and finishes it with its own model, from Python, or when you want hosted runs at scale without running browsers yourself.
  • Stagehand is the better choice when you write the automation as code in TypeScript, Python or Go and want act, extract and observe with schemas, against a local Chrome or Browserbase.
  • Steel is the better choice when you want a browser API you can host yourself in Docker, or a cloud browser with an MCP server that hands logins to a person.
  • Browserbase is the better choice when the browsers must run in the cloud: many at once, from servers or CI, with recordings and a live view you can embed in your own app.
  • agent-browser is the better choice when you want a native CLI with skills that match its version, a browser per session, domain allowlists and action confirmations, or engines turno-browser does not have (Obscura, Mobile Safari, cloud providers).
  • turno-browser fits when several coding agents work on one laptop with your own signed-in accounts: one profile per identity, passwords the model never sees, Chrome kept from growing with idle tabs, flows to replay, and a live view to take over. It does not run in the cloud, has no SDK, and does not do performance profiling.

Sources

On this page