JetBrains study: coding-agent benchmarks should match real users' task flows

JetBrains-Research · hf · 2026-10-12

A JetBrains Research paper argues coding-agent evaluation ignores how real engineers interact. The authors collected 4,782 real agent sessions from JetBrains IDEs ("Production Sessions"), focusing on sessions with at least three user messages (33%). These differ from issue-derived benchmark tasks in two ways: requests span a far wider mix of types (code questions, planning, review, refactoring, execution), and users switch between types mid-session.

Comparing three public corpora shows markedly different Task Flows (lengths, task-type distributions, transitions), so no single interaction distribution is universally realistic—benchmarks should name a target use case and calibrate to it. They introduce SWE-TaskFlow, which preserves verified tasks/tests while steering interaction toward a target Task Flow via prompt splitting and verifiable repo QA, with a TaskFlow Alignment Score (TFAS) for trajectory selection. On 700 SWE-Bench Pro tasks, solving sequentially in several steps roughly doubles agent cost without a stable change in resolve rate—the interaction protocol itself is an important evaluation dimension.

Related event: JetBrains Research: Coding Agent Benchmarks Diverge from Real-World Workflows(2 posts)→

Original post →

More from coding & agent

coding & agent channel →