floatboat
Open navigation menu

Browserbase

Builds Stagehand and browser infrastructure, connecting deterministic code, agent interaction, and local or hosted browser workflows.

About Browserbase

Browserbase publishes Stagehand and supporting browser tooling. Stagehand is an open-source automation project within a broader browser-service ecosystem; the organization identity should not be confused with one SDK package or one MCP endpoint.

Stagehand is the automation framework; Browserbase supplies hosted browser sessions. A developer can keep stable navigation in code, use language-driven actions for changing controls, and extract a typed result. Local browse is a starting point for exploration; an SDK application makes the resulting workflow maintainable in a codebase.

The current project README is the entry point for choosing browse CLI, SDK, or hosted MCP. Older MCP repositories and major-version examples remain historical material, so follow current links before using a copied configuration.

Software from Browserbase

Explore with browse when the page behavior is still unknown; evaluate SDK code when navigation and extraction need to become part of a maintained application.

Alternatives to Browserbase Workflows

Compare Browser Use for model-driven browser tasks, Vercel Labs for terminal browser control, Microsoft for Playwright MCP automation, Steel for browser session infrastructure. Choose by the browser environment and task result you need.

Frequently Asked Questions

How are Browserbase and Stagehand related?
Browserbase maintains Stagehand, the browser automation framework, and provides hosted browser infrastructure. Stagehand can work with local browsers or Browserbase sessions; using the framework does not by itself require a hosted browser account.
When should I use local browse or a hosted session?
Use local browse to explore an accessible page with your local Chrome. A hosted session is useful when the workflow needs a remotely managed browser; check its account and service requirements separately.
Which MCP documentation is current?
Follow links from the current Stagehand README. The older mcp-server-browserbase repository is archived and should not be the default installation source.
What is the browse Skill for?
It teaches a coding agent to use the browse CLI. It is a companion entry point for browser tasks, not an additional hosted browser entitlement.
Does local use always require a subscription?
The documented local browse mode differs from hosted Browserbase sessions. Check the chosen interface rather than applying cloud billing assumptions to all project use.
How should older examples be interpreted?
Treat them as version-specific. Confirm the installed Stagehand major and current API before translating an old example into a maintained workflow.

Inspect a Changing Portal Interaction

Separate stable navigation from changing controls before investing in an SDK implementation. The first deliverable is a version-matched implementation proposal, not an automatically tested application.

Open Stagehand guide