Skip to Content

Did Commander Cody Let Obi-Wan Live on Purpose?

Did Commander Cody Let Obi-Wan Live on Purpose?

We all remember that moment on Utapau. Obi-Wan is riding Boga across the sinkhole, Cody gets the transmission from Palpatine, and within seconds the clones turn their guns on him. Then Obi-Wan gets blasted off the wall and disappears into the depths below.

And because Obi-Wan survives, a lot of fans have asked the same question ever since: did Cody secretly let him live?

Because when you really think about it, Cody had just handed Obi-Wan his lightsaber back only moments earlier. So it’s easy to look at that whole scene and wonder if there was any hesitation there at all.

Cody Wasn’t Saving Obi-Wan, He Tried to Kill Him, and Failed

If you go back and watch the scene in Revenge of the Sith, Cody doesn’t hesitate at all.

“Execute Order 66” [4K UHD] | Star Wars: Episode III - Revenge of the Sith (2005)

The moment Palpatine’s message comes through, “Execute Order 66”, Cody immediately turns to his men and orders them to fire on Obi-Wan. There’s no pause, no warning, nothing. From Cody’s point of view, Obi-Wan had just become the target.

And one source actually makes this even clearer.

In the Star Wars: Revenge of the Sith novelization by Matthew Stover, Cody’s reaction to the order isn’t regret or hesitation. It’s frustration. The order had come just a little too late.

Because only moments earlier, Cody had returned Obi-Wan’s lightsaber to him before the battle. When the command finally arrives, Cody even mutters to himself that it would’ve been much easier if the order had come through before he gave Obi-Wan back the lightsaber. In other words, he’s annoyed that Obi-Wan is now armed again.

That little detail tells us everything we need to know about Cody’s mindset in that moment.

He wasn’t secretly trying to spare Obi-Wan. If anything, he wanted the exact opposite. Cody wanted Obi-Wan dead, and the only reason Obi-Wan made it out was because the attack failed.

From Cody’s point of view, the job probably looked finished anyway. Obi-Wan gets blasted off the sinkhole wall and disappears into the depths below. For anyone standing up there, that would’ve looked like a kill.

So Obi-Wan surviving had nothing to do with mercy from Cody. It was just a mix of bad aim, bad luck for the clones, and very good luck for Obi-Wan.

Cody Didn’t Regret Order 66, But He Did Start Questioning the Empire

Now, because of that Order 66 moment, some fans like to connect another idea to it. Since Commander Cody eventually disappears from the Empire later on, people sometimes assume he must have regretted what happened with Obi-Wan.

But the material we have doesn’t really point to that.

Cody leaving the Empire wasn’t about suddenly realizing he had made a mistake during Order 66. The timeline actually shows something different.

Years after the fall of the Republic, Cody was still serving the Empire. We see this in The Bad Batch, where he appears on an Imperial mission alongside Crosshair. By this point the war is already over, but the clones are still being used to enforce the Empire’s rule across different worlds.

And during that mission, you can start to see Cody questioning what the Empire is turning into.

He tells Crosshair that the war is finished and that the clones were supposed to help build something better afterward. Instead, what they’re doing now looks more like occupation than peacekeeping.

Commander Cody Desertion | Star Wars: The Bad Batch Season 2

Not long after that mission, Cody disappears from Imperial service completely.

So the interesting part of Cody’s story isn’t that he secretly spared Obi-Wan. It’s that years later, he may have started realizing the Empire he helped create wasn’t the Republic he had been fighting for.