Comber is every-click QA for preview deploys. Point it at a URL and it explores your app like a real user — clicking, typing, navigating every reachable state — then files what broke with a repro, screenshot, and trace. One expensive AI run, then deterministic replays for cents, so it fits inside CI on every preview deploy. No test scripts to write, no selectors to maintain. Free to start; bring your own Anthropic key or let us run it.
No reviews yetBe the first to leave a review for Comber
Maker
📌
hey PH — I built Comber because writing end-to-end tests felt like a second job. Scripted suites only catch what you thought to script, they rot the moment a selector moves, and the bug that ships is always on the path nobody wrote a test for.
So Comber goes the other way: point it at a URL — `npx comber check ` — and it explores your app like a person would, clicking and typing through every reachable state, watching the console, network, and accessibility tree. Anything broken comes back with a repro, screenshot, and trace.
The trick that makes it affordable: one expensive AI run maps the app, then every run after that is a deterministic replay that costs cents. That's what lets it live inside CI on every preview deploy instead of nightly.
Honest fine print: commercial, not open source. Free with your own Anthropic key; hosted plans if you'd rather not think about it. No card, no sales call.
It caught a real bug on its own homepage the week before this launch, so I trust it a little more than I did. Tell me where it breaks on yours — that's the feedback I actually want.
Report
Pointed it at a staging build and it actually clicked through the onboarding flow, caught a broken redirect, and handed me a clean repro with screenshots. The deterministic replay piece is genuinely clever since the first run is the only expensive one. Solid fit for CI.
Report
Maker
@phineas_luo That's the first time I've heard about it catching something on someone else's app — thank you for actually running it. A broken redirect in an onboarding flow is exactly the shape of bug I built this for: nobody writes a test for the path that's supposed to just work, and it's the first thing a real user hits.
Curious about one thing if you end up wiring it into CI: how does the replay hold up when your onboarding copy or layout shifts? That's the seam I'm watching hardest right now — replays are cheap because they don't re-explore, and the open question is how much drift they tolerate before a re-map is the honest answer. If you hit a false positive there I'd genuinely like to see it.
Pointed it at a staging build and it actually clicked through the onboarding flow, caught a broken redirect, and handed me a clean repro with screenshots. The deterministic replay piece is genuinely clever since the first run is the only expensive one. Solid fit for CI.
@phineas_luo That's the first time I've heard about it catching something on someone else's app — thank you for actually running it. A broken redirect in an onboarding flow is exactly the shape of bug I built this for: nobody writes a test for the path that's supposed to just work, and it's the first thing a real user hits.
Curious about one thing if you end up wiring it into CI: how does the replay hold up when your onboarding copy or layout shifts? That's the seam I'm watching hardest right now — replays are cheap because they don't re-explore, and the open question is how much drift they tolerate before a re-map is the honest answer. If you hit a false positive there I'd genuinely like to see it.