The $\tau^\tau$-bench (pronounced hyper-tau-bench), a benchmark that makes agent construction the task, is introduced to turn the work of cooperative agent building into a measurable target for coding agents.
Abstract
LLM agents are rapidly becoming production software, deployed to handle customer service, adjudicate disputes, and operate internal systems. Notably, the work of building them is increasingly handed to coding agents, yet existing benchmarks say little about whether an AI system can deliver one under the conditions of a real client engagement. We introduce $\tau^\tau$-bench (pronounced hyper-tau-bench), a benchmark that makes agent construction the task. A developer agent is given the records a business actually keeps, a client who holds requirements, a production API that operations must run through, a codebase to inherit, and limits on serving cost and models: the same starting point a real engagement provides. From these it must deliver a complete customer-service agent, scored by deploying that agent against held-out simulated users. Across 53 tasks spanning four domains, the strongest configuration, Claude Opus 5 under Claude Code, passes just 23.9% of evaluation simulations. Meanwhile, an expert-authored reference ceiling scores 82.2%. The failures mirror ones human agent developers see: models issue shallow queries in place of deep comprehension of the records, communicate almost nothing to the client, and experiment too little with agent architecture and serving spend, shipping the first design that runs. We aim for $\tau^\tau$-bench to turn the work of cooperative agent building into a measurable target for coding agents.
ERPBench is introduced, a benchmark that evaluates screenshot-only agents on a live and reproducible system and scores each task against ground-truth values in its database and presents a production-grade harness that gates agent actions behind human approval for safe deployment.
Kratika Bhagtani, K. Sridhar, M. B. Pouyan et al.· 1 citation
AgentSWE is introduced, a benchmark for agent software engineering spanning three stages of the agent development lifecycle: Creation of a complete agent from a natural-language requirement, Editing of production agent codebases, and Optimization toward a measurable target.
Jia-Hao Wang, Hong-Jin Qian, Yuyang Hu et al.· 0 citations
Experiments on guideline-following and artifact-generation tasks show that specifications can serve not merely as behavioral guidance, but as authority over compliant execution and completion.
Hai-Qing Li, Xin-Yu Ma, Yin-Hao Wu et al.· 0 citations
This position paper proposes that companies deploying agents in sustained operation should rebuild their cognitive substrate, the shared environment agents read as working context, around representations matched to that reasoning surface, isolating schema translation to the action boundary.
Oliver Aleksander Larsen, M. T. Moghaddam· 0 citations
Large language model (LLM)-assisted operations often rely on many independent tools, with the operator or agent stitching partial answers together client-side. This can produce correct answers, but the reasoning remains brittle, session-local, and difficult to reuse. We present Axiom, a production federated query engin...