Find the tests you didn’t know to write. Tell Wren what should work in plain English. Its QA agents try the paths your customers take, like going back to change an address halfway through checkout or retrying a failed payment. When something breaks, you get a replay and the steps to reproduce the bug. First 10 runs free.
Hey Product Hunt! I’m Tom, co-founder of Seldon. We built Wren because your entire test suite can pass and a customer can still find a bug five minutes after you ship.
We’re an applied research lab in SF. Our team includes researchers from MIT and Berkeley and people who’ve built products at Meta and Spotify. We put people and agents in front of the same screens and study where their decisions differ. That got us interested in a QA problem. A test can tell you whether the route you scripted works. Customers get to pick their own route.
How does Wren work?
Give it a goal in plain English, like “a new teammate should be able to accept an invite and join the workspace.”
Wren’s QA agents open your app and try different ways to reach that goal. One might open the invite while signed into the wrong account, switch accounts halfway through, and try the link again. You can test those paths without writing a separate script for each one.
When something breaks, you get a recording and the steps to reproduce it. You can run Wren alongside your existing tests in CI.
Who’s it for?
We built Wren for engineering and QA teams, from startups shipping new features every week to enterprise teams with years of test coverage. One early team told us Wren saved them days of QA before a release.
Try it on something you already test
Your first 10 runs are free. I’d start with a flow your team already has a passing test for. Did Wren catch something your suite missed? I’d love to hear what happened. We’ll be here all day.
Writing tests in plain English and letting the agents find their own way through the app is such a good shift. It caught a confirmation that only showed up below the fold after loading, something my unit tests would never flag. The replays make it easy to see exactly what happened. Congrats on the launch!
testing the messy checkout paths is where the real bugs are. congrats on the launch!
@tom_charman How does Wren deal with unexpected popups , loading delays, or interrupted user journeys ?
the wrong account invite example is a good test of a real onboarding flow
the replay needs to make it clear whether a failure came from the product or from the agent getting stuck operating it
Fun fact: Wren was developed using Wren
\\
\\ (o>
(o> //\
_(()_____V_/_____
|| ||
||
congrats on the launch tom. the invite plus account switch example is a good one, those half finished flows are where real users get stuck and nobody writes a test for them. can wren start from a landing page and follow the whole signup from there?
Epic. This is all i need in my life right now. My team (and I) can't ship anything without missing serious flaws. Godsend.
cool launch!! the hard part is knowing if a weird path it found is a real bug or just something no customer would ever do
About Seldon on Product Hunt
“Behavioral QA agents that use your product like customers do”
Seldon launched on Product Hunt on November 10th, 2026 and earned 129 upvotes and 26 comments, placing #5 on the daily leaderboard. Find the tests you didn’t know to write. Tell Wren what should work in plain English. Its QA agents try the paths your customers take, like going back to change an address halfway through checkout or retrying a failed payment. When something breaks, you get a replay and the steps to reproduce the bug. First 10 runs free.
Seldon was featured in API (98.8k followers), Developer Tools (522.8k followers) and Artificial Intelligence (483.3k followers) on Product Hunt. Together, these topics include over 242.2k products, making this a competitive space to launch in.
Who hunted Seldon?
Seldon was hunted by Tom Charman. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Seldon stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Tom Charman
Hey Product Hunt! I’m Tom, co-founder of Seldon. We built Wren because your entire test suite can pass and a customer can still find a bug five minutes after you ship.
We’re an applied research lab in SF. Our team includes researchers from MIT and Berkeley and people who’ve built products at Meta and Spotify. We put people and agents in front of the same screens and study where their decisions differ. That got us interested in a QA problem. A test can tell you whether the route you scripted works. Customers get to pick their own route.
How does Wren work?
Give it a goal in plain English, like “a new teammate should be able to accept an invite and join the workspace.”
Wren’s QA agents open your app and try different ways to reach that goal. One might open the invite while signed into the wrong account, switch accounts halfway through, and try the link again. You can test those paths without writing a separate script for each one.
When something breaks, you get a recording and the steps to reproduce it. You can run Wren alongside your existing tests in CI.
Who’s it for?
We built Wren for engineering and QA teams, from startups shipping new features every week to enterprise teams with years of test coverage. One early team told us Wren saved them days of QA before a release.
Try it on something you already test
Your first 10 runs are free. I’d start with a flow your team already has a passing test for. Did Wren catch something your suite missed? I’d love to hear what happened. We’ll be here all day.