Hegseth plans ‘Autonomous Warfare Command’

Defense One | Bradley Peniston

Defense Secretary Pete Hegseth announced plans to establish the Autonomous Warfare Command by October 1, 2027, to scale robotic capabilities across the joint force. This new four-star combatant command will inherit planning from the Pentagon's unmanned systems portfolio manager, which is being renamed Project Agincourt under the leadership of Owen West.

This structural shift aims to accelerate the deployment of robotic weapons by bypassing traditional acquisition bottlenecks. To support this transition, the military services will create new job classification frameworks for autonomous warfighters. Hegseth also launched Project Meridian, an advisory committee led by Elon Musk, Palmer Luckey, and Newt Gingrich, to identify future warfare domains. Additionally, a homeland defense initiative called FORTRESS America will build a massive new base to enhance domestic resilience. The initiative targets foreign dependencies. This effort includes stockpiling critical munitions, medicine, and blood to secure the homeland against potential supply chain disruptions.

Comment

The establishment of AUTOWARCOM as a distinct four-star combatant command represents a fundamental shift in the Pentagon's command and control architecture for emerging technologies. By granting service-like authorities to this new entity, the Department of Defense bypasses the traditional, fragmented service-level acquisition pipelines that historically slowed the integration of unmanned platforms. This centralisation under Project Agincourt aims to harmonise operational requirements directly with rapid prototyping cycles. Consequently, the traditional boundary between combatant commanders who employ forces and service secretaries who organise, train, and equip them becomes increasingly blurred.

This structural realignment will likely trigger bureaucratic friction with established service branches, particularly the US Navy and US Air Force, which guard their budgetary authority over platform development. As AUTOWARCOM asserts its mandate to scale autonomous capabilities, the joint force faces the challenge of integrating these systems into existing tactical networks without clear doctrinal precedence. Ultimately, the operational utility of AUTOWARCOM depends on its ability to wrest funding control from legacy service program offices to sustain rapid software-defined updates across the joint force.

Strategic Question for Discussion

If AUTOWARCOM successfully secures service-like acquisition authorities, how will the US Navy and US Air Force adapt their own independent uncrewed development programs to avoid redundant capabilities?

The trajectory indicates that the services will likely resist full integration, choosing instead to brand their proprietary platforms as specialised niche capabilities exempt from AUTOWARCOM's oversight. My assessment is that this defensive budgeting will persist until joint exercises demonstrate that siloed software architectures actively degrade battlefield interoperability. Consequently, the transition will likely yield a dual-track system where legacy programs remain service-controlled while rapid, attritable systems are consolidated under the new command.

Share your assessment in the comments below.

To read in details click here