guides: pin Stagehand to 3.x and say why - #106
Merged
Merged
Conversation
Stagehand 4 moved its DOM work into a Chrome extension loaded through the CDP Extensions domain, which Lightpanda does not implement, so localBrowser.connect() fails against it. The guide's code is the 3.x API.
cdebled
self-requested a review
September 22, 2026 12:40
cdebled
approved these changes
Sep 22, 2026
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.
Stagehand 4 (npm
latest) moved its DOM work into a Chrome extension thatlocalBrowser.connect()loads through the CDPExtensionsdomain, which Lightpanda does not implement, so it cannot connect. The install line now pins@browserbasehq/stagehand@3, which is the API the guide already uses, with a sentence explaining the pin.