mlsanityData to 7 Oct 2026

Software Delegation Contracts: Measuring Reviewability in AI Coding-Agent Work

arXiv 2606.17099 ↗First posted 14 Jun 2026cs.SE cs.AIcited by 0

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

AI coding agents increasingly accept assigned software tasks, modify repositories under bounded authority, and return work packages for review. Prior work proposed the software delegation contract, covering the task, authority, returned work package, and acceptance context, as the unit of analysis for delegated coding work, but did not measure its effects. This paper reports a controlled pilot study of explicit delegation contracts for coding agents. We built a dependency-free TypeScript API task environment with seeded defects and documentation gaps, authored ten tasks across five families, and ran 64 agent executions across two model tiers under three conditions: a realistic issue-style prompt, an explicit delegation contract, and a contract with a required evidence bundle. Each run was scored with hidden acceptance tests, mutation checks, and scope analysis, then reviewed by three independent condition-blinded model-based reviewers using a fixed rubric, for 192 reviews. Explicit contracts did not improve objective task outcomes: all 64 runs passed hidden acceptance checks, with zero scope violations. They did improve reviewability. Evidence sufficiency improved in 22 of 30 paired comparisons and worsened in none (+0.83 on a 5-point scale, p < 0.0001, Cliff's delta = 0.66); reviewer ambiguity decreased (p = 0.035); changed-file lists, known-limitations sections, residual-risk sections, and reviewer checklists appeared mostly or only when demanded by the contract. Contracts cost +13% agent tokens and +38% wall-clock time, with larger effects for the weaker model tier. On these small tasks, delegation contracts bought reviewability rather than correctness.

Key facts. No citing papers in the map yet (data through 7 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 7 of its 16 references that are in the map. First posted on arXiv 14 Jun 2026.

Builds on

7 of 16 references.

Closest ancestors · 3

Same direction, newest first

  1. 2026AIDev: Studying AI Coding Agents on GitHub9 Feb
  2. 2024Agentless: Demystifying LLM-based Software Engineering Agents1 Jul
  3. 2024SWE-agent: Agent-Computer Interfaces Enable Automated Software Engineering6 May

Other references · 4

  1. 2023Judging LLM-as-a-Judge with MT-Bench and Chatbot Arenacited by 8,393
  2. 2023SWE-bench: Can Language Models Resolve Real-World GitHub Issues?cited by 3,193
  3. 2024A Study on Developer Behaviors for Validating and Repairing LLM-Generated Code Using Eye Tracking and IDE Actionscited by 12
  4. 2025On Developers' Self-Declaration of AI-Generated Code: An Analysis of Practicescited by 1

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026CR-Bench: Evaluating the Real-World Utility of AI Code Review Agents
  2. 2026The Work Behind Delegation: A Framework for Supervising AI Coding Agents
  3. 2026Scanning the Harness: A Repository Study of Configuration Exposures in AI Coding Agents
  4. 2026When AI Teammates Meet Code Review: Collaboration Signals Shaping the Integration of Agent-Authored Pull Requests
  5. 2026Using Agentic AI for contextualized and multifaceted code review at Ericsson
  6. 2026Are We All Using Agents the Same Way? An Empirical Study of Core and Peripheral Developers Use of Coding Agents
  7. 2026Why Are Agentic Pull Requests Merged or Rejected? An Empirical Study
  8. 2026How Do AI Coding Agents Contribute to Software Development? an Empirical Study of Agentic Pull Requests