Schr"odinger's Code Repository: Have LLMs Learned SWE-bench or Memorized It?
cs.SE, cs.AI
Submitted: 2026-08-21
Updated: 2026-08-21
Comments: Our code and data are available at https://github.com/cslsolow/Schrodinger-Repo
Code: https://github.com/cslsolow/Schrodinger-Repo
License: http://creativecommons.org/licenses/by/4.0/
The gist: Repository-level coding benchmarks have become the standard for evaluating coding agents, yet they inherently suffer from data leakage because they are built upon popular open-source repositories
Terminology
Abstract
Repository-level coding benchmarks have become the standard for evaluating coding agents, yet they inherently suffer from data leakage because they are built upon popular open-source repositories repeatedly used for training. Consequently, strong performance may reflect memorization of canonical repository cues rather than robust repository reasoning. We propose SchrodingerRepo (Schrödinger's Repository), an evaluation framework for testing coding agents under dynamically instantiated repository representations. Instead of repeatedly using a static representation of the test repository, SchrodingerRepo treats the test repository as an evaluation-time latent variable that is dynamically instantiated only when the agent enters the evaluation environment. The instantiated repository preserves the original executable behavior while eroding familiar cues such as naming conventions, file layouts, and implementation patterns through four transformation levels: problem statement reconstruction, namespace remapping, intra-file layout reordering, and functionality-preserving code rewriting. We evaluate popular LLMs on SWE-bench Verified and SWE-QA. Results show that removing familiar repository cues consistently degrades agent performance and substantially increases interaction costs across models. Further analysis reveals that the additional cost is primarily caused by increased difficulty in repository exploration and localization. These findings suggest that current coding agents may partially rely on memorized repository-side cues, highlighting the need for evaluation under dynamically instantiated repository representations.
Sources
- Pruning the Unsurprising: Efficient LLM Reasoning via First-Token Surprisal
- Dockerless: Environment-Free Program Verifier for Coding Agents
- SWE-MeM: Learning Adaptive Memory Management for Long-Horizon Coding Agents
- Test vs Mutant: Adversarial LLM Agents for Robust Unit Test Generation
- Know Before Fix: QA-Driven Repository Knowledge Acquisition for Software Issue Resolution
- Rethinking the Value of Agent-Generated Tests for LLM-Based Software Engineering Agents
- LLM Agents Can See Code Repositories
- SWE-bench Goes Live!
- SWE-rebench: An Automated Pipeline for Task Collection and Decontaminated Evaluation of Software Engineering Agents
- SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks?
- SWE-Pruner: Self-Adaptive Context Pruning for Coding Agents
- SWE-Exp: Experience-Driven Software Issue Resolution
- SWE-Effi: Re-Evaluating Software AI Agent System Effectiveness Under Resource Constraints
- R2E-Gym: Procedural Environments and Hybrid Verifiers for Scaling Open-Weights SWE Agents
- SWE-Bench++: A Framework for the Scalable Generation of Software Engineering Benchmarks from Open-Source Repositories
- SWE-Bench ProMax: Benchmarking Agents on Large-Scale Multilingual Code Refactoring
- SWE-Bench+: Enhanced Coding Benchmark for LLMs
- Are "Solved Issues" in SWE-bench Really Solved Correctly? An Empirical Study
Related papers
- Falsification-Based Verification of LLM-Generated Optimization Models: Sound Test Batteries and Their Detection Limits
- GitSkills: A Dataset of Agent Skills on GitHub
- SABER: Benchmarking Operational Safety of LLM Coding Agents in Stateful Project Workspaces
- PackMonitor: Enabling Zero Package Hallucinations Through Decoding-Time Monitoring
- IntentCoding: Amplifying User Intent in Code Generation
- Incentives and Outcomes in Bug Bounties