The Chief Digital and Artificial Intelligence Office published an update on October 5 on Swarm Forge, which the department calls Pace-Setting Project number one under its AI strategy. The program started in January 2026 and is built around a compressed 90-day development cycle: commercial drone companies are put in the field next to Special Operations Forces operators, and their autonomous swarm systems are tested under realistic conditions every quarter in events the department calls Crucibles. More than 130 companies entered at the start. Through continuous field winnowing, roughly 25 remain as active partners.
The program has now run three Crucibles. The second took place in June. The third, in September at Fort Bragg, North Carolina, tested systems under electronic warfare interference, at night, and in complex terrain. That event combined air and ground systems under what the release describes as an advanced battle manager, with human operators on the loop rather than in it, meaning operators supervise and can intervene while the swarm executes on its own. The department characterizes the heterogeneous swarms it saw there as immediate, scalable force multipliers. A fourth Crucible is scheduled for late January 2027 at Camp Lejeune, North Carolina, and the plan is to select final swarm packages roughly one year after launch and transition validated packages directly to operational units by the end of that fourth event.
The organizations named are the CDAO, U.S. Army Special Operations Command, and the newly created Direct Reporting Portfolio Manager for Unmanned Systems, the office Owen West left the Defense Innovation Unit to run last week. That linkage matters: Swarm Forge is the test bed and the portfolio office is the buyer, so the program is structured to end in procurement rather than a demonstration report. The release does not disclose swarm sizes, the ratio of operators to vehicles, target sets, or funding, so the numbers that would let anyone judge how far the autonomy has actually progressed are not public.
The interesting design choice is methodological. Rather than writing a requirement and running a multi-year competition, the department is using repeated live-fire field trials as the selection function, with operators in the loop of evaluation and vendors cut between rounds. That is closer to how frontier AI labs iterate on models than to traditional acquisition, and it puts electronic-warfare resilience and night operations in the test from the start instead of at the end. The open question is whether quarterly field events produce enough data to distinguish robust autonomy from well-rehearsed demonstrations, especially when the swarm software from about 25 different firms has to interoperate under a common battle manager. The January Crucible and the first transition decisions will be the first real test of whether this model of acquisition scales.