Keeping the record when an agent run fails
Preserving failed attempts and partial trajectories, then preparing the next step toward batch execution.
Read note : Keeping the record when an agent run failsYousuf Golding
Work notes
Accounts of what I am building, the decisions along the way, and what the results show.
Project · In progress
MP1 · Minimal software-engineering agent
A tutorial-based agent implementation, developed step by step toward a complete SWE-bench evaluation.
Current stage: Recording failed attempts and implementing the batch runner.
View project overview →Recent work notes
Dated entries about individual work sessions.
Scoring the first saved agent patch
Adding a separate evaluation command, preserving distinct failure states, and getting the first resolved result from the SWE-bench harness.
Read note : Scoring the first saved agent patchFinding premature exits in the saved agent traces
Recording individual model messages, guarding against an exit before execution, and checking what a single-task result actually establishes.
Read note : Finding premature exits in the saved agent tracesKeeping the patch and the record of a run
Capturing changes before container cleanup, saving trajectories, and finding a failure in the final summary.
Read note : Keeping the patch and the record of a runMoving run settings into one configuration
Loading configuration once, keeping prompt values consistent with execution, and separating build history from current code.
Read note : Moving run settings into one configurationBuilding the execution environment for my minimal agent
Separating command execution from the agent loop, working through timeouts and cleanup, and checking the single-task runner.
Read note : Building the execution environment for my minimal agent