Skip to main content
Search

# SWE-bench Verified

12 related articles

Subscribe to updates
  1. LMSYS Org

    RadixArk moves Miles agentic RL sandboxes onto NVIDIA Vera CPUs, cutting episode time 12% under full load

    RadixArk, working with NVIDIA, ran every sandbox of its open-source RL post-training framework Miles on NVIDIA Vera CPUs, which it calls the first public result of end-to-end agentic RL training with all sandboxes on Vera CPU servers. In a comparison that first kept the machines busy, with the same model, tasks, GPUs and settings, episodes with sandboxes on Turin took 12% longer on average, while model thinking time was identical, so nearly all of the gap came from work inside the sandbox. With a single sandbox running, Vera performs on par with or better than current x86, and its lead grows with load.

  2. arXiv

    Delivered memory is not used memory: MemUse traces each delivery and finds most entries irrelevant and most relevant ones ignored

    MemUse moves the unit of evaluation from the task outcome to the individual memory delivery: across 8,000 SWE-bench Verified agent episodes, three memory systems stayed within 0.4 percentage points of a no-memory baseline on resolve rate, yet per-delivery judgments show most delivered entries were irrelevant, 51.3%–79.7% of relevant entries went unused in each system, and 23.2% of episodes with beneficial memory use still failed.

  3. LMSYS Org

    Software-engineering agents stop waiting for the slowest rollout: async RL lifts pass@1 from 7.3% to 27.5%

    On AMD Instinct MI355X, Qwen3-30B-A3B-Instruct trained with fully asynchronous agentic RL after supervised fine-tuning raised pass@1 from 7.3% to 27.5% on a 100-task stratified subset of SWE-bench Verified, with RL tasks drawn from repositories absent from that benchmark. The bottlenecks were long-tail trajectories and CPU sandbox scheduling rather than GPU compute: capping trajectory length cut step time from 850 s to 284 s, and cloud sandboxes at 384 concurrent trajectories lifted rollout throughput from about 860 to about 3,480 trajectories per hour.

  4. arXiv

    Software agents no longer get only pass or fail: the policy itself ranks debugging traces within the same outcome

    Reinforcement learning rewards for software engineering agents no longer stop at pass or fail: the current policy compares debugging traces from the same task and verifier outcome, turning those preferences into bounded auxiliary rewards and lifting Qwen3-14B average accuracy on SWE-bench Verified from 32.1% to 34.7%.

  5. arXiv

    Agents stop guessing when to ask for help: ARIA picks consultation points and recovers 68% of the gap on SWE-bench at under half the cost

    ARIA turns when to consult a stronger model into a learned sequential decision: across SWE-bench Verified, Terminal-Bench 2.1 and a telecom customer-service benchmark it recovers 44–81% of the executor–advisor success gap at less than half the Advisor-only cost.

  6. arXiv

    Passing tests is not enough: structural scoring picks 1,024 agent trajectories and lifts SWE-Bench Verified pass@1 to 27.6%

    Supervised fine-tuning of coding agents no longer has to select only on whether the final patch passes the test suite: ranking trajectories by structure and keeping the top 1,024 raised pass@1 on SWE-Bench Verified from 24.8% for a random subset to 27.6%.

  7. arXiv

    Rejected patches stop being wasted: failure feedback enters training, lifting SWE-bench first-attempt resolution from 38.9% to 41.7%

    Repository-level software engineering agents previously treated each attempt's pass or fail as a terminal reward, discarding the failed patch and verifier feedback. FC-SWE restores the repository to its original task state after a patch fails verification, uses the failed patch and verifier diagnostics as context for a recovery trajectory, keeps each trajectory's own verifier outcome, and compares only the initial and recovery trajectories actually executed for the same issue. On all 500 SWE-bench Verified tasks with the same Qwen3.5-4B policy, first-attempt resolution rises from GRPO's 38.9% to 41.7% and two-attempt cumulative resolution from 48.5% to 52.8%; trained with at most two attempts per chain, the same policy reaches 70.7% with eleven test-time attempts.

  8. Microsoft Research Asia open-sources Agent Lightning v1.0: Harnessed Agentic RL in about 3,500 lines lifts Qwen3.5-9B from 41.8% to 56.4% on SWE-bench Verified

    Microsoft Research Asia introduces the Harnessed Agentic RL paradigm and open-sources a rebuilt Agent Lightning v1.0, in which the same agent harness used in deployment participates directly in reinforcement learning through an LLM proxy; the framework is about 3,500 lines of code, runs agents as standard Kubernetes jobs, and on an end-to-end coding agent pipeline built on SWE-smith, mini-SWE-agent, and Qwen3.5-9B, roughly 6,000 training samples raise Pass@1 on SWE-bench Verified from 41.8% to 56.4%, an absolute gain of 14.6 percentage points.

  9. arXiv

    DeReAct externalizes action validation and completion certification, lifting Pass@1 by 6.5–7.0 points for Qwen3-Coder-480B on GAIA and SWE-bench Verified

    DeReAct introduces a modular agent architecture that separates action authorization and completion control from a single LLM policy, delegating them to a Critic that validates proposed actions before execution and a Context Manager that reconstructs an environment-supported State and certifies task completion; across GAIA and SWE-bench Verified it improves Pass@1 most for weaker Brain models (6.5–7.0 points for Qwen3-Coder-480B and 4.2–5.2 points for Claude Sonnet 4.5), with gains diminishing as Brain capability increases, while on Claude Opus 4.5 Pass@1 remains comparable to ReAct but trajectories are more evidence-complete and constraint-satisfying.

  10. NVIDIA proposes a tool-call-centric agent evaluation framework and uses a SWE-bench trace to show how end-to-end and step-level scoring divide the work

    This NVIDIA article traces how agent evaluation moved from scoring a single function call to scoring whole-task completion, proposes a framework built on an execution environment, two scoring layers (step-level process and end-to-end outcome), and a fixed Benchmark to Trial to Task to Turn to Step hierarchy, and uses a real SWE-bench Verified trace for pytest-dev__pytest-5262 (E2E score 1, step-level 3/4, tool-call precision 3/4, argument accuracy 4/4) to show how each metric should be read, alongside a workflow of setting a public floor and building domain evals from your own tickets and APIs.