Great points! For sure, the whole agentic browsers space is still super early.
We are also just getting started and trying to narrow down on a high-value niche use-case.
There are few repetitive, boring use-cases where time saving could be meaningful -- one example: Walmart 3rd-party sellers routinely (multiple times a day) keep checking prices of the competitor products to price their products appropriately. This could be easily automated with current agentic browsers.
But in reality, would much more consistently be automated by a single playwright script.
True, there are plenty of libs already available to do such an automation if you are (or can hire a) dev.
But for non-technical folks, agentic browsers seems like a good UX to build such and many more automations.
Yeah it should have your preferences for things to do stuff based on your aesthetics but I see how it could become security nightmare
I think it'd be better to show more non-trivial examples where the time savings is clear, and the failure cases are minimized... or even better how it's going to recover from those failure cases. Do I get a bespoke UI for the specific problem? Talk to it via chat?
This whole world is non-trivial. Good luck!