Is the browser instance able to be shared across nodes?

[evok01]

Is it possible to have a pupeteer node that starts a browser session but keeps it open so that another pupeteer node can pick up where it left off? The browserless documentation suggests this is possible if you enable PREBOOT_CHROME and KEEP_ALIVE, but even when setting both of those, it looks like this node closes every browser instance when it is done.

I have two pupeteer nodes and an email node in the middle. The first pupeteer node does the login, then I fetch the OTP from email and the other pupeteer node attempts to enter the code on the same page. It always errors though because I found the second pupeteer is always attempting to use a fresh browser instance.

Also, both of these nodes use the Browser WebSocket Endpoint setting pointing to the same URL using the same token.

[drudge]

Hi David, it is not currently possible as each run closes the browser. It's absolutely possible to do technically - I just haven't had time to add it yet.

I'm adding it to the backlog to work on as time permits. If you are willing and able, PRs welcome!

[conor-is-my-name]

I'd also use this, very helpful for staying logged into websites

would also be fine with all cookies and user sessions being saved and then loaded for each session