Bring your own browser?

[AdamGoodApp]

I have my own browser instance running that I would like Stagehand to attach to.

Is this possible?

[filip-michalsky]

can you say more? What kind of browser and where is it running? we do support a local mode currently.

[marchellodev]

+1 for this one. I wish there was an option to pass in a custom Playwright Browser through the config

Use cases:

• To be able to attach cookies / browser extensions
• To be able to use custom chrome builds
• To be able to use firefox / safari

At work I am forced to use a corporate laptop, on which all the browsers are blocked except for chrome on a specific path
Hence, playwright does not work, unless I specify the path to the chrome manually

[AdamGoodApp]

can you say more? What kind of browser and where is it running? we do support a local mode currently.

I have a Chromium browser running in a docker container I would like stagehand to attach to.

[kamath]

Hey!

Multiple browsers is unfortunately not on the roadmap as of now. We want Stagehand to be really really good on Chrome, and our roadmap is actually more likely to include performance upgrades for users running on Chrome at the cost of degraded support for Firefox/Safari.

If you're interested in browser customization, I highly recommend checking out Browserbase for stuff like custom contexts and extensions while we work on implementing those features natively in Stagehand

[shuangg]

@kamath He meant attaching to an existing browser session.

[rdvo]

yeah ifi have a chromium running on my own server could i point stagehand at that wss:// browser CDP protocol and control it the same way, it shoudl work theoretically

[miekassu]

I would like to do something like this

import { chromium } from 'playwright-extra'

const browser = await chromium.launch()

const context = await browser.newContext({
    // custom state
    storageState: loadStorageState(),
})

const stagehand = new Stagehand({
  ...StagehandConfig,
  // Use your own context
  context,
})

[jonastemplestein]

I'd really like to be able to connect to the local Chrome on my Mac via CDP, too. This is so I can re-use the cookies/localstorage in there

So I'd log into a bunch of systems in Chrome (including "hard to log into" ones) and then run the stagehand program

[misprintt]

Not being able to pass arguments to the Playwright context (i.e. browser.newContext({...}) is a major blocker.

This prevents Stagehand from being used in real-world projects that depend on options in Playwright’s BrowserContextOptions (docs).

I like @miekassu’s suggestion of passing through an existing context.

If that’s not feasible, could you add Playwright’s BrowserContextOptions to StagehandConfig so they can be passed to the internally created context?

[jackthedev]

+1 for Chrome CDP support

We currently use tools to manage multiple browser "profiles" (each with their own cookies and storage) that are accessible via CDP.

Currently we maintain Playwright automation scripts for these profiles and we'd like to use Stagehand to simplify our automation workflow.