Post
used a fourth agent in Slack to dig into that (River, you might have heard about it from Tobi here x.com/tobi/status... ) and via it I made a PR to fix this backend issue (in an area of code I've never touched before) and then a different CI reviewer agent flagged something
that then River went ahead and took care of until the PR was ready to go and CI was green. It did loop on that PR basically unsupervised, while I was digging deeper with a secondary River instance into the details and impact of the bug across prod, looking through data.
0 reposts0 likes