Papers › Can Agents Fix Agent Issues?

Can Agents Fix Agent Issues?

27 May 2025arXiv:2505.20749archive 2025-07-28

Alfin Wijaya Rahardja, Junwei Liu, Weitong Chen, Zhenpeng Chen, Yiling Lou

LLM-based agent systems are emerging as a new software paradigm and have been widely adopted across diverse domains such as medicine, robotics, and programming. However, maintaining these systems requires substantial effort, as they are inevitably prone to bugs and continually evolve to meet changing external requirements. Therefore, automatically resolving agent issues (i.e., bug reports or feature requests) is a crucial and challenging task. While recent software engineering (SE) agents (e.g., SWE-agent) have shown promise in addressing issues in traditional software systems, it remains unclear how effectively they can resolve real-world issues in agent systems, which differ significantly from traditional software. To fill this gap, we first manually analyze 201 real-world agent issues and identify common categories of agent issues. We then spend 500 person-hours constructing AGENTISSUE-BENCH, a reproducible benchmark comprising 50 agent issue resolution tasks (each with an executable environment and failure-triggering tests). We further evaluate state-of-the-art SE agents on AGENTISSUE-BENCH and reveal their limited effectiveness (i.e., with only 3.33% - 12.67% resolution rates). These results underscore the unique challenges of maintaining agent systems compared to traditional software, highlighting the need for further research to develop advanced SE agents for resolving agent issues. Data and code are available at https://alfin06.github.io/AgentIssue-Bench-Leaderboard/#/ .

PaperPDFCode 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; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: found in paper text by Syntology: 12 samples from 1 repository, 10 ran (10 with no instrument failure; 0 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.

No sample is linked to this paper from 3 of its repositories that Syntology harvested for other papers:

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

camel-ai/camel found in paper text by SyntologySyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Society (arXiv:2303.17760; that paper's own run record: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
OpenBMB/ChatDev found in paper text by SyntologyApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to ChatDev: Communicative Agents for Software Development (arXiv:2307.07924; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified) and ChatDev 2.0: A No-Code Multi-Agent Platform for Developing Everything (arXiv:2609.00714; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
alfin06/AgentIssue-Bench found in paper text by SyntologyMITSyntology: 12 samples, 10 ran (0 instrument-failed) · 2 unverified report
assafelovic/gpt-researcher found in paper text by SyntologySyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks (arXiv:2005.11401; that paper's own run record: 6 ran (of which 3 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
crewAIInc/crewAI found in paper text by SyntologyMITSyntology: not harvested 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

12 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 0 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 has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

10ran
2unverified

Licence: 0 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 alfin06/AgentIssue-Bench. “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.

alfin06/AgentIssue-Bench found in paper text by Syntology 12 samples, 10 ran (0 instrument-failed) · 2 unverified
construct_query find_issue.py ran MIT (permissive) · 33f7107666e83053 · report fixture: signature agent_terms:list/1/str, issue_terms:list/1/str, repro_terms:list/1/str, base_qualifiers:str/0/str · returned str · level recorded 2026-09-25
count_operators find_issue.py ran fingerprinted MIT (permissive) · 7cf77ecead2642e7 · report fixture: signature term_lists:list/1/list · returned int · level recorded 2026-09-25
get_args in 84 papers SWE-agent/run_replay.py ran MIT (permissive) · c8ced7040ad99966 · report fixture: signature args:list/1/str · returned tuple · level recorded 2026-09-25
get_repo_url_and_commit_from_pr reproduce.py ran MIT (permissive) · a15d6b4d596bc4f8 · report fixture: signature pr_url:str/0/str, headers:dict/0/? · returned tuple · level recorded 2026-09-25
run_flake8_check Agentless/evaluate_patches.py ran MIT (permissive) · 279a8b96670e1f2a · report fixture: signature project_path:str/0/str · returned bool · level recorded 2026-09-25
run_import_check Agentless/evaluate_patches.py ran fingerprinted MIT (permissive) · a25590a6367280a3 · report fixture: signature project_path:str/0/str, edited_files:list/1/str · returned bool · level recorded 2026-09-25
run_reproduce_script auto-code-rover/evaluate_patches.py ran MIT (permissive) · 4d2e689b4a2777c6 · report fixture: signature repo_path:PosixPath/0/? · returned bool · level recorded 2026-09-25
run_static_check Agentless/evaluate_patches.py ran MIT (permissive) · 43162bab71a2c080 · report fixture: signature project_path:str/0/str · returned bool · level recorded 2026-09-25
save_repo_state auto-code-rover/evaluate_patches.py ran MIT (permissive) · 22478d4ac43df6b0 · report fixture: signature repo_path:PosixPath/0/? · returned PosixPath · level recorded 2026-09-25
scrape_pr_urls_from_issue_page find_issue.py ran MIT (permissive) · a59d0d41024846fd · report fixture: signature issue_html_url:str/0/str, request_headers:dict/0/? · returned list · level recorded 2026-09-25
apply_patch_and_check auto-code-rover/evaluate_patches.py unverified MIT (permissive) · b79d0cde035fc0b6 · report
setup_workspace reproduce.py unverified MIT (permissive) · 1860f525c15bb57e · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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