Is Your Automated Software Engineer Trustworthy?
Not on the map. Why?
Abstract (arXiv)
Large Language Models (LLMs) are being increasingly used in software engineering tasks, with an increased focus on bug report resolution over the past year. However, most proposed systems fail to properly handle uncertain or incorrect inputs and outputs. Existing LLM-based tools and coding agents respond to every issue and generate a patch for every case, even when the input is vague or their own output is incorrect. There are no mechanisms in place to abstain when confidence is low. This leads to unreliable behaviour, such as hallucinated code changes or responses based on vague issue reports. We introduce BouncerBench, a benchmark that evaluates whether LLM-based software agents can refuse to act when inputs are ill-defined or refuse to respond when their own outputs are likely to be incorrect. Unlike prior benchmarks that implicitly incentivize models to generate responses even when uncertain, BouncerBench aims to improve precision by targeting two overlooked failure points: (1) vague or underspecified issue descriptions in tickets and (2) logically or functionally incorrect code patches created by the system. It measures whether proposed systems can distinguish actionable issues from vague tickets and valid patches from untrustworthy ones. We also implement a basic input and output bouncer, evaluating how well current LLMs can abstain when needed. Our results show that most models fail to abstain from underspecified inputs or incorrect outputs. Hence, we conclude that there is significant room for improvement before LLMs can be trusted to make correct decisions and recommendations in real-world software engineering workflows. BouncerBench provides a first step toward evaluating and building more cautious, trustworthy code agents. The replication package, dataset, and leaderboard can be found at bouncerbench.com
Key facts. Cited by 3 papers in the map (data through 14 Oct 2026). First posted on arXiv 21 Jun 2025.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2025: 1; 2026: 2.
3 papers.
- 2025Abstain and Validate: A Dual-LLM Policy for Reducing Noise in Agentic Program Repaircited by 5
- 2026The Partial Testimony of Logs: Evaluation of Language Model Generation under Confounded Model Choicecited by 2
- 2026Don't Start What You Can't Finish: A Counterfactual Audit of Support-State Triage in LLM Agentscited by 0
- 2026The Partial Testimony of Logs: Evaluation of Language Model Generation under Confounded Model Choice2 May 2026
- 2026Don't Start What You Can't Finish: A Counterfactual Audit of Support-State Triage in LLM Agents17 Apr 2026
- 2025Abstain and Validate: A Dual-LLM Policy for Reducing Noise in Agentic Program Repair3 Oct 2025
Similar, not cited
Close in wording, no citation either way
- 2026Bias in the Loop: Auditing LLM-as-a-Judge for Software Engineering
- 2025TREAT: A Code LLMs Trustworthiness / Reliability Evaluation and Testing Framework
- 2025The SWE-Bench Illusion: When State-of-the-Art LLMs Remember Instead of Reason
- 2026When Passing Tests Hides Vulnerabilities: An Empirical Study of Silent Failures in Agentic Systems
- 2025LLM-as-a-Judge for Software Engineering: Literature Review, Vision, and the Road Ahead ↗
- 2024An Empirical Study on LLM-based Agents for Automated Bug Fixing
- 2026GBQA: A Game Benchmark for Evaluating LLMs as Quality Assurance Engineers
- 2026SelfHeal: Empirical Fix Pattern Analysis and Bug Repair in LLM Agents