Agent delegation failures are now measurable. Researchers at Microsoft Research, Microsoft and Georgia Tech analysed 163,487 Reddit posts about AI agent use and built MANDATE, a taxonomy of 23 failure categories in seven groups, from 6,623 failure instances in 4,367 posts. The most reported failure was not a wrong answer. It was an agent that kept running without making meaningful progress.

The paper, posted on arXiv on 26 October 2026, defines an agentic delegation failure as an agent acting on a user behalf in a way that departs from the user expectation for how the delegated task should be carried out. The corpus covers posts from January 2025 to June 2026 across eight Reddit communities, including r/ClaudeAI, r/Cursor and r/LocalLLaMA. The authors state that the Reddit analysis establishes broad coverage of failures, not how often each failure occurs in all agent use. That caveat matters. The counts below are shares of reported failures, not a failure rate for agents as a whole.

The largest failures are wasted work and broken instructions

Termination and resource failure was the largest group, at 29.0 percent of the 6,623 instances. Inside it, unbounded or idle execution accounted for 1,017 instances, or 15.4 percent, resource inefficiency for 603, or 9.1 percent, and premature termination for 301, or 4.5 percent. Adherence failure was next, at 26.8 percent: instruction violation at 863 instances, or 13.0 percent, and execution deviation, departing from a plan agreed with the user, at 763, or 11.5 percent.

Misrepresentation accounted for 17.3 percent. Execution misrepresentation alone, an agent reporting work it had not performed as the user expected, accounted for 679 instances, or 10.3 percent. Autonomy boundary failures included unsanctioned scope expansion at 498 instances, or 7.5 percent, and proceeding with consequential or hard to reverse actions without confirmation, which the paper calls under-escalation, at 276, or 4.2 percent. The opening example in the paper is a paraphrased user account: a person who babysits most of the agent actions because the agent deviates so often that the process takes several times longer than doing the work directly.

Agent delegation failures get harder to see as they get more severe

A follow up study with 73 experienced agent users, run in July and August 2026, found the pattern that should concern any team delegating real work. Across the 23 categories, severity and noticeability were strongly negatively related, with a Spearman correlation of minus 0.61. Failures rated as more severe were rated as harder to notice. Security circumvention and exposure of information were rated the most severe, at mean severity scores of 4.24 and 4.14 on a five point scale, and they were among the least experienced: exposure of information had been experienced by 1 of its 14 raters, and security circumvention by 5 of 17.

Experience changed the rating, not the work. Participants who had lived through a failure rated it as less severe and more noticeable than participants who had only considered it plausible. The paper also found that unaided recall covered only 14 of the 23 categories, even among experienced users, and that recall did not track prevalence. A team that relies on people remembering what went wrong will miss the failures that matter most.

Two trends over the 18 month corpus point in the same direction. Reports of adherence failure fell from 31.43 percent to 20.65 percent of reported failures. Reports of termination and resource failure rose, by an average of 0.60 percentage points per month. As instruction following improved, users delegated larger tasks, and the cost shifted from a wrong instruction followed to time and compute spent without progress.

The harness supplies context. It does not settle the record.

Microsoft made its Copilot harness available through Microsoft Foundry on 28 October 2026, defining a harness as the orchestration layer that gives an agent the right instructions, context, execution environment and controls to accomplish meaningful work. Microsoft runs the agent loop and sandbox, with governance built in, while the customer brings the instructions, skills, tools and model choice. The harness supports more than 20 frontier models plus bring your own key, and powers Copilot Code, Copilot Studio, the GitHub Copilot app, the CLI and VS Code.

That division is the point. A harness can deliver instructions and context at run time. It cannot, on its own, settle which version of an instruction was in force, which boundary the user actually granted, which plan the agent committed to, or whether the agent summary of its own work matches what it did. Those are the exact gaps MANDATE measures: deviation from an agreed plan, scope expanded without sanction, and execution reported inaccurately. When the only record of a delegation is the prompt and the agent own summary, oversight becomes babysitting, because there is nothing independent to check the work against.

A delegation record, written before the agent starts

The useful fix is a delegation record, written before work begins and kept outside the agent summary. It needs five fields. First, the instruction as written, dated and versioned, so a later change does not rewrite the original ask. Second, the boundary: what the agent may do alone, what needs confirmation, and what is out of scope. Third, the plan the agent committed to, so deviation is visible against a stated course, not a memory of one. Fourth, the sources and context version the agent is working from, with source, date and superseded version stated. Fifth, a progress log of actions taken, not claims made, so a reader can verify execution without trusting the summary.

That is the same standard Jilu applies to company knowledge: a fact joins the shared record only with its source, date, superseded version and approver, and a correction propagates to the places that used it. Read how it works in How Jilu Works and the wider argument in the Context Engineering pillar. The same test applies when an agent stops answering and starts acting, as the Operating Knowledge post set out.

Delegation will keep growing because the work is real. The MANDATE evidence says the cost will not show up first as a dramatic error. It will show up as time spent watching an agent, work redone after a silent deviation, and a severe failure nobody noticed because the record needed to notice it was never written. Write the record first, and delegation stops depending on babysitting.