Launching today

fastbrowse
Fastest open source browser agent
34 followers
Fastest open source browser agent
34 followers
A fast open-source browser agent. It reads every button, link and field on the page and has a System One model (ex: jev) pick the next step from that list. If it's unsure, it falls back to a standard model model. Fast, cheap, and every answer provides a citation.


Free
Launch Team / Built With

Framer AI AgentsDesign and publish professional sites with AI
Promoted


Hey Product Hunt, I'm Furqan, one of the makers of fastbrowse.
Browser agents have become exceptionally popular, but there's some huge problems. They're slow, expensive and miss easy tasks.
A lot of them take a screenshot and have a slow model decide every step, so each task takes a while and the bill adds up.
Fastbrowse reads the elements on the page instead. Every button, link and field is handed to a System One model (like Jev) with a list of choices. This model decies what to do next, when it isn't sure, fastbrowse falls back to a LLM to get it right. And because it only picks from what's on the page, it can't click something that isn't there.
We tested this against the latest open-source browser agents agent: same sign-in and add-to-cart task on a demo shop, three runs each.
fastbrowse took 25.7 seconds and $0.020 a run. Browser Use took 42.2 seconds and $0.045. Both got it right every time. On a wider 46-task benchmark against Browser Use's hosted agent running Claude Opus, our median task cost $0.026 vs $0.284. 99.2% of tasks passed.
Fastbrowse produces citations for everything it referenced to get answers, so you can trust and verify the results.
It's MIT licensed, and the code, the benchmark harness and the raw results are all on GitHub: https://github.com/agent-labs-dev/fastbrowse
Congrats on the launch, Furqan! Sharing the benchmark harness and raw results on GitHub is the kind of transparency that makes me trust a tool right away.
Question from the design side: since fastbrowse reads the elements instead of screenshots, how does it handle icon-only buttons with no label, or canvas-heavy UIs where there's barely any DOM to read? Feels like this approach quietly rewards apps with good accessibility, which I love.
We're launching on Product Hunt today too, good luck! 🚀