Is your feature request related to a problem? Please describe.
I'm frustrated that the product is so close to what I need but missing one simple thing: All sessions are connected to the same browser when running in a docker container!
Describe the solution you'd like
When you create a session, it should be in a separate browser.
Describe alternatives you've considered
I've migrated off of steel's docker containers and am using Puppeteer processes spawned locally instead.
Use case
A multi-tenant application that does not want to adopt the SaaS yet but could be convinced once we show value with the OSS deployment.
Implementation ideas (optional)
Disable browser reuse by forcing shouldReuseInstance to false inside CDPService.launchInternal(), so every startNewSession() spawns a new browser process instead of reusing.
Would you be willing to contribute this feature?
Is your feature request related to a problem? Please describe.
I'm frustrated that the product is so close to what I need but missing one simple thing: All sessions are connected to the same browser when running in a docker container!
Describe the solution you'd like
When you create a session, it should be in a separate browser.
Describe alternatives you've considered
I've migrated off of steel's docker containers and am using Puppeteer processes spawned locally instead.
Use case
A multi-tenant application that does not want to adopt the SaaS yet but could be convinced once we show value with the OSS deployment.
Implementation ideas (optional)
Disable browser reuse by forcing shouldReuseInstance to false inside CDPService.launchInternal(), so every startNewSession() spawns a new browser process instead of reusing.
Would you be willing to contribute this feature?