🤖 AI Summary
This study addresses the significant misalignment between existing coding assistant benchmarks and real-world scenarios, particularly regarding task long-horizon complexity and the authenticity of multi-turn interactions. To bridge this gap, we propose a weak-to-strong automated synthesis pipeline for constructing long-horizon tasks and derive four user personas from authentic interaction logs to establish user-simulating agents that replicate realistic multi-turn behaviors. Evaluations using this benchmark reveal that current models provide critically insufficient support for non-expert users, achieving pass rates below 25%. Furthermore, our analysis identifies precise questioning, accurate localization, and effective repair as key capability bottlenecks. By systematically addressing these limitations, this work narrows the divide between benchmark evaluation and practical deployment in AI-assisted software engineering.
📝 Abstract
Coding assistants such as Claude Code and Codex have become a major application of LLM agents, yet existing benchmarks remain far from real-world use, particularly in task horizon and interaction length. Code assistants require completing long chains of development work in continuously evolving repositories, while repeatedly clarifying requirements and adapting implementations through multi-turn interaction. To address these gaps, we introduce SWE-Journey, a benchmark for more realistic evaluation of coding assistants. To address the task-horizon gap, we propose a weak-to-strong synthesis pipeline that automatically constructs long-horizon coding tasks. To address the interaction gap, we mine four representative user personas from real interaction data and build a user-simulation agent to reproduce realistic code-assistance interactions. On average, models pass over 75% of tests for requested functionality with software architects, but fewer than 25% with non-coders. These results show that current coding assistants still fall short of enabling reliable coding for non-coders. We further analyze the reasons for this gap and identify asking right, finding right, and fixing right as key capabilities during interaction.