Passmark hit 500 stars. The pattern we’re seeing: qa teams are done writing locators based scripts. They want to describe the flow and move on. Building the best playwright ai library for regression testing in public. 💪

Just crossed 500 🌠 at Passmark. Help us build the most complete and comprehensive AI-regression testing library. Already merged a few PRs last week and this one. We would love to see more contributions! github.com/bug0inc/passmark

Introducing browsers.bug0.com Instant cloud browsers for automation, testing, and agentic workflows. Pair it with Passmark and browser automation becomes dead simple. No min commitment. Get started with our pay-as-you-go plan.

tap in

Shipping Bug0 Browsers today Real Chromium in the cloud. One API call, one CDP URL. Your Playwright code runs as-is. Sessions spin up in seconds and shut down when you're done. Built for speed. One thing done well. Your agents, crawlers, and test suites need it.

passmark@1.0.8 supports @Cloudflare AI Gateway! btw, we just crossed 200 stars! 🎊 We're just getting started. If you are an SDET you can use Passmark for free within your org and let AI upkeep the burden. Check it out and feel free to contribute. github.com/bug0inc/passmark

we finally open-sourced the core engine of bug0 called passmark. makes the old process of generating scripts with locators instantly redundant. with passmark, you can build a natural language based regression testing suite for your apps, at scale. AI playwright library

RT @Sandeepg33k: Introducing Passmark: an open-source AI agent purpose-built for regression testing at scale. Built on Playwright: natural…

RT @hashnode: announcing Breaking Apps Hackathon - a 4-week challenge to test any web app using AI. write tests in plain english using ope…

hence we do AI QA with adult supervision…

getting ai ask engines to recommend your product is way easier than most think. we did it for bug0 from scratch. 400% growth in 2 months. giving away the playbook in a free 15 min session. covers what we did with docs, blog content, and structured data to show up in ai search results. dm me if you want in.

12 tonnes of KitKats stolen? Thieves took a break... My AI agent just reproduced the bug in my drawer. @KITKAT this is P0.

We now cap interviews at 2 rounds max a short paid trial @bug0inc. Best hires we've made came from that.

I've watched the same thing happen at dozens of SaaS teams: They set up GitHub Actions. Add unit tests. CI goes green. They call it "automated testing." Then a customer reports a bug that no test caught. Because no test was looking.

ai coding models are getting exponentially better each month. teams are shipping new features faster than ever. here are 10 reasons why bug0 might not be a fit for your e2e regression testing… Read more

introducing the qa engineer you never have to onboard. give it a URL. no test plan, no context. it just opens your app and starts browsing like a real user. it finds your signup flow, your search, your checkout. stuff you'd normally spend a week mapping out in a spreadsheet before anyone writes a single test. each flow becomes a draft test. you decide what to keep. we're calling it bug0 discover. the whole thing takes about 5 minutes. but here's the thing. you can leave it running. go to sleep. come back in the morning and it's found flows in your app you didn't even know existed. edge cases nobody on your team thought to document. no qa tool has done this before. most tools wait for you to tell them what to test. this one figures it out on its own. that's not a 2x improvement in qa productivity. that's 1000x. your test coverage grows while you're not even working. here's what it looks like ↓ (video has been sped up)

A dev built an entire SaaS with AI. Zero hand-written code. Users signed up. Weeks later: subs bypassed, API keys maxed, random data in the db. He couldn't debug it. He didn't write it. Shut down permanently. This is the pattern of 2026. hashnode.com/blog/state-of-v…

bug0.com is now open to all. no sales call. no demo. Just sign up and start testing your website with our AI agents.

Every investor says the same thing: services don't scale. We're a software company. We have a self-serve platform. Teams create tests from plain English, run them in CI, get reports. Pure SaaS. But we also have FDE pods - Forward-Deployed Engineers who handle QA testing end-to-end for larger customers. They plan tests, verify results, file bugs, gate releases. Sounds like an agency, right? Here's what I've learned: the service layer isn't a compromise. It's the product lab. Every week, our FDEs see patterns. Where the AI fails. Where customers get stuck. What "done" actually looks like for a VP of Engineering who just wants to ship without worrying, catch regressions early. That feedback doesn't come from analytics dashboards. It comes from being in the workflow. We take those learnings and bake them into Studio. The service makes the software smarter. The software makes the service more leveraged. There's a debate happening right now: are agencies cooked? Can't Claude just do it? Maybe for some things. But for high-stakes work - where quality matters and mistakes cost real money - you need controlled, responsible AI-powered services. Humans in the loop. Judgment. Accountability. YC just published an RFS on this: AI-Native Agencies. Their take - AI lets you sell outcomes with software margins. Not hours. Not headcount. That's the bet we made early @ bug0. Still early, but feels good to see the thesis validated.