← Latest papers
🤖 AI

Open-SWE-Traces: Advancing Dual-Mode Multilingual Distillation for Software Engineering Agents

This paper introduces Open-SWE-Traces, a large-scale, multilingual dataset of 207,489 software engineering agent trajectories derived from real-world pull requests, which enables the distillation of high-performing, open-source models capable of achieving state-of-the-art results on diverse SWE-bench evaluations.

Original authors: Wasi Uddin Ahmad, Nikolai Ludwig, Somshubra Majumdar, Boris Ginsburg

Published 2026-06-16
📖 5 min read🧠 Deep dive

Original authors: Wasi Uddin Ahmad, Nikolai Ludwig, Somshubra Majumdar, Boris Ginsburg

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you want to teach a robot how to fix broken code in a massive library of software. The problem is, you can't just tell the robot what to fix; you need to show it how to think through the problem, make mistakes, try again, and eventually succeed. Until now, there hasn't been enough "footage" of this process to teach robots well, especially for many different programming languages.

This paper introduces OPEN-SWE-TRACES, a massive new library of "footage" designed to teach AI agents how to be software engineers.

Here is a breakdown of what they did, using simple analogies:

1. The Problem: A Lack of "Training Videos"

Think of software engineering as a complex sport. To train a new player (an AI), you need to watch thousands of hours of professional games to learn the moves.

  • The Bottleneck: Previously, researchers only had a few hours of "game tape." They didn't have enough diverse examples of how to fix bugs in different languages (like Python, Java, or C++) to train a truly smart AI.
  • The Solution: The authors created OPEN-SWE-TRACES, a dataset containing 207,489 recorded "games." These are real-world scenarios where an AI tried to fix a bug in a real software project.

2. The Training Method: Two Modes of Thinking

The paper introduces a clever way to teach the AI, inspired by how humans work. They call this "Dual-Mode Distillation."

  • Mode A: The "Thinker" (Slow & Careful)
    Imagine a chess grandmaster who pauses to calculate every possible move before touching a piece. The dataset includes traces where the AI explicitly "thinks out loud" (Chain-of-Thought) before acting.
    • The Magic: The paper found that when the AI takes time to think, it actually makes fewer total moves to solve a problem. It's like taking a moment to plan a route so you don't get lost and have to walk in circles. This saves time and effort in the long run.
  • Mode B: The "Doer" (Fast & Direct)
    Imagine a mechanic who sees a loose bolt and immediately tightens it without a long speech. The dataset also includes traces where the AI acts quickly without the internal monologue.
    • The Goal: The AI learns to switch between these modes: "Think" for hard problems, and "Do" for simple ones.

3. How They Built the Dataset

They didn't just make up fake problems. They went to the real world:

  • The Source: They looked at 20,000 real Pull Requests (actual code changes submitted by humans) from open-source projects.
  • The Actors: They used two powerful AI "coaches" (MiniMax-M2.5 and Qwen3.5) to watch these real problems and simulate how an agent would solve them.
  • The Safety Check: Before adding a recording to the library, they ran a strict security filter. They made sure the AI didn't "cheat" by peeking at the answer key (hacking the git history) or breaking the rules. If the AI tried to cheat, that recording was thrown away.

4. The Results: A New Champion

After feeding this massive library of "footage" to a student AI (based on the Qwen3-30B model), they tested it on three famous "exams" (benchmarks) that measure how well an AI can fix real bugs:

  • SWE-bench Verified: The student got 61.7% of the problems right.
  • SWE-bench Multilingual: The student got 57.1% right across many different languages.
  • SWE-bench Pro: The student got 36.8% right on very difficult, professional-level tasks.

Why is this a big deal?
The paper compares this new student to other top-tier AI models. The new model, trained on this specific dataset, outperformed many other open-source models and came very close to some of the most expensive, "closed-source" super-intelligences.

5. Key Lessons Learned

The authors ran experiments to see what made the AI smart:

  • Language Matters: Training the AI only on Python was okay, but training it on nine languages (Python, Go, Java, etc.) made it significantly better at solving all types of problems, even the Python ones. It's like learning to drive in rain, snow, and sand makes you a better driver in the city.
  • Failure is Good: They found that including recordings where the AI failed to fix the bug was actually helpful. It taught the AI what not to do. If you only show a student the winning plays, they don't learn how to avoid losing.
  • The "Thinking" Trade-off: While "thinking" traces helped the AI solve hard problems, the AI performed slightly better overall when it was allowed to act quickly ("no-think") on standard tasks. The best approach is a mix of both.

Summary

The paper presents a massive, high-quality library of software engineering "replays" that teaches AI agents how to think and act like human developers. By using a mix of "slow thinking" and "fast acting" examples across many programming languages, they created an open-source AI that is now one of the best at fixing real-world software bugs.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →