Been following this maker across two launches now (the original disposable-environments version and now this PR-testing follow-up). What I like about this second version is that it's actually solving the exact bottleneck the maker described in the first launch's comments - reviewing a PR still means clicking through the app yourself to see if it actually works. Getting a video walkthrough and verdict posted right on GitHub means you don't have to context-switch into a separate environment to check. It's still early beta (first 100 users, waitlist invite code), so I'm rating it for the idea and execution I've seen in the thread rather than months of daily use.
TryCase
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.
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?
TryCase
@steve_croce Hi Steve, TryCase currently supports anything that runs on Linux. I've tried it with several web apps, desktop apps, CLI applications, and anything in Docker. We have a setup agent that figures out how to run your repo initially, so it should be quite flexible. I'm giving everyone 1 hour free for this initial setup, so you should be able to find out pretty quickly if your repo is compatible or not.
In the future I'm hoping to support macOS (my personal pain is testing iOS apps), but Macs in the cloud are still quite expensive.
If you manage to try it out, let me know how it goes :)
Macaly
video proof on a PR instead of a green checkmark is such a usefull idea 🎥 nice 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.
TryCase
@therayess I think this is the goal. I want to just 'watch' my PRs rather than reviewing them. Ofc for serious work we are still quite far away from that but I think this is one step closer.
TryCase
@therayess curious if to see what you think if you've tried it. I've added free credits for people to try. it's not perfect but I'm keen to learn what would be useful.
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.
TryCase
@robin_de_lacroix yes absolutely. Would love to hear your thoughts if you get a chance to try it.
Dial
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?