The Proposal

The U.S. military is right to accelerate the development and fielding of systems that harness autonomy and artificial intelligence (AI). These capabilities will be essential to deterring and, if necessary, defeating advanced adversaries. They can extend reach, complicate enemy targeting, reduce risk to personnel, increase desired effects, and help commanders sense and strike at machine speed.

But the Senate Armed Services Committee’s recently announced legislation to create a new combatant command for robotic and autonomous systems gets the problem backward. According to public reporting, the provision would centralize control over the acquisition and operation of uninhabited vehicles under a four-star general officer leading a new combatant command. The instinct is understandable. The Department of Defense/War is still moving too slowly in fielding affordable, attritable, autonomous, and AI-empowered capabilities at scale. Congress is right to press for urgency.

However, the proposed combatant command is ill-conceived. Organizing operational control around a class of technology would sub-optimize joint force operations. It confuses a tool with the mission.

Warfighting should be organized around objectives, effects, and campaigns—not platforms, weapons, or categories of hardware. Autonomous and AI-empowered vehicles do not constitute an independent theory of victory. They are but one means to an end. They help commanders find, fix, track, target, engage, assess, maneuver, protect, sustain, and communicate. However, their military value is realized only when they are integrated into a broader joint concept of operations.

The right question is not, “Who controls autonomous and AI-empowered systems?” The right question is, “How do these systems best contribute to a joint force commander’s military objectives as part of an enterprise approach?”

That distinction matters.

Geographic combatant commanders are responsible for deterring and defeating adversaries in theaters against complex operational problems. They need the full panoply of U.S. military capabilities available for integrated employment involving air, space, cyber, maritime, land, electronic warfare, intelligence, long-range strike, logistics, communications, inhabited and uninhabited vehicles, and autonomous systems. Those capabilities must be orchestrated together—not segregated into stovepipes—to generate desired operational effects.

Don’t Segregate Robotics From The Using Commands

If autonomous and AI-empowered systems are placed under a separate technology-specific combatant command, they risk being separated from the commanders responsible for the outcome of the fight. That creates friction where the military needs speed and it would introduce a new seam in command and control precisely when modern warfare demands tighter integration across domains.

Collaborative combat aircraft, for example, will likely achieve their greatest value when integrated with inhabited aircraft, with the combined approach producing effects greater than either could generate alone. The same is likely true for underwater autonomous vehicles, which will best operate in concert with surface ships and submarines as a teamed ecosystem of capabilities. This kind of collaboration requires common training, tactics, operational concepts, interoperability, and command relationships—not separate command stovepipes.

A high-end conflict will not unfold in neat organizational lanes. An autonomous aircraft, an uninhabited maritime system, a cruise missile, a space-enabled sensing node, or an autonomous logistics platform may all be part of the same kill chain. Their value depends on how they are connected to sensors, shooters, commanders, data networks, electronic warfare systems, and sustainment architectures.

Creating a separate combatant command for autonomous and AI systems would complicate tasking, authorities, targeting, prioritization, communications, and sustainment. It would increase seams, add command complexity, and reduce understanding of how the respective tools operate together. In combat, those seams are not administrative nuisances; they are vulnerabilities. Adversaries would exploit them.

Autonomy and AI should be embedded across the military, not isolated in a new stovepipe. These systems are not confined to a single domain. They operate in the air, on land, on and under the sea, in logistics networks, across the electromagnetic spectrum, and in support of space and cyber operations. The more pervasive they become, the less sense it makes to treat them as a separate operational category. The objective should be to make autonomy and AI a standard component of every service’s force design and every combatant command’s operational planning.

Confusing Acquisition With Employment

The proposal confuses acquisition with employment. The services need to build autonomous and AI-empowered systems that solve real operational problems for combatant commanders. A separate weapon-oriented command would create incentives to develop programs that satisfy that headquarters’ priorities rather than theater requirements. The result would be more systems that fit a bureaucratic category, but fewer capabilities that produce decisive combat effects.

The Pentagon does not need another combatant command. It needs the authorities, incentives, and accountability to field capability at speed.

Nor should the United States repeat the recurring mistake of treating technology as a substitute for operational concepts. Autonomous vehicles are important, but they are not magic. Their value in the battlespace depends on resilient communications, data architecture, human-machine teaming, electromagnetic protection, intelligence support, logistics, targeting processes, rules of engagement, training, and integration with human forces. A new command may create the appearance of decisive action, but it would not by itself solve any of those challenges.

Congress can drive urgency in better ways. It can require common architectures and data standards so systems can communicate across service components and domains. It can mandate large-scale experimentation tied to the real theater war plans in the combatant commands. It can establish fielding goals connected to operational problems rather than technology categories; accelerate acquisition pathways for successful prototypes; require joint exercises that integrate autonomous vehicles into air, maritime, land, space, cyber, and electromagnetic warfare operations; and clarify authorities so commanders can employ these systems at operationally relevant speed.

Most importantly, Congress can insist that autonomy be treated as a core element of joint warfighting—not as a separate enterprise detached from the commands who execute combat operations.

The purpose of defense organization is not to give every emerging technology its own four-star command. The purpose is to help the United States deter war and, if deterrence fails, win. That requires commanders who can integrate all available capabilities to achieve assigned military objectives. That is the essence of the U.S. joint warfighting construct established by the Goldwater-Nichols Act of 1986: the armed services organize, train, and equip; the combatant commands integrate service components, capabilities, and equipment to achieve the objectives of the contingency at hand.

The debate should not be framed as whether one supports or opposes autonomous systems. The United States needs them urgently. The real issue is how to organize for their effective employment.

A combatant command for robotic and autonomous systems would risk centralizing control in a way that makes these capabilities less responsive to the commanders who need them most. It would organize around the tool rather than the effect, create a new operational seam when the U.S. military needs greater integration, and risk building a bureaucracy around technology rather than accelerating its practical application in combat.

Field Robotics Faster To The Existing Combatant Commands

The better answer is to field autonomous and remotely operated capabilities faster, integrate them into every domain, and ensure they are employed by the commanders responsible for achieving operational outcomes.

Congress should push the Department of Defense/War hard on speed, scale, interoperability, and accountability. But operational control should remain tied to missions and commanders, not separated into a technology-specific combatant command.

Autonomy will be central to the future of warfare. That is exactly why it must be integrated into joint force operations—not segregated outside of them.