I like infrastructure changes that remove stupid waiting. Not “AI-powered synergy” waiting. Actual waiting. The kind where one bit of software is sitting there with its thumb up its arse because another bit still has the browser.
Cloudflare has changed Browser Run so multiple Workers can connect to the same live browser session. Before this, one session took one connection at a time. Now each puppeteer.connect() call gets its own Chrome DevTools Protocol connection, so several Workers can attach concurrently.
That is genuinely useful.
Stop launching Chrome like it’s disposable cutlery
The old beginner pattern for browser automation is brutally simple: request arrives, launch browser, do thing, kill browser, repeat until the bill arrives or the machine catches fire.
Cloudflare already recommends reusing Browser Run sessions because reconnecting avoids the cold start of launching another browser. The new bit is that session reuse no longer means everyone politely waiting in a queue for the same browser handle.
Multiple clients can now pile into the same browser at once.
And yes, before somebody straps twelve unrelated customers into one browser and calls it “multi-tenant architecture”, Cloudflare explicitly tells you to create a separate browser context for each request. Contexts isolate cookies, local storage and cache. They do not magically turn one shared browser process into twelve independent machines.
That distinction matters.
There’s a money angle too
Browser Sessions are priced on both browser hours and concurrent browsers. So if you can safely push several jobs through one running browser instead of launching several browsers, you are not just shaving latency. You may also be reducing the browser concurrency your workload consumes.
Cloudflare says the same thing in plainer language: sharing sessions means fewer new browsers, less cold-start time and fewer concurrent browsers counted against limits.
That is the sort of optimisation I enjoy because it is not a heroic distributed-systems thesis. It is “stop creating the expensive thing over and over when the expensive thing is already sitting there”.
Beautiful.
I already know what I’m doing with it
I’ve been building PouchQA, a little AI-coded bastard that stress-tests web forms and takes screenshots when they break.
At the moment, the architecture in my head is offensively wasteful: job arrives, browser launches, page loads, test runs, screenshot gets captured, browser dies. Then the next job does the whole bloody ceremony again.
I’m changing that plan.
One shared Browser Run session, separate browser context per test, multiple workers attaching when there is work to do. If one test needs cookies or storage, its context gets them. If another needs a blank slate, it gets one. No need to spin up a fresh browser process every time somebody moves a button three pixels to the left.
That does not mean “one browser forever”. Cloudflare’s own FAQ warns that tabs still share the browser process and memory. Heavy pages can make a shared browser fall over, and one sick browser is still one shared failure domain.
So you measure it. You recycle sessions. You set sensible limits. You do engineering instead of summoning Chrome instances like a wizard with a RAM fetish.
Small feature, proper architectural consequence
This is not the sort of feature that gets a keynote bloke striding across a stage in white sneakers.
It is better than that.
It removes an artificial serial bottleneck from session reuse. It makes the cost model more interesting. It makes long-lived browser workers more practical. And it gives people building agentic browser workflows a cleaner option between “launch everything” and “make everything wait”.
Cloudflare made browser sharing less bloody stupid.
I’m annoyingly enthusiastic about it.