What SWE-bench and similar benchmarks measure. How coding agents plan and repair a change across a whole repository. What a team needs before it can trust the result in production code.
A coding agent on a laptop stops when the lid closes or the plan's usage limit hits. Oxagen runs it in a sandbox on your Modal account, with every linked repository and a terminal that pauses it.
A key saved once serves every organization you work in. A run moves to your next saved login when one runs out, and a refused login asks for a new sign-in on your own machine.
Oxagen now drafts steering from what people correct mid-run, reads refusals and failing tools across runs each night, and serves steering only to the agents it wraps.
An agent can write a change in minutes. Then the change waits for a person to read it. This post measures that wait, what eight companies changed about it, and how Oxagen ships at every hour.
A coding agent changed your code and no one can replay how. What the research says about feedback from running code, random sampling, and turns you can audit.
Coding agents are ranked by their SWE-bench resolve rate. This post covers what that rate shows, where test-based grading goes wrong, and what the rate cannot tell you.
AgentBench, WebArena, GAIA, SWE-bench, and tau-bench each measure a different thing. None of them reports what a run costs. This post covers what that hides.
