Open a PR. TryCase uses your app like a real user and sends back a video walkthrough of your changes, plus a test verdict, right on GitHub. See what happened before you merge, with multiple PRs tested in parallel.
While working on another project, testing became my bottleneck. I often have a few coding agents working in parallel across different worktrees, so several branches can be ready to test at once.
I've tried having the agents test locally too. But with several apps and browsers running, ports started colliding and my laptop ran out of memory. I kept ending up back where I started, checking branches one at a time.
That's why I built TryCase. I wanted to open a PR and get proof that the changes actually worked, without having to start another agent, manage an environment, or keep checking on it.
Our first version gave coding agents disposable environments. A lot of the feedback from that launch was simpler: people just wanted to open a PR and get a verdict. So this version has its own testing agent and handles that workflow for you.
TryCase reads your PR, opens the app, and tests it like a user would. It sends a video walkthrough, verdict, and screenshot back to GitHub. Each PR gets its own environment, so multiple PRs can be tested at once. You can also watch the agent live and interact with the remote desktop yourself.
Code review is still useful, but sometimes I need to see what happens when someone actually clicks through the app. That's the gap I'm trying to fill.
I'm looking for beta users, and I'm opening this up to the first 100 people for now. I want to stay close to the feedback and focus on making each verification reliable before opening it up more widely. The Visit link already includes a waitlist invite code, so you can join directly through it.
If you run into any issues, email me at [email protected] and I'll jump on it. If you're on a paid plan and hit a platform issue, I'll also add extra testing hours to your account.
Thanks for trying it early and helping me make it better. I'd love to hear how you're handling testing when several coding agents are working at once.
video proof on a PR instead of a green checkmark is such a usefull idea 🎥 nice one
congrats on the relaunch, Ben. the "watch instead of review" framing clicks for me - that's basically what CI status checks were supposed to be but never actually showed you. capping it at the first 100 beta users seems smart given you're still tuning reliability per-verdict. curious how you're pricing the testing hours once it's past the free-credits stage - per PR, per minute of agent time, or a flat monthly tier?
Would love to try this Ben, but interested in what the requirements / limitations are for TryCase to be able to run a PR. Are there specific frameworks / stacks that you're targeting out of the gate?
Ben, the number of times I've waved through a tiny change without clicking around, and of course it's the small one that breaks. A quick video and a plain yes or no sitting there waiting for me sounds like a relief. Neat one.
ha, the idea of getting a video walkthrough right on GitHub kicks me out of my “i’ll check this later” habit. i usually procrastinate on reviewing PRs, but with this, i'd probably just binge-watch them while ignoring my other tasks.
About TryCase on Product Hunt
“AI tests your PRs. Get a video walkthrough before you merge.”
TryCase launched on Product Hunt on September 14th, 2026 and earned 103 upvotes and 10 comments, placing #13 on the daily leaderboard. Open a PR. TryCase uses your app like a real user and sends back a video walkthrough of your changes, plus a test verdict, right on GitHub. See what happened before you merge, with multiple PRs tested in parallel.
TryCase was featured in Developer Tools (519.7k followers), Artificial Intelligence (478.9k followers) and GitHub (41.4k followers) on Product Hunt. Together, these topics include over 235.7k products, making this a competitive space to launch in.
Who hunted TryCase?
TryCase was hunted by Ben Chomsang. 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 TryCase stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Ben Chomsang
Hey everyone, Ben here.
While working on another project, testing became my bottleneck. I often have a few coding agents working in parallel across different worktrees, so several branches can be ready to test at once.
I've tried having the agents test locally too. But with several apps and browsers running, ports started colliding and my laptop ran out of memory. I kept ending up back where I started, checking branches one at a time.
That's why I built TryCase. I wanted to open a PR and get proof that the changes actually worked, without having to start another agent, manage an environment, or keep checking on it.
Our first version gave coding agents disposable environments. A lot of the feedback from that launch was simpler: people just wanted to open a PR and get a verdict. So this version has its own testing agent and handles that workflow for you.
TryCase reads your PR, opens the app, and tests it like a user would. It sends a video walkthrough, verdict, and screenshot back to GitHub. Each PR gets its own environment, so multiple PRs can be tested at once. You can also watch the agent live and interact with the remote desktop yourself.
Code review is still useful, but sometimes I need to see what happens when someone actually clicks through the app. That's the gap I'm trying to fill.
I'm looking for beta users, and I'm opening this up to the first 100 people for now. I want to stay close to the feedback and focus on making each verification reliable before opening it up more widely. The Visit link already includes a waitlist invite code, so you can join directly through it.
If you run into any issues, email me at [email protected] and I'll jump on it. If you're on a paid plan and hit a platform issue, I'll also add extra testing hours to your account.
Thanks for trying it early and helping me make it better. I'd love to hear how you're handling testing when several coding agents are working at once.