The Army is quietly taking a red pen to its wish list of robot trucks and unmanned battle wagons, trimming ambitions after years of promising to turn ground formations into something between a Tesla convoy and a “Terminator” reboot. Instead of a sprawling menu of bespoke autonomous vehicles, leaders now want a leaner portfolio and a tighter focus on software, integration and affordability. That shift comes with a warning label: some programs will shrink, some will morph and a few may simply vanish.
Behind the jargon about “streamlining” and “realignment” is a blunt reality that even the Pentagon cannot escape: budgets are finite, humans are still required and not every shiny robot gets to survive contact with the spreadsheet. As the Army pares back its ground vehicle autonomy plans, it is weighing which efforts actually help soldiers in the near term and which look more like science projects with lobbyists.
From robot gold rush to budget diet
The Army spent the past several years pitching a future where convoys drove themselves, Robotic Combat Vehicles scouted ahead and human crews lounged in command vehicles like slightly stressed airline pilots. Now senior leaders are signaling that the autonomy buffet is closing early and the kitchen staff is being told to pick a few dishes and do them well. Dec has described possible cuts as part of a deliberate shift to a new approach to autonomy, one that favors common architectures and reusable software over a zoo of one-off platforms.
That pivot is not just about taste, it is about money and manpower. In the same breath that Dec talked about trimming autonomy efforts, the Army has been warning that more reductions are coming as part of a broader transformation ordered by Secretary of Defense Pete Hegseth and reinforced by George, who called earlier cuts only “a first step” toward a larger restructuring of roles and programs. The service is already wrestling with what Hegseth labeled “excess ground vehicles,” and the autonomy portfolio is now being pulled into that same diet plan rather than treated as a protected growth area.
Robotic Combat Vehicle: from star of the show to name change
If there was a poster child for the Army’s robot enthusiasm, it was the Robotic Combat Vehicle, a family of unmanned platforms meant to scout, carry weapons and generally make armored brigades look futuristic. That star is now getting a more modest billing. Earlier this year the Army chose not to sign a production deal for its previous Robotic Combat Vehicle effort, and officials are still working through what the next version of that concept should look like. Dec has acknowledged that plans for the Robotic Combat Vehicle are evolving and that decisions on the path ahead have not yet been finalized.
In parallel, the Army has already started a cheaper competition for what used to be the Robotic Combat Vehicle, complete with a new name and a more constrained role inside Armored Brigade Combat Teams. The new request for information focuses on affordability and integration rather than exotic prototypes, a quiet admission that the earlier vision was too expensive and too ambitious for the current budget climate. Rasch has also pointed to the Human Machine Integrated Formation, or HMIF, as another venue where the Army is rethinking how robotic systems and crewed vehicles work together, looking beyond the original Robotic Combat Vehicle construct and searching elsewhere for autonomy software that can be reused across multiple efforts.
Autonomous resupply: the robot truck that might actually show up
While some high‑end combat robots are being sent back to the drawing board, the Army’s more humble dream of self‑driving resupply trucks is still very much alive, if slightly delayed and nervously watching the budget process. The service wants to field an Autonomous Transport Vehicle System within roughly the next 12 to 18 months, turning existing logistics vehicles into robot teammates that can follow routes, reduce driver fatigue and keep humans a bit farther from roadside bombs. The catch is that budget delays could slow down fielding and push back source selection for that capability, which is not the sort of suspense program managers enjoy.
Even so, the autonomous resupply effort has made tangible progress that some flashier programs cannot claim. Since the initial experimentation phase, the program has downselected to two vendors, Forterra and Carnegie Robotics, and moved into a second phase focused on refining the technology and reducing the risk of operator fatigue. In a portfolio where several efforts are being re‑scoped or renamed, the Autonomous Transport Vehicle System stands out as a practical, near‑term application of autonomy that directly addresses a chronic problem: too many long, dangerous convoy hours for too few drivers.
Program cancellations, unanswered questions and the great robot reshuffle
The Army’s new restraint on autonomy is not happening in a vacuum, it is part of a broader campaign to prune its ground vehicle garden. Earlier this year the service abruptly ended several vehicle programs after Secretary of Defense Pete Hegseth flagged a glut of platforms and called for a “comprehensive transformation” that would modernize inefficient defense contracts and cut excess ground vehicles. The Army’s decision to terminate those efforts, previewed in a memo from Hegseth, left industry and some lawmakers asking what exactly would replace them and how the service planned to avoid another round of expensive dead ends.
That uncertainty is amplified by a wider restructuring described as a Break with Legacy, centered on Program Cancellations and Reductions that touch everything from artillery to robotic systems. The Robotic Combat Vehicle is explicitly listed in that transformation as a program being reshaped, with the Army looking at different roles such as reconnaissance, mortars and weapons carriers rather than a single monolithic family. At the same time, the service is consolidating offices and cutting roles, with George warning that the initial moves are only the beginning. For companies that spent years chasing bespoke vehicle contracts, the message is clear: the era of big, standalone ground robot programs is giving way to a more modular, software‑centric approach, and not everyone will make the cut.
New autonomy initiatives, shifting platforms and the ISV pivot
Even as the Army trims some efforts, it is quietly launching others under new banners, which is either clever adaptation or a rebranding exercise depending on how charitable you feel. One of the more intriguing moves is a new initiative for two autonomous platforms under a concept called the Common Autono, a sign that the service wants shared solutions instead of a separate autonomy stack for every vehicle type. That push for commonality lines up with Dec’s argument that the Army needs a more coherent autonomy strategy rather than a patchwork of experiments that never scale.
The service is also shaking up how and where it tests new autonomy concepts. Over the fall, the Army began pivoting away from using Infantry Squad Vehicles as the primary testbed for a new autonomy initiative, a shift that reflects frustration with trying to bolt advanced software onto platforms that were never designed for it. Reporting has described the UxS shakeup as part of a broader debate inside the Office for Ground Combat System about how to proceed with unmanned systems and which formations should own them. Instead of treating the Infantry Squad Vehicle as the default science project, the Army is now looking at other options that may be better suited to hosting sensors, processors and the inevitable tangle of cables that come with autonomy kits.
Software, soldiers and the maintenance reality check
Behind every sleek rendering of a robotic vehicle is a less glamorous truth that every mechanic already knows: someone has to keep the thing running. As the Army leans harder into autonomy, it is discovering that the real bottleneck is not just hardware or funding, it is digital skill. Recent analysis from within the force has stressed that the need for software and data fluency is eclipsing the traditional electrical or mechanical skills that used to define maintenance, especially for complex systems that blend sensors, networks and autonomy algorithms. Elaborating on that trend, Army thinkers have argued that formations will need maintainers who can troubleshoot code and cyber issues as readily as they swap out a transmission.
That skills gap is one reason the service is trying to consolidate autonomy software and architectures instead of fielding a dozen incompatible stacks that each require their own training pipeline. Rasch has been explicit that for efforts like the Human Machine Integrated Formation, the Army is looking beyond its traditional vendors for autonomy software that can be applied across multiple robotic initiatives, including whatever emerges from the reworked Robotic Combat Vehicle effort. The more the service can standardize on common autonomy components, the easier it becomes to train soldiers, stock spares and keep the robots from turning into very expensive lawn ornaments the first time a software update goes sideways.
All of this leaves the Army in a slightly awkward middle ground. On one hand, leaders are trimming programs, canceling some vehicles and warning that more cuts are coming. On the other, they are doubling down on autonomy as a core part of future formations, launching efforts like the Common Autono and HMIF while trying to get practical systems like the Autonomous Transport Vehicle System into the field. It is a classic modernization juggling act: fewer bespoke platforms, more shared software, and a lot of nervous program managers hoping their robot makes it through the next round of budget reviews with its funding and its name intact.