Open
Conversation
Update SKILL.md and REFERENCE.md to reflect new browse env local behavior: auto-discovers existing Chrome with remote debugging, --isolated flag, and explicit CDP target (port or URL). Sister PR to browserbase/stagehand#1886. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
7 tasks
shrey150
added a commit
to browserbase/stagehand
that referenced
this pull request
Mar 27, 2026
) ## Summary - `browse env local` now auto-discovers an already-running Chrome with remote debugging enabled (via `DevToolsActivePort` files and common port probing), attaching to it instead of always launching an isolated browser - Falls back to isolated launch when no debuggable Chrome is found — keeps the command reliable - Added `--isolated` flag to force clean isolated browser (old behavior) - Added positional CDP target argument: `browse env local 9222` or `browse env local ws://...` - `browse status` now reports `localStrategy`, `localSource`, `resolvedCdpUrl`, and `fallbackReason` **Sister PR:** browserbase/skills#54 ## Test plan <img width="698" height="373" alt="image" src="https://github.com/user-attachments/assets/1612cf7e-61f4-46b8-9cc6-e739c7363a5a" /> - [x] All 44 existing tests pass - [x] `browse env local` with Chrome running + `--remote-debugging-port=9222` → attaches to existing Chrome - [x] `browse env local` without debuggable Chrome → falls back to isolated launch - [x] `browse env local --isolated` → always launches clean browser - [x] `browse env local 9222` → persists CDP strategy targeting 127.0.0.1:9222 - [x] `browse status` shows local strategy details - [x] `browse env remote` → unchanged 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
browse env localauto-discovery behavior (attaches to existing debuggable Chrome, falls back to isolated)--isolatedflag to force clean browserbrowse env local <port|url>browse statusfields:localStrategy,localSource,resolvedCdpUrl,fallbackReasonSister PR to browserbase/stagehand#1886.
🤖 Generated with Claude Code
Note
Low Risk
Documentation-only updates describing new
browse env localbehaviors and additionalbrowse statusfields; no runtime code changes.Overview
Updates
REFERENCE.mdandSKILL.mdto document enhanced local mode behavior forbrowse env local, including auto-discovery of an existing debuggable Chrome, fallback to launching an isolated browser, and a new--isolatedflag to force a clean instance.Adds guidance/examples for attaching to an explicit CDP target via port or WebSocket URL, and notes additional
browse statusfields reported in local mode (localStrategy,localSource,resolvedCdpUrl,fallbackReason).Written by Cursor Bugbot for commit e1cd472. This will update automatically on new commits. Configure here.