Probe is agentic testing for the AI-native team. One autonomous agent covers your web, mobile, and APIs end-to-end discovering surfaces, generating tests in plain English, running them on every commit, and triaging regressions while you ship. Get verified bug reports with screenshots, traces, and reproduction steps delivered straight to GitHub, Linear, and Slack no selectors to maintain, no flaky scripts to debug. Find issues in hours, not weeks. Stop writing tests. Start shipping.
Hey Product Hunt π
I kept seeing the same thing at every engineering team I worked with: ship velocity went up 5Γ in two years, and the QA stack stayed stuck
in 2018. Brittle Selenium scripts. Playwright fixtures nobody owns. A CI suite everyone learned to ignore. Coverage shrank silently as the
codebase grew.
We built Probe because QA shouldn't be something you maintain β it should be something that runs itself. Probe is one autonomous agent that
covers your web, mobile, and APIs end-to-end: it discovers surfaces on its own, generates tests in plain English, runs them on every
commit, and triages regressions while you ship. No selectors. No fixtures. No DSL. Verified bug reports β with screenshots, traces, and
reproduction steps β land straight in GitHub, Linear, or Slack.
The hardest part wasn't building the agent. It was building one whose bug reports you'd actually trust. We threw out our first three
architectures before the answer clicked: less prompting, more deterministic tooling, tighter feedback loops, and a planner that explains
exactly what it's testing and why.
Two things that are still surprising us:
1. Most regressions Probe catches are flows nobody had a test for in the first place.
2. Teams that adopt it stop writing tests within a week β they just describe surfaces.
If your team ships faster than your tests can keep up with, please try a run on your own product and tell us what broke β or, hopefully,
didn't. We're reading every comment today
Hritvik & the Probe team
Suprbox
mailX by mailwarm
Can you review and edit the generated test steps before theyβre added to the suite?