Launching today
BrowserBash
CLI that turns plain-English into real browser tests
79 followers
CLI that turns plain-English into real browser tests
79 followers
Free, open-source CLI that turns one plain-English sentence into a real browser test — no selectors, no code, no flaky locators. Runs on free local models (Ollama) or free OpenRouter models, so there are zero API keys and no credit card. Works with local Chrome, LambdaTest, BrowserStack, Browserbase or any CDP endpoint. `npm install -g browserbash-cli` and automate any site in seconds. Apache-2.0.
OneUp
@promode_ Looks great and something I'd like to use, but my machine isn't powerful enough to drive local models. Can I use an AI subscription instead?
OneUp
@artk yes, you can use the openrouter, Groq.com APIs
Really interesting project! 🚀
The idea of describing a test instead of writing selectors is compelling, especially for quickly validating user flows.
I'm curious: if the UI changes significantly between releases, how does BrowserBash decide whether it's the same workflow with a different layout versus an actual regression that should fail the test?
Love that it supports local models via Ollama right out of the box so we don't burn through API credits testing basic flows. Going to point this at my onboarding sequences today!
OneUp
@varunvivek Thank Vivek, You can always use cheaper model like Deepseek V4 Flash, Qwen3.5 models to automate scenarios, cost is very low.
https://browserbash.com/math.html
We've gone from writing tests to describing tests. At this rate the browser is going to start filing bug reports against itself.
OneUp
@jacob_spencer2 😄 Honestly not far off, every run already returns a pass/fail verdict and a video recording of what it did, so the browser's basically halfway to filing its own incident report. "Describing tests" was the whole bet: say what done looks like, let the agent figure out the clicks. Thanks Jacob 🙏
great man, how would you montize it if it is free
OneUp
@marc_vuit @marc_vuit great question 🙏 The CLI and local runs stay free forever, that's the open-source core, and I want it to stay that way. Monetization is opt-in: a paid tier for keeping your cloud run history + recordings past the free 15-day window. Free runs auto-expire after 15 days; if you want them retained, you upgrade. Team/hosted features are on the roadmap too. The free tier isn't a trick to upsell later it's the actual product.