Hegseth: Autonomous Warfare Command Has Always Been End State

U.S. Department of War | C. Todd Lopez

United States Secretary of War Pete Hegseth announced plans to establish the Autonomous Warfare Command following the temporary launch of Project Agincourt, targeting the acquisition of hundreds of thousands of one-way attack systems this year. This policy aims to eventually field millions of low-cost unmanned platforms across all combatant commands.

To bridge high-level doctrine with service-level execution, the U.S. Army established the Futures and Autonomous Systems Command, designed to aggregate purchasing power and feed capabilities into the joint command. Operational implementation is already underway across theater forces. In June 2026, autonomous surface systems executed a recovery operation off Oman, while the Theodore Roosevelt Carrier Strike Group deployed on October 8 with medium and large unmanned surface vessels. Massed autonomy is critical. Concurrently, the U.S. Air Force is conducting operational integration of autonomous fighters at Creech Air Force Base in Nevada, projecting cost savings five to ten times greater than manned alternatives despite ongoing procurement reforms.

Comment

Establishing Autonomous Warfare Command and service-level components like Futures and Autonomous Systems Command reflects a structural transition from ad-hoc operational testing to institutionalised command authority over uncrewed systems. Centralising joint autonomy under a functional combatant command addresses the friction between service-specific acquisition channels and cross-domain data integration. Without a unified command structure, autonomous surface and aerial platforms risk operating within isolated combatant command silos rather than synchronized kill chains.

This organisational consolidation mirrors the operational evolution of United States Cyber Command, which initially emerged to unify fragmented branch-level cyber capabilities under a single operational authority. By establishing institutional mechanisms such as Fascom to channel service developments into Autowarcom, the Department of War aims to standardise autonomous fleet architecture across the Theodore Roosevelt Carrier Strike Group and frontline Air Force wings.

Strategic Question for Discussion

Which factor presents a greater bottleneck to integrating service-level entities like Fascom into Autowarcom — cross-service data interoperability or traditional branch procurement rivalries, and how might that dynamic shift during a high-intensity crisis?

The available evidence points toward cross-service data interoperability as the more immediate operational constraint, as joint autonomous networks require real-time, cross-domain synthesis that legacy service architectures were not built to share. While procurement rivalries between services persist over budget allocation, establishing concrete operational conduits like Fascom forces programmatic alignment faster than technical software standardization can be executed across disparate combatant commands.

Share your assessment in the comments below.

To read in details click here