TryCase

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.

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 ben@trycase.dev 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.