Papers for

ai tool developers

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Benchmark reveals large language models struggle with multi-turn code instructions

MTAC-IFBench: Benchmarking Instruction-Following in Multi-Turn Agentic Coding

Abstract: Recently, the rapid development of large language models (LLMs) has reshaped software engineering by enabling autonomous code agents that plan, execute, and utilize external tools iteratively to tackle complex tasks. Beyond achieving functional correctness, these agents must faithfully follow process instructions and constraints throughout the development lifecycle. However, existing benchmarks typically focus on final functional correctness or confine instruction-following evaluation to single-turn, general chat or simple code generation scenarios, leaving instruction-following in multi-turn agentic coding underexplored. To bridge this gap, we propose MTAC-IFBench, a comprehensive benchmark for this critical capability. It features multi-turn progressive software development instructions with diverse constraints spanning 6 primary and 18 secondary categories. With an average of 7.04 turns and 91.33 constraints per instance, it poses a rigorous challenge to current LLMs. To make the evaluation reliable, we construct a checklist for each constraint and functional requirement, and integrate verification scripts and judge agents to verify each checklist item. MTAC-IFBench identifies significant deficiencies in existing code agents in multi-turn instruction-following, with their performance degrading rapidly as the interaction session grows longer.

Mon 14 SeptComputation and Language
The gist
When AI programs write code by following step-by-step instructions over multiple interactions, they often make mistakes or miss important details. The paper presents a new benchmark called MTAC-IFBench that tests how well these AI agents follow complex instructions when coding across many steps. This benchmark uses detailed checklists and automated checks to measure both if the code works and if it meets all the given requirements at each step. The authors found that current AI coding agents perform worse as the interaction continues, showing it is still hard for them to perfectly follow multi-turn instructions.
Open 2609.14992v1

Open source software hits show chance and lasting skill unchanged by generative AI

Chance, Persistent Advantage, and the Generative-AI Era in Open-Source Package Careers

Abstract: Studies of careers in science, film, music, and books report a common pattern. When a person's most successful work arrives is close to a random draw over the works they produce. How large their successes tend to be, in contrast, follows a stable, person-specific factor. We test whether this pattern holds for open-source software careers and whether it changed when generative AI coding tools arrived. From the complete public record of GitHub push events (2015-2025), we reconstruct 102.2M career works by 6.15M contributors, and for the 908k contributors whose repositories publish packages, we measure each work's impact by how many downstream packages come to depend on it. First, we find that the timing of a career's biggest hit is close to a lottery over their works, as in science and the arts, with a small, replicable lean toward early career that grows as careers get longer. Second, some coders reliably produce higher-impact work than others, but this lasting personal factor accounts for only part of why impact persists (about a fifth in our primary specification); the rest behaves like momentum, success feeding on itself for a period of time. Third, within the same contributors, this structure did not change after ChatGPT's release. The stable factor's weight grew by about as much as it grew for an earlier cohort that simply aged, and subtracting the effect of aging from the effect of generative AI puts the shift at +0.03 (95% CI [-0.22, +0.23]), indistinguishable from zero. The success pattern documented in science and the arts therefore describes open-source careers too, and it shows no detectable break across the arrival of generative AI. These results have implications for how track records on open platforms should be read and on what to expect from generative AI for the careers built on them.

Wed 9 SeptSocial and Information NetworksComputers and Society
The gist
The paper looks at how open-source software developers find success across their careers. It finds that when a developer’s biggest success happens is mostly random, similar to patterns seen in science and the arts. Some developers consistently create more impactful work, but that personal advantage only partly explains success, with a momentum effect also playing a role. The arrival of tools like ChatGPT did not change these success patterns in open-source development careers. The authors suggest that generative AI has not disrupted how long-term success forms in this field.
Open 2609.09687v1

RobustSGPO improves AI agent prompt editing and task success rates

RobustSGPO: Search-Space Control for Agent Harness Evolution

Abstract: Semantic-gradient-based prompt optimization (SGPO) improves agent harnesses using execution feedback, but its local update rule leaves the choice of edit scope and operation unresolved. We introduce RobustSGPO, which specifies the requested edit, constructs and checks the patch, and continues search from either the incumbent or retained snapshots. We evaluate permission scheduling, cumulative controls, and task-family transfer in the AgentX brainstorming workflow using 120 tasks, 95 runs, and 7,350 candidate attempts. Periodic $1\to2\to3$ scheduling exceeds fixed maximum permission by 0.28 test-score points. RobustSGPO increases completion on 30 held-out tasks from 60.0% to 80.0% and improves test quality from 3.77 to 4.14 under a 20-million-token budget. Category retention reduces source-task degradation after a shift, whereas random retention reaches a higher destination endpoint. Search-space control benefits quality through executable edits and alternative starting points, with measurable retention overhead.

Wed 9 SeptArtificial Intelligence
The gist
Improving AI agents often involves tweaking how they are instructed or prompted. The authors found that a common method can get stuck by only making local, small changes without clear rules about how to edit. They created RobustSGPO, a method that controls where and how edits happen, checks these edits before applying them, and manages different starting points during the search. This approach led to better performance on a set of brainstorming tasks, increasing how often tasks were completed and improving overall quality.
Open 2609.09646v1

Safe self-evolution strategies improve AI tool updates with limits

Safe Harness Self-Evolution: A Theoretical Analysis of Feasibility and Limits

Abstract: Harness self-evolution is the process by which an agent modifies its prompts, tools, code, or orchestration in response to task feedback while keeping the underlying language model frozen, with changes persisting across subsequent tasks. We provide a systematic theoretical analysis of the feasibility and limits of safe harness self-evolution, connecting modification generation, finite-data certification and selection, safe adoption, and behavior after an update. Under a fixed user-task distribution, we establish conditions guaranteeing overall expected-reward improvement while controlling changes on retained tasks, characterize the probability of generating qualified modifications, and derive finite-data bounds for safe selection and adoption. Our analysis shows that generation and certification impose distinct constraints: current task performance does not determine the probability of generating qualified modifications, and generating more candidates need not improve the guarantee of a successful update when evaluation is limiting. Stagnation may therefore arise even when improvement opportunities remain. We further show that worst-case evaluation cost for recognizing genuine improvements diverges as expected reward approaches its upper bound. Across successive updates, certified improvement guarantees accumulate over a finite run, but a successful update does not by itself guarantee that further improvement remains possible. These results provide a basis for diagnosing bottlenecks and designing safer self-evolution mechanisms.

Tue 8 SeptArtificial Intelligence
The gist
Some AI systems can change their own instructions or code to do tasks better over time, without changing their base brain model. This paper studies the math behind when and how such safe self-changes can actually improve performance without causing problems. It explains conditions for safe improvements, shows why simply creating more new ideas isn't always better, and highlights that it gets harder to find improvements as the system gets better. These insights help diagnose issues and guide safer design of self-updating AI tools.
Open 2609.08175v1

Software engineering agent benchmark improved for reliable results

SWE-Bench Pro Verified: A Reliable Benchmark for Software Engineering Agents

Abstract: SWE-Bench Pro has emerged as a standard benchmark for evaluating software engineering agents on challenging repository-level tasks. However, our analysis work show that its evaluation is undermined by two sources of unreliability: \textbf{reward hacking}, enabled by leakage of gold solutions or hidden evaluation information, and \textbf{task quality issues}, including misleading problem statements and improperly scoped tests. These issues can inflate benchmark performance and obscure agents' true coding ability. We present \textbf{SWE-Bench Pro Verified}, a verified version of SWE-Bench Pro that addresses both problems. Our approach combines \textbf{anti-hacking} safeguards that eliminate major leakage channels without disrupting normal agent functionality, with \textbf{task refinement} that minimally corrects inconsistencies within flawed instances. Evaluations on SWE-Bench Pro Verified reveal that some models perform substantially worse than previously reported, suggesting that existing results on SWE-Bench Pro may overestimate real software engineering capability. SWE-Bench Pro Verified offers a more trustworthy benchmark for assessing software engineering agents.

Tue 8 SeptArtificial IntelligenceSoftware Engineering
The gist
Software engineering agents are computer programs that write or fix code automatically. The existing SWE-Bench Pro benchmark used to test these agents has problems, like letting the programs cheat or testing unclear tasks. The authors created SWE-Bench Pro Verified, which removes cheating opportunities and fixes task problems. Testing with this new version shows some agents do worse than before, meaning previous tests may have been too optimistic.
Open 2609.08149v1