AUTOWARCOM: Big ambition, thin force structure, uncertain funding
AUTOWARCOM’s fast start hinges on a politically fragile reconciliation bill and a force-structure build that, unlike prior functional COCOMs, has little to draw on.
Key facts
- AUTOWARCOM’s launch is tied to a $54B request routed through a reconciliation bill, which sources describe as politically uncertain and time-bound.
- Analysts argue a four-star combatant command focused on acquisition is a poor fit for the COCOM model; an MDA-like structure may be more appropriate.
- The Army rapidly created an autonomy-focused component by repurposing existing organisations; Navy and Air Force positions are less defined in the reporting.
3 minute read
Defense One reports that the Pentagon’s proposed U.S. Autonomous Warfare Command (AUTOWARCOM) is at risk of being stood up as an underpowered headquarters if Congress does not pass an atypical funding package. The department earlier sought $54 billion for a Defense Autonomous Warfare Group, which Secretary of Defense Pete Hegseth has linked to launching AUTOWARCOM, but the Trump administration routed this and other priorities through a separate reconciliation bill rather than the main defense budget. Analysts quoted in the piece frame reconciliation as politically uncertain and time-sensitive; if it fails, AUTOWARCOM could exist in name while lacking the “buying power” to function as intended, or it could be forced to extract personnel and procurement funding from the services—an approach expected to trigger resistance.
A second constraint is organisational: functional combatant commands historically build on existing force structure, but AUTOWARCOM is described as working “backwards”. The plan envisages new service component commands and even a new autonomous-warfare corps for officers and enlisted personnel, yet publicly available guidance—Hegseth’s directive memo and an “operational roadmap” (Project Agincourt)—does not, per the reporting, explain how new specialties would integrate with existing units. Mark Cancian (CSIS) argues that a four-star COCOM optimised for acquisition is structurally odd because COCOMs typically operate forces; he suggests a Missile Defense Agency-like model—three-star, budgeted, developing systems and handing them off to services—may be a better fit. Both Cancian and John Ferrari (AEI) warn that centralising operations would be counterproductive given the tight integration required between unmanned systems and manoeuvre forces; Ferrari instead anticipates a role skewed toward doctrine, training, and synchronising disparate efforts.
The services’ responses appear uneven. The Army moved quickly: after AUTOWARCOM’s announcement, it created its own autonomy command and rebranded its Futures and Concepts Command into Futures and Autonomy Command, providing a staffed, funded component with minimal friction. By contrast, the Navy and Air Force referred inquiries to the Office of the Secretary of Defense, while the Pentagon pointed to the Navy’s new Direct Reporting Portfolio Manager for Robotic and Autonomous Systems and said the Air Force is exploring organisational structures to accelerate implementation and training.
For European defence officials and industry, the immediate lesson is not that Europe should mirror a U.S. four-star acquisition-centric command, but that Washington is testing a far more centralised mechanism to accelerate autonomy procurement and iteration. If successful, it may harden U.S. expectations for NATO interoperability in autonomous C2, mission autonomy safety cases, and data/compute pipelines, and it could reshape transatlantic market access by concentrating purchasing decisions. If it stalls, European partners should anticipate continued fragmentation across U.S. services, complicating joint capability roadmaps and slowing standardisation for autonomous teaming concepts.
Source: Defense One