Star Wars: What Happened To Commander Cody After Executing Order 66
When Emperor Palpatine initiated Order 66 in Star Wars: Episode III – Revenge of the Sith, Commander Cody was among the clone troopers that turned against their Jedi compatriots — but he survived long after betraying Obi-Wan Kenobi. First mentioned offhandedly in 1977’s A New Hope, the Clone Wars was a conflict between the Galactic Republic and the Confederacy of Independent Systems that served as the backdrop to many Star Wars projects, most notably the prequel trilogy and the Star Wars: The Clone Wars TV show. The Republic’s forces were composed primarily of a large clone army grown by Kaminoan scientists from the genetic blueprint of bounty hunter Jango Fett. Although born identical for all practical purposes, some of these clones, Cody among them, were given additional training meant to qualify them for positions of greater power and responsibility. Properly named CC-2224, Commander Cody first appeared onscreen in Revenge of the Sith, after which The Clone Wars would go on to cover some of his history in the war.
Throughout the Clone Wars, Cody often served with Jedi General Obi-Wan Kenobi, building the respect that can be seen between the two in Revenge of the Sith. Together, they would lead the 212th Attack Battalion in several large-scale battles against the droid armies. Engaged in a mission to capture General Grievous on Utapau when Palpatine announced Order 66, Cody nevertheless immediately began moving his forces against Obi-Wan Kenobi. Commander Cody was not one of the clone troopers who avoided their Order 66 programming. Despite being good friends with the Jedi, Cody wasn’t able to resist his clone inhibitor chip. His pursuit only ended when he was mistakenly believed Kenobi had fallen to his death in one of the planet’s massive sinkholes. As Palpatine transitioned the Galactic Republic into the Galactic Empire Cody remained loyal, becoming one of the first Stormtroopers. In this capacity, he participated in many campaigns for the Imperial war machine, including the so-called pacification of Kashyyyk, wherein the planet of the Wookies was completely subjugated. Here’s the full story of everything that happened to Commander Cody after The Clone Wars.
Cody’s Fate Is One Of Star Wars Most Unfair Endings
In serving the Empire after the Jedi were eliminated, Commander Cody was one of the last waves of clones to see action. Almost as soon as the Empire declared victory against the Trade Federation, the Imperial Army discontinued the Kaminoan program and from then on recruited conscripts for Stormtroopers. While some groups of clones, including Cody’s 212th Legion, would be kept together, many of the final clone generations were dispersed among Imperial territory to make room for the new human recruits filling the ranks. The transition from clone troopers to Stormtroopers was swift, and by Solo: A Star Wars Story, a mere 6 years after Episode III, they’d been all but phased out. Even as their practical impact declined, however, the clones’ influence could still be felt in both the iconography of the stormtroopers and the mythologized legacy of the Grand Army of the Republic that greatly encouraged Imperial enlistment.
Being shallowly venerated as war heroes for propaganda wasn’t enough to protect most clones from a bleak fate though, as demonstrated by Temuera Morrison’s homeless clone veteran cameo in Obi-Wan Kenobi. Fortunately, Cody managed to avoid becoming a persona non grata in the eyes of the Empire, but his story is still one of the most unfair character arcs in Star Wars. Commander Cody was uncommonly skilled as a combatant and tactician, but ultimately he was still susceptible to the programming impressed upon him since birth. Many fans feel that Star Wars should have found a narrative way to work around Cody and Order 66, similar to Clone Force 99 in The Bad Batch. Cody was a fan favorite and hero of The Clone Wars series, and ending as just another lackey for the Empire felts like an unfitting finale for him. Cody’s legacy is complicated by the Empire that he was made to serve, especially in a campaign as oppressive as the pacification of Kashyyyk — unlike Clone Wars’ Rex, who assisted the Rebel Alliance long after the Clone Wars. However, Cody unarguably lived an impactful life to both extremes, so at the very least he should not be judged solely by the moment of coerced betrayal shown in Revenge of the Sith.
Commander Cody’s Story Continues In The Bad Batch Season 2
Commander Cody’s story isn’t fully written yet though, as his presence in the trailer for Star Wars: The Bad Batch season 2 confirms that he’ll be given a chance to redeem himself in upcoming Star Wars projects. Fans hoping for an immediate return to hero status will be disappointed, however, as it seems Cody continues to work for the Empire. This is a crucial point because it’s already been revealed that the effects of clone trooper programming aren’t for life and wear off after some time, which means that even those who enacted Order 66 now have free will. Cody in Bad Batch season 2 still being an Imperial agent, despite no longer being a slave to programming, is a compellingly tragic turn for the former Star Wars: The Clone Wars protagonist. Even if this is just a fake-out to eventually reveal that Cody isn’t really on the Empire’s side, it seems Bad Batch season 2 will continue to explore the socio-political implications of the larger events in the Star Wars universe. Cody’s reasons for remaining with the Empire could be an interesting lens to explore this through, and it’s clear that Disney plans to continue writing Commander Cody’s story long after his Star Wars Episode III: Revenge Of The Sith debut.
