What is your cutoff for killing a bad Codex run?
<p>One thing I’m still trying to reason about with Codex is when a run should be stopped rather than allowed to keep spending context, steps, and time.</p> <p>Some failures are obvious: repeated test failures, the same edit being attempted multiple times, or the agent circling around the same error message.</p> <p>But the harder cases are more subtle:</p> <p>A run looks like it is making progress, but the diff keeps growing in the wrong direction.</p> <p>It keeps adding abstractions instead of f







