Cause (Documented platform behavior): SDK locates exactly one enabled Stagehand extension via CDP; otherwise throws.
Fix status: documented_behavior
Unknowns:
- How to include the extension when creating a session via raw API is not described in this file
Other error fragments:
- The extension must be included when the Browserbase session is created.
- Stagehand extension is installed in the connected browser but is disabled.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/browserbase/stagehand/70f4e91f1983677c1e8ca9a86f0b738f828d059a/packages/sdk-ts/src/cdpClient.ts (official_docs, unknown, documented_behavior): Extension discovery throws distinct errors for none, disabled, or multiple enabled Stagehand extensions.
Search phrasings: Stagehand extension is not installed in the connected browser; stagehand v4 connect existing browserbase session
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Stagehand init fails when attaching.
- Context
- Product: Stagehand Component: Stagehand TS SDK CDP client (extension-backed) Operation: Connecting Stagehand to an existing Browserbase session or browser created without the Stagehand extension Affected versions: unknown Environment: unknown Packages: @browserbasehq/stagehand 4.x (source at time of mining) Trigger: Session was created without the extension (e.g. via raw Browserbase API) or the extension is disabled / multiple copies enabled.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Stagehand extension is not installed in the connected browser.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Stagehand v4 SDK] 'Stagehand extension is not installed in the connected browser. The extension must be included when the Browserbase session is created.' (or 'installed ... but is disa
Recommended action: Create the session through Stagehand (or include the extension at session creation); ensure exactly one enabled copy.
Option: Create the session through Stagehand (or include the extension at session creation); ensure exactly one enabled copy. [evidence: official_recommended_action]
Applies when: Connecting Stagehand to an existing Browserbase session or browser created without the Stagehand extension
Steps:
1. Create sessions via the Stagehand browserbase() factory
2. If creating via API, include the Stagehand extension
3. Remove/disable duplicate copies
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- 3574eb24-6275-4c03-ac06-f389b53e5bb5
- Proposed action
- Recommended action: Create the session through Stagehand (or include the extension at session creation); ensure exactly one enabled copy. Option: Create the session through Stagehand (or include the extension at session creation); ensure exactly one enabled copy. [evidence: official_recommended_action] Applies when: Connecting Stagehand to an existing Browserbase session or browser created without the Stagehand extension Steps: 1. Create sessions via the Stagehand browserbase() factory 2. If creating via API, include the Stagehand extension 3. Remove/disable duplicate copies Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.