Super cool!

1. Self healing means that it detects it needs some new helper function to complete a task. So, it adds it by itself while doing the task. 2. Will consider yes. 3. Nothing. Only if you decide to use remote browsers, we use the API Key to create one for you

Interesting way to put it. Maybe it is.

Browsers don't sign ToS, users do. Use it with care.

PW is usually easier to detect. Using raw CDP is in our opinion much better for this.

We published a survey of stealth browsers just yesterday https://botforensics.com/blog/stealth-browser-survey-april-2...

There's still plenty that Browser-Use could improve in terms of stealthiness.

We didn't detect it using CDP (good!) but can still detect that it is Browser-Use.

This is an advertisement that looks like a technical blogpost for a moment.

So only a stealth advantage?

Curious why? You can just take this and run locally or deploy anywhere you'd like with any provider agent provider.

Hey! Where did you submit this exactly? Can you provide a link? Will ask others on the team also, but I am not sure what you are referring to.

yes: https://github.com/browser-use/browser-use/security/advisori...

404 for me

Its 404 because its reported to them "privately" via the "Security and Privacy" tab. It has just been ignored by them.

Agreed, the pattern is converging across the industry. The Unikraft setup is where it gets interesting for us with sub-second boots (or sub 100ms even), scale-to-zero that suspends the VM after a few seconds of idle (frees resources), and dedicated bare metal in AWS so we're not sharing hardware.

We haven't open-sourced the control plane glue yet but it's something we're thinking about. browser-use itself is open source. The sandbox infra on top is the proprietary part for now.

Exactly, this is the very stuff I'd be interested to hear more about. Great work on all this btw and best of luck going forward!