You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat(cli): add experimental browse setup for Stagehand MCP - #3328
Now that Stagehand Middleware is published, coding agents need an easy way to connect to Stagehand MCP.
This experimental addition needs a one-off Browse CLI release. After that, compatible Stagehand Middleware updates do not require another Browse CLI release. Users just rerun browse setup and restart their agent to get the latest compatible MCP runtime.
What
Add browse setup to configure browse skills, Stagehand MCP, or both for Claude Code, Codex, Cursor, and OpenCode v2.
browse setup
├── Install or update the latest compatible Stagehand Middleware
├── Connect selected agents to Stagehand MCP
└── Choose local Chrome or Browserbase cloud
How
Install the MCP runtime independently of Browse CLI, so middleware updates can reach users without updating the CLI itself. Rerunning setup updates the runtime while preserving unrelated agent settings and server environment overrides.
Validation: build, formatting, lint, type checks, and all 540 CLI tests passed.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
This PR is from an external contributor and must be approved by a stagehand team member with write access before CI can run.
Approving the latest commit mirrors it into an internal PR owned by the approver.
If new commits are pushed later, the internal PR stays open but is marked stale until someone approves the latest external commit and refreshes it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BetterShot_2026-10-27-14-21-04.mp4
Why
Now that Stagehand Middleware is published, coding agents need an easy way to connect to Stagehand MCP.
This experimental addition needs a one-off Browse CLI release. After that, compatible Stagehand Middleware updates do not require another Browse CLI release. Users just rerun
browse setupand restart their agent to get the latest compatible MCP runtime.What
Add
browse setupto configure browse skills, Stagehand MCP, or both for Claude Code, Codex, Cursor, and OpenCode v2.How
Install the MCP runtime independently of Browse CLI, so middleware updates can reach users without updating the CLI itself. Rerunning setup updates the runtime while preserving unrelated agent settings and server environment overrides.
Validation: build, formatting, lint, type checks, and all 540 CLI tests passed.