Papers › Lingma SWE-GPT: An Open Development-Process-Centric Language Model for Automated...

Lingma SWE-GPT: An Open Development-Process-Centric Language Model for Automated Software Improvement

1 Nov 2024arXiv:2411.00622archive 2025-07-28

Yingwei Ma, Rongyu Cao, Yongchang Cao, Yue Zhang, Jue Chen, Yibo Liu, Yuchen Liu, Binhua Li, Fei Huang, Yongbin Li

Recent advancements in LLM-based agents have led to significant progress in automatic software engineering, particularly in software maintenance and evolution. Despite these encouraging advances, current research faces two major challenges. First, SOTA performance primarily depends on closed-source models, which significantly limits the technology's accessibility, and potential for customization in diverse SE tasks. Second, these models are predominantly trained on static code data, lacking a deep understanding of the dynamic interactions, iterative problem-solving processes, and evolutionary characteristics inherent in software development. To address these challenges, our study adopts a software engineering perspective. We recognize that real-world software maintenance and evolution processes encompass not only static code data but also developers' thought processes, utilization of external tools, and the interaction between different functional personnel. Consequently, we introduce the Lingma SWE-GPT series, comprising Lingma SWE-GPT 7B and 72B. By learning from and simulating real-world code submission activities, Lingma SWE-GPT systematically incorporates the dynamic interactions and iterative problem-solving inherent in software development process, thereby achieving a more comprehensive understanding of software improvement processes. We conducted experimental evaluations using SWE-bench Verified benchmark. The results demonstrate that Lingma SWE-GPT 72B successfully resolves 30.20% of the GitHub issues, marking a significant improvement in automatic issue resolution (22.76% relative improvement compared to Llama 3.1 405B), approaching the performance of closed-source models (31.80% issues of GPT-4o resolved). Notably, Lingma SWE-GPT 7B resolves 18.20% of the issues, highlighting the potential for applying smaller models to ASE tasks.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 12 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 7 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 10 ran (3 with no instrument failure; 7 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

LingmaTongyi/Lingma-SWE-GPT officialSyntology: 12 samples, 10 ran (7 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

12 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 7 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

7ran · our draft was wrong
3ran
2unverified

Licence: 12 of the 12 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from LingmaTongyi/Lingma-SWE-GPT. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

LingmaTongyi/Lingma-SWE-GPT official repository 12 samples, 10 ran (7 instrument-failed) · 2 unverified
add_step_trigger app/inference.py ran fingerprinted no licence file found · pointer only · 4a9d291fd8231065 · report fixture: signature orig_prompt:str/0/str, is_first:bool/0/bool · returned str · level recorded 2026-09-25
count_and_organize_tasks app/post_process.py ran no licence file found · pointer only · 4ba8180b0bea20ec · report fixture: signature task_list:list/1/str, task_list_name:str/0/str, task_exp_names:list/1/str, expr_dir:str/0/str · returned str · level recorded 2026-09-25
create_new_logger app/log.py ran · our draft was wrong no licence file found · pointer only · b80e52761ce47d00 · report fixture: signature task_id:str/0/str, out_dir:str/0/str · returned Logger · level recorded 2026-09-25
extract_gpt_content app/model/gpt.py ran · our draft was wrong no licence file found · pointer only · 62d4bc6ae2e0bf70 · report fixture: signature chat_completion_message:ChatCompletionMessage/0/? · returned str · level recorded 2026-09-25
get_all_py_files app/MCTS/SWEGPT/run_gpt_and_bm25.py ran · our draft was wrong fingerprinted no licence file found · pointer only · fbc78031a9466729 · report fixture: signature dir_path:str/0/str · returned list · level recorded 2026-09-25
get_bm25_score app/MCTS/SWEGPT/run_gpt_and_bm25.py ran no licence file found · pointer only · 52159cbb2c30cfe0 · report fixture: signature issue:str/0/str, code_content:str/0/str, retriever:MockRetriever/0/? · returned int · level recorded 2026-09-25
get_logger in 383 papers app/log.py ran · our draft was wrong no licence file found · pointer only · 48d86997cc5e93eb · report fixture: signature task_id:str/0/str · returned Logger · level recorded 2026-09-25
get_review_result app/inference.py ran · our draft was wrong fingerprinted no licence file found · pointer only · ff5fc9ba9b79f7a5 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-25
prepare_issue_prompt app/inference.py ran · our draft was wrong no licence file found · pointer only · 8509558455ad7ff9 · report fixture: signature problem_stmt:str/0/str · returned str · level recorded 2026-09-25
read_extract_status app/post_process.py ran · our draft was wrong fingerprinted no licence file found · pointer only · da242e87f1c615cd · report fixture: signature individual_expr_dir:str/0/str · returned ExtractStatus · level recorded 2026-09-25
chatswegpt app/model/call_vllm.py unverified no licence file found · pointer only · c27aa88ac8371c88 · report
run_script_in_conda app/utils.py unverified no licence file found · pointer only · 5ab9d3877e545f78 · report

Tasks

Language ModelingLanguage Modelling

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

LLaMA

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections