Termination Lag: Coding Agents Solve Early but Stop Late
Musa Cim, Burak Topcu, Mahmut Taylan Kandemir
Termination Lag: Coding Agents Solve Early but Stop Late: 7 upvotes on Hugging Face Daily Papers, #16 of 42 papers on 2026-11-17. Day-by-day upvote history.
Upvotes over time
It had 5 upvotes by its first day, 6 upvotes by the next day, 7 upvotes by day 3, 7 upvotes by day 7, and has 7 now. It ranked #61 of 146 papers in its week and #283 of 520 in its month.
Coding agents can solve a task well before they stop working on it. We characterize termination lag--the number of steps between an agent's first correct patch and the end of its run--across five models, two agent frameworks, and three SWE-bench datasets by recording and testing every distinct repository patch generated during execution. Our analysis reveals that 38--82% of successful runs achieve a correct solution on their initial source-code edit. However, agents continue to expend substantial effort after correct patches, with post-solution steps accounting for a median of 35--37% for Qwen3-Coder and 54--60% for Laguna-XS.2 in successful runs on SWE-bench Verified and Multilingual. Agents spend most of these additional steps verifying their work and exploring the repository. In a small fraction of cases (1--8%), this continued activity leads agents to undo their earlier correct patch, leaving the final solution incorrect.
Paper page on Hugging Face · arXiv
Data: hysts-bot-data/daily-papers-stats and the Daily Papers API. Open data: tardellirs/paper-pulse-data. Sister project: Model Pulse, the download history of every model on the Hub.