Original Summary

I've been using coding agents a lot recently, and after setting up a dedicated machine to run them remotely, I started sending my colleagues way too many PRs. Understandably, they weren't quite as excited about that as I was. I wanted to make reviewing them less work. Having agents attach browser recordings helped, and people liked them, but getting the agents to run through everything and record it took ages on my machine and burned loads of tokens. So I built Diff Stage. Obviously, I've now spent far more tokens building it than I'll ever save. It records browser tests in GitHub Actions and puts a link in your PR. Reviewers can watch the test running on your branch beside the same test on main, so they can see how the behaviour changed. It's heavily designed around agents, so realistically when you push your agents are requesting which tests will be recorded to provide the best evidence for your PR. It currently works with Laravel and Pest. But even if you use something else, I'm curious whether you've had the same problem. Has writing code faster just moved the bottleneck onto whoever reviews it? What helps your team? Here's a short demo, and the app is at https://diffstage.com if you want a look.   submitted by   /u/wardy484 [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/14 10:40:11