Skip to Content

All Clones That Disobeyed Order 66

All Clones That Disobeyed Order 66

Order 66 was one of the most devastating events to take place in the Star Wars universe. A single command from Darth Sidious–“Execute Order 66”–turned an entire army of cloned soldiers against their Jedi generals and led to the near-complete destruction of the Jedi.

But not all of the Clones carried out Order 66. Some of them consciously resisted the Order, while others were simply unaffected by it.

In this article, we’ll discuss all of the clones that disobeyed Order 66, both in Star Wars Canon and Legends.

In Canon

In Star Wars Canon, the Clone soldiers of the Grand Army of the Republic were controlled by inhibitor chips implanted in their brains. 

When Order 66 was issued, these inhibitor chips stole their autonomy and made it nearly impossible for them to disobey. 

And yet, not every Clone went through with the Order. Let’s take a closer look at their stories.

Clone Force 99

Clone Force 99, better known as the Bad Batch, was unlike any other squad in the Grand Army of the Republic. Genetically engineered with desirable mutations, each member possessed unique abilities: Hunter’s enhanced senses, Tech’s intellect, Wrecker’s brute strength, and Crosshair’s unerring aim. Later, they were joined by Echo, a former ARC trooper turned cybernetic specialist after surviving torture and experimentation at the hands of the Techno Union.

When Order 66 was issued,  the Bad Batch didn’t immediately turn on the Jedi. Their genetic mutations appeared to interfere with the programming of the inhibitor chips implanted in every clone’s brain.

Execute Order 66 [4K HDR] - Star Wars: The Bad Batch

But not all of them were immune. Crosshair, always the most rigid and loyal to orders, began acting differently. The chip’s influence started to override his judgment, amplifying his aggression and obsession with following protocol. During the Battle of Kaller, he tried to kill the Jedi padawan Caleb Dume, even when Hunter hesitated. This was the first sign that something was wrong. Eventually, Crosshair turned on the team completely. Under Admiral Rampart’s orders, his chip was intentionally enhanced on Kamino, locking in his loyalty to the Empire and pushing him to lead the hunt against his own brothers.

Wrecker’s struggle came later, but it was no less heartbreaking. For weeks, he suffered from increasingly severe headaches, brushing them off at first with his usual humor. But during a mission aboard a derelict Jedi cruiser on Bracca, the chip finally activated. In an instant, he turned on his squadmates, attacking the Bad Batch squad with deadly force and nearly killing the young clone Omega, whom he had grown protective of like a big brother. 

Star Wars The Bad Batch: Wrecker Executes Order 66 | Disney+

At that point, the team knew it was only a matter of time before the rest of them lost control too. With the help of Captain Rex, who had found them on Bracca and warned them of the danger, they used the ship’s old medical bay to perform high-risk surgeries to extract the chips from their brains. One by one, the Bad Batch reclaimed their free will before the chips could do to them what they had already done to so many others.

Cut Lawquane

Cut Lawquane was never meant to be different. He was bred to fight and die for the Republic, one of millions of identical soldiers created on Kamino. But fate had other plans. During a mission early in the Clone Wars, his transport was shot down. Presumed dead, Cut took the chance to disappear.

He wandered far from the war, eventually settling on the remote world of Saleucami. There, he found peace. He married a Twi’lek woman named Suu and became a father to her two children. He built a home, not from orders or duty, but from love—a life no clone was ever supposed to have.

When Order 66 was issued, Cut felt nothing. There was no violent switch flipping in his mind, no sudden urge to kill. Why? Because by then, he was no longer part of the Republic’s war machine. He wasn’t connected to the military command structure, and it’s likely he never received the order at all. The inhibitor chip in his brain, designed to activate only when the specific command was issued, remained dormant. Cut had been off the grid for years. And without a superior officer to deliver the Order, the chip simply never turned on.

Why Cut Didn't Execute Order 66

After the rise of the Empire, Cut was targeted for his deserter status. When Clone Force 99 came to Saleucami shortly after escaping Kamino, Cut warned them firsthand—things were changing fast. The Empire was tightening its grip. Chain codes were being issued, travel was being restricted, and clones like him were no longer welcome, even if they never fired a shot during the Purge.

Fives

The Death of Fives [4K HDR] - Star Wars: The Clone Wars

Fives was an ARC trooper who had seen more than his share of battles by the time the war entered its final stretch. But his most important mission began not on a battlefield, but in a medical bay—after a fellow clone, Tup, suddenly and inexplicably gunned down his Jedi General in the middle of combat. The incident was written off as a freak accident… but Fives knew better.

Driven by instinct and an unshakable sense of duty, Fives investigated Tup’s breakdown and uncovered something terrifying: a biological implant buried deep inside every clone’s brain. Kaminoan scientists called it an “inhibitor chip.” Fives realized that this chip wasn’t meant for the clones’ health or safety—it was a control mechanism, and whatever it was designed to trigger, it was going to be catastrophic.

As he dug deeper, Fives found himself being stonewalled and silenced. The Kaminoans, the Jedi Council, even Chancellor Palpatine himself—all played roles in keeping the truth hidden. In a desperate confrontation, Palpatine revealed his true identity as Darth Sidious and framed Fives as a rogue soldier suffering from paranoia and mental instability.

Alone and hunted, Fives removed his own chip to prove it was real—and then made one final attempt to reveal the truth. He reached out to his brothers, Captain Rex and Anakin Skywalker, in hopes of exposing the conspiracy before it was too late.

But time wasn’t on his side.

Before he could fully explain the scope of what he had uncovered, Fives was shot and killed by shock troopers. His death was written off as the tragic end of a clone who had “lost his mind.”

Grey

Grey initially followed Order 66 without hesitation, carrying out the directive that led to the death of Jedi Master Depa Billaba. He and his squad fired on her as she defended her padawan, Caleb Dume. The order was absolute, and the inhibitor chip ensured there was no hesitation, just swift, brutal obedience.

But over the next several days, something began to shift. As Grey and his men scoured the planet Kaller for the fleeing padawan, cracks formed in his certainty. The memory of killing the general he once respected began to weigh heavily on him. Doubt crept in. Guilt took root.

In Star Wars: Kanan – The Last Padawan #5, we see the full arc of Grey’s inner conflict. While his squad remained committed to the mission, Grey quietly unraveled. The more he thought about what they had done, the more he realized it wasn’t justice—it was murder. Caleb wasn’t a traitor. The Jedi weren’t the enemy.

When the clones finally caught up with the boy, Grey made a choice that very few clones ever could. He turned on his own men. In a final moment of clarity, he sabotaged the squad’s transport, helping Caleb escape the ambush. The resulting explosion killed him, but not before he redeemed himself.

Grey’s inhibitor chip didn’t fail. He overcame it. Not through outside help or surgical removal, but through the sheer strength of his conscience. In the end, he chose to make things right—even if it cost him everything.

Kix

After Fives was killed for uncovering the truth about the inhibitor chips, Kix didn’t let it die with him. He knew something was wrong. He had been there when Fives tried to warn Rex and Anakin. He had seen the desperation in his brother’s eyes. So Kix kept digging.

What Happened to KIX After the Clone Wars? (The Last Clone Trooper) - Star Wars [Updated 2021]

As a medic, he had access to information others didn’t. He pieced together what Fives had nearly exposed—that the clones had been implanted with chips designed to control them. And he got close. Too close.

Before he could share his findings with Rex or the Jedi, his investigation was discovered. Count Dooku, realizing how dangerous Kix had become, ordered his capture. Kix was abducted and placed into stasis aboard a Separatist transport, where he was kept in suspended animation for decades, effectively erasing him from the war before Order 66 was ever carried out.

He never got the chance to resist. He never even heard the command.

As revealed in the official short story The Crimson Corsair and the Lost Treasure of Count Dooku, Kix’s story didn’t end with the Clone Wars—but it didn’t continue during them, either.

By the time his ship crash-landed in the far reaches of the galaxy, the Clone Wars were long over. The Empire had risen and fallen. The Jedi were myths. When he was finally found by the pirate Sidon Ithano, he awoke to a galaxy he no longer recognized. He was the last living clone with the truth about the chips… but by then, it was too late to stop what had already happened.

It’s believed Kix later fought alongside Sidon’s crew, possibly even taking part in the Resistance’s final stand at Exegol. 

Rex

Rex Executes Order 66 [4K HDR] - Star Wars: The Clone Wars

We saw what happened to Rex the moment Order 66 was given.

He was standing with Ahsoka on the bridge of a Venator-class Star Destroyer, receiving a report from the Jedi Council. Just as the transmission ended, he received a private message directly from Palpatine: “Execute Order 66.” That was when it hit him.

Rex froze. He dropped the datapad in his hand. His body started shaking, and tears welled up in his eyes. He tried to resist, but the chip was already activating. He pulled his pistols and ordered the clones around him to execute Maul—and to find Ahsoka Tano. Even though she had already left the Jedi Order, the chip still classified her as a target.

Ahsoka didn’t know what was going on, but she managed to stun him before he could shoot. While the clones began hunting her through the ship, she dragged Rex to the medical bay and had the droid start scanning for the chip. It didn’t work at first—until she used the Force to locate it inside his head.

Together with the droid, she surgically removed the chip right there in the medbay. When Rex woke up, he was back in control. The first thing he told her was that the clones would be coming for them both—and that they didn’t stand a chance unless they found a way out.

From that point on, Rex and Ahsoka worked together to escape. The ship was in the middle of re-entering the atmosphere, spiraling out of control, and filled with soldiers trying to kill them. They freed Maul as a distraction, fought their way to a shuttle, and barely made it out alive.

When the cruiser crashed and the dust finally settled, Rex helped Ahsoka bury every clone that had died onboard. After that, he disappeared.

Years later, he resurfaced alongside Gregor and Wolffe, and eventually joined the Rebellion. But what matters most is that Rex did everything he could to resist the chip—and thanks to Ahsoka, he got a second chance.

Wolffe

We don’t know exactly when or how Wolffe’s inhibitor chip was removed. That part was never shown on-screen. What we do know is that by the time of Star Wars Rebels, he was living in isolation on Seelos alongside Rex and Gregor, both of whom had already removed their chips.

But according to Star Wars Rebels writer Henry Gilroy, Wolffe likely did carry out Order 66 and had the chip removed sometime afterward (as mentioned by Star Wars Explained on Twitter)

At some point between the Clone Wars and the rise of the Rebellion, Wolffe must have removed his chip too, or had it removed with help from Rex. He was no longer under Imperial control, but the effects of the war—and possibly the chip’s influence—still lingered. He was distrustful, cautious, and remained on high alert whenever outsiders appeared.

When the Ghost crew arrived, Wolffe was the one who initially reported their presence to the Empire. He believed they were a threat and didn’t want to risk exposing the others. Rex and Gregor convinced him otherwise, and he later apologized and helped fight back against the Imperial forces he had accidentally summoned.

By that point, Wolffe had fully broken from Imperial control. He didn’t play a direct role in the major battles that followed, but we know he stood by Rex and Gregor as part of their resistance cell. His loyalty to them never wavered.

In Legends

The Clones of the Star Wars Expanded Universe (now known as Legends) are often portrayed as more nuanced, complex characters than the ones in Canon; specifically, they are not always portrayed as being under complete control of their inhibitor chips.

Legends contains some interesting stories of Clone troopers that disobeyed Order 66. Let’s take a closer look.

Able

Able was stranded before Order 66 ever happened.

As shown in Star Wars: Empire #26, his transport crashed during a mission late in the Clone Wars, leaving him as the only survivor on the uninhabited planet Lubang Minor. With no way to contact the Republic, he was listed as missing and presumed dead. He ended up surviving alone on that world for over twenty years.

Because of that, he never received the Order. No transmission. No command. The inhibitor chip in his head was never triggered, and he had no part in the Jedi Purge.

Years later, Luke Skywalker and Rebel forces found him still wearing his clone armor and identifying himself by his number, CT-0000/1010. Luke explained what had happened while he was gone—how the Republic became the Empire, and how the Jedi were wiped out.

Able chose to fight again. But this time, it was with the Rebellion. He continued wearing his Phase I clone armor while serving under the Alliance, becoming one of the few surviving clones to take up arms against the Empire.

Hob-147

Hob-147 appeared in the Star Wars: Clone Wars Adventures comic series. He had been badly injured during a space battle and was presumed dead. Instead, he was rescued by a scavenger who took him aboard her ship and helped him recover.

While Hob was unconscious and healing, Order 66 was issued. He never received the transmission, and his inhibitor chip remained inactive.

When he eventually recovered, he learned that the scavenger had been hiding Jedi younglings aboard her ship—children who had escaped the Purge. At that moment, Hob-147 was faced with a choice. He still wore the armor of a clone trooper, and his training told him what those kids were supposed to be.

But he didn’t follow it.

He made the decision to protect them. Not because his chip failed or because someone removed it—but because he chose to. He helped the scavenger keep the younglings safe and refused to report them to the Empire.

Omega Squad

Omega Squad appeared throughout the Republic Commando novels. They were one of the few squads that didn’t carry out Order 66—not because of a chip malfunction, but because of personal loyalty and emotional bonds that went beyond programming.

The key reason was Darman. He had developed a close relationship with Jedi General Etain Tur-Mukan, which eventually turned romantic. That connection changed how he—and the rest of the squad—viewed the Jedi. By the time Order 66 was issued, they no longer saw the Jedi as traitors, but as allies, friends, and in Darman’s case, someone he loved.

When the order came through, Omega Squad refused to comply. They didn’t turn on Etain. Instead, they protected her and helped shield Jedi targets from the initial wave of the Purge.

Their resistance didn’t last forever. Etain was killed shortly after Order 66, trying to protect civilians during the chaos. Darman, devastated by her death and now the father of her child, ended up staying behind on Mandalore to raise their son. The rest of the squad was scattered.

Maze

Maze was an Alpha-class ARC trooper featured in the Republic Commando novels. Like the rest of the Alphas, he had been trained directly by Jango Fett and was not subjected to the same behavioral modifications as regular clone troopers. That made him independent, critical, and fully capable of thinking for himself.

He developed a strong respect for the Jedi over the course of the war—particularly the ones who treated clones as individuals rather than assets. Maze was also known for reading in his spare time, something unusual among clones and another sign of his self-awareness.

When Order 66 was issued, Maze didn’t follow it. He refused to turn on the Jedi, acting on his own judgment rather than any implanted programming. He wasn’t alone—many ARC troopers, especially those from the Alpha class, ignored the order altogether for the same reason.

Null-Class ARC Troopers

The Null-Class ARC troopers were introduced in the Republic Commando novels. They were the earliest batch of ARC troopers—clones with enhanced cognitive and emotional development, but deemed too unstable by Kaminoan standards. The Kaminoans planned to terminate them, but Mandalorian trainer Kal Skirata intervened and took them in as his own.

Because they were never fully integrated into the Grand Army and answered only to Skirata, they were never truly under Republic control. They didn’t follow orders from Jedi generals, and they didn’t operate under standard protocols.

When Order 66 was issued, the Nulls rejected it without hesitation. They didn’t trust the Republic, they didn’t follow the Jedi hierarchy, and they were fully aware of the chips and the contingency plans long before the order went out. Loyalty to Skirata came first—and they walked away from the war when the time came.

Yayax Squad

Yayax Squad also appeared in the Republic Commando novel series. They were trained under Kal Skirata, just like the Nulls, and held close ties to him throughout the war.

When Order 66 was issued, they chose not to carry it out. Instead, they deserted the Republic and went straight to Mandalore to regroup with Skirata and other clones who had broken away. Their loyalty was never to the Chancellor or to the chain of command—it was to the man who had raised and protected them.

Yayax Squad’s defection was quiet, but absolute. Like many of Skirata’s men, they had already seen where the war was heading—and they wanted no part in the Empire that came next.