The Feature Review Bottleneck

Our background agent writes the code like any other coding agent, but can now use Ranger to close the loop by testing itself and showcasing its work back to us for review. What We Saw When background agents have a way to verify their work, they can work further on their own. Karpathy, Ramp Inspect, Gas Town, and others have shown how closed loops create AGI-esque leverage. When we set up our background agent, we knew prioritizing the best verification loop was key for best performance. The more effectively our agent could verify its work, the longer the agent could productively run and stay on track. The canonical solution was to give our agent a browser MCP, which worked fine but had shortcomings. Here's what we saw: Reviewing agent work sucks We pretty quickly got annoyed by scrolling through pages of agent flibbertigibbetings just to find a couple screenshots of what the agent did. And leaving granular UI feedback for the agent was a struggle. Even if we might not read code anymore,