Skip to content

Conversation

@njukenanli
Copy link
Collaborator

No description provided.

@njukenanli njukenanli merged commit 91dd8ef into microsoft:main Dec 4, 2025
1 check passed
@danielzayas
Copy link

Whoa! Big change! I thought that RepoLaunch was the core innovation of SWE-bench-Live, so I'm confused about moving it to a new project at https://github.com/microsoft/RepoLaunch. Does this mean that the SWE-bench-Live project will be sunsetted and no longer maintained @njukenanli ? I ask because my fork is affected https://github.com/danielzayas/SWE-bench-Live

@njukenanli
Copy link
Collaborator Author

Hi Daniel!

Thank you so much for your continued interest in our project and enthusiastic contributions!

We make RepoLaunch a separate project because we think that the utility and impact of RepoLaunch has moved beyond providing instances for SWE-bench-Live. RepoLaunch is now a generalized tool to automate the build and test pipeline of code repositories.

SWE-bench-Live project would continue to be maintained and developed. The SWE-bench-Live project would be seen as a pure project for creating SWE tasks for the benchmarking of LLMs and coding agents, and also providing training instances for the SFT and RL of coding LLMs, such as Training Long-Context, Multi-Turn Software Engineering Agents with Reinforcement Learning. We would continue to update SWE-tasks on Python, and multi-language, and Windows specific bug in the long term, and would continue to test new versions of LLMs (GPT, Claude, Gemini... when we have more budgets) inside SWE-bench-Live project. We welcome any new research project thinking about how to use RepoLaunch to create other kinds of SWE tasks, as SWE-bench-Live simply scrapes issues and PRs as SWE tasks.

We acknowledge sincerely for your generous contributions to our project with these PRs. But could you please move the PRs related to the launch folder to RepoLaunch ? I apologize so much for making such inconvenience.

So for open-source contributors, from now on the issues and PRs to the curation (scraping from GitHub) and evaluation&validation should be inside SWE-bench-Live; while those to the RepoLaunch Agent should be committed to RepoLaunch.

Yours sincerely,
Kenan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants