BROWSER TOOLS / FRAMEWORKS / CODING AGENTS

Your tools.
A remote browser.

Connect Browser Use, agent-browser, Stagehand, Playwright MCP, Chrome DevTools MCP, Claude Code, and Codex to browser infrastructure. Explore setup, architecture, and runtime requirements.

Choose the layer you want to connect

An agent decides the next action. A CLI or MCP server exposes browser tools. Browser infrastructure supplies the runtime and connection. Start with the tool you already use, then check its attachment method and lifecycle requirements.

Each collection includes an architecture, a setup path, use cases, connection notes, FAQs, and related resources. Documented connection methods describe upstream options; validate your exact runtime combination before production use.

7 BRAND COLLECTIONS

Find your browser workflow

Agent framework

Browser Use + Remote Browser

Use Browser Use with remote Chromium over CDP. Explore persistent login, session ownership, production workflows, and comparisons.

Python Browser(cdp_url=...)8 articles · Explore
Browser CLI

agent-browser + Remote Browser

Connect the agent-browser CLI to a remote CDP endpoint. Understand snapshots, browser ownership, persistent accounts, and runtime trade-offs.

CLI --cdp9 articles · Explore
Agent framework

Stagehand + Remote Browser

Evaluate Stagehand v4 with a remote browser: CDP attachment, extension availability, filesystem requirements, and session lifecycle checks.

localBrowser.connect({ cdpUrl }) + extension4 articles · Explore
MCP server

Playwright MCP + Remote Browser

Attach Playwright MCP to remote Chromium through its CDP setting, then verify navigation, profile state, artifacts, and cleanup.

PLAYWRIGHT_MCP_CDP_ENDPOINT15 articles · Explore
MCP server

Chrome DevTools MCP + Remote Browser

Connect Chrome DevTools MCP to an existing browser for inspection and debugging. Check endpoint type, authentication, and remote artifact handling.

--ws-endpoint / --browser-url8 articles · Explore
Coding agent

Claude Code + Remote Browser

Give Claude Code a remote browser through a skill or MCP tools. Plan authenticated QA, human takeover, and verifiable task outcomes.

Remote Browser Agent skill or MCP3 articles · Explore
Coding agent

Codex + Remote Browser

Use Codex with a remote browser skill for authenticated UI checks and browser workflows, with explicit endpoint handling and task verification.

Remote Browser Agent skill or MCP4 articles · Explore

Evaluating another browser provider?

Infrastructure providers belong to the deployment decision. Use the comparison collection, browser alternatives, or the existing Remote Browser vs Browserbase comparison to evaluate that layer.