“The Sehlat Who Ate its Tail”

Star Trek: Strange New Worlds delivers James T. Kirk’s first taste of being Captain when a crisis forces him to take command of the Farragut.

James T. Kirk’s recurring presence in Strange New Worlds remains a contentious choice. For some, he’s a distraction from the show’s original premise, drawing focus away from the ensemble cast meant to anchor Pike’s tenure aboard the Enterprise. That concern isn’t unfounded. Kirk’s screen time often comes at the expense of the development of other characters. His involvement also blurs the show’s mission statement. Is this a chronicle of Pike’s crew, or a slow-burn origin story for Kirk’s eventual rise to command?

Controversy aside, Kirk is part of the show, which makes it both valid and arguably necessary to tell stories that develop him into the Captain seen in The Original Series. This episode places him in command during a crisis, testing his ability to make difficult decisions and confront his own readiness for leadership. It’s a formative scenario that offers long-time fans fresh insight into a familiar character, while giving newer viewers a chance to see this version of Kirk evolve under pressure.

Captain James T. Kirk is a cultural icon, but the popular image of him as a reckless hothead who defies orders and wins through sheer bravado is flatly wrong. It’s a distortion that ignores the actual character portrayed in The Original Series. Kirk is a seasoned, strategic leader who takes risks only after weighing the odds and understanding the strengths of his crew. He’s not impulsive. He’s deliberate. The show may have leaned into high-stakes adventure and unpredictable encounters, but Kirk never operated with a flagrant disregard for rules. He respected the chain of command, understood the burden of responsibility, and made decisions grounded in experience, not ego.

The episode opens by leaning into the familiar but flawed perception of Kirk. His log entry reveals boredom with routine duty, frequent disagreement with his Captain’s orders, and a belief that the rule book would be better if he wrote it himself. He’s portrayed as an adventure-hungry officer who assumes command will come naturally and that nothing can shake him. It’s a clear setup for the lesson he’s about to learn, and it marks the beginning of his arc. It also feels like a statement of intent from the showrunners, a promise to correct the record and present a more faithful, grounded version of Captain Kirk while exploring his origin.

Kirk’s arrogance is swiftly tested when a sudden attack leaves his Captain critically injured, placing him in command of the Farragut. The Enterprise responds to the distress call and sends reinforcements. Spock, Chapel, Scotty, Uhura, and La’an beam aboard to assist, though La’an returns to the Enterprise just before it is captured by the scavenger vessel. Kirk is left in charge with no backup, flanked almost entirely by his future crew. The setup is unmistakably meta. It plays like a proof-of-concept for a rebooted Original Series, quietly asking whether audiences are ready to follow this version of Kirk into his own show. Whether intentional or not, it feels like a test run for a dynamic that could be spun off once Strange New Worlds comes to an end.

Putting aside the out-of-universe implications, Kirk is thrust into his first real command with an experienced crew looking to him for direction. But the emotional gravity of the situation is left largely unexplored. The Enterprise officers fill every key role, leaving the Farragut crew as silent bystanders in their own crisis. One bridge officer speaks up now and then, but only to support the conversation already dominated by the Enterprise team. Meanwhile, the Farragut has suffered a catastrophic blow. Their chief medical officer is dead, their Captain is fighting for her life, and many of their colleagues are gone. These are people who have served together, built trust, and shared the kind of camaraderie that defines Starfleet crews, as seen repeatedly on the Enterprise. Yet their grief is invisible. No one mourns. No one hesitates. No one questions the loss.

Kirk never acknowledges it either. He is focused, determined, and locked into the task at hand. That makes sense for someone trying to prove himself, but it also reveals a blind spot. Leadership is not just about making decisions. It is about understanding the emotional state of those who follow you. If Kirk had been shown wrestling with the weight of their loss, or even momentarily distracted by concern for his friends, it could have added a powerful layer to his arc. It would have exposed his vulnerability and highlighted the emotional toll of command. A moment of hesitation, a flash of guilt, even a quiet exchange with a grieving officer could have transformed this into something more than a tactical exercise as well as acknowledging the Farragut crew as a lived-in team who spend every day together. It could have been a lesson in empathy and the cost of being the one who gives the orders when lives are on the line.

Even with its missed opportunities, this episode is a strong showcase for Kirk as a character. The early formation of dynamics with his future crew is compelling, and Paul Wesley delivers his most assured performance in the role to date. He captures Kirk’s familiar bravado but tempers it with vulnerability, hesitation, and self-doubt. These qualities are not just acted. They are written into the fabric of the episode. The script gives Kirk room to stumble, reflect, and grow, presenting him as someone still learning what it means to lead.

The interplay between writing and performance is especially effective in the quieter moments. Wesley’s hesitation before issuing orders, his reluctance to sit in the Captain’s chair, and his visible calculation of risk all speak to a character who is beginning to understand the weight of command. The writing reinforces this with a well-timed narrative beat. Kirk’s gamble with the engines seems to succeed, and he finally takes the chair. Just as the moment begins to feel earned, the engines fail. The victory is short-lived, and the consequences arrive immediately. It is a clear lesson, delivered without fanfare. Leadership is not about confidence or bravado. It is about accepting consequences, listening to others, and recognizing that the chair is a responsibility that must be earned and respected.

The trial by fire is often a compelling way to build character as it encourages them to learn and grow under pressure while understanding the actual consequences of their decisions and actions. Prior to this experience, Kirk has always had a safety net of some sort whether that be the theoretical framework of Starfleet Academy courses or an experienced Captain giving orders and bearing the weight of responsibility for what follows. This is a James T. Kirk who cheated on the Kobayashi Maru test at Starfleet Academy to make a no-win scenario winnable so he is of the belief that dogged determinism is always the best approach and gains a very harsh lesson in reality through this situation. Though it should be noted that this episode takes place at least two years after the Farragut encounters the vampiric cloud creature depicted in The Original Series episode “Obsession” so should have some experience of blaming himself for lethal consequences.

This episode takes place at least two years after the Farragut’s encounter with the vampiric cloud creature in The Original Series episode “Obsession.” If that event is still part of Kirk’s history, it should inform his response to the crisis. Referencing it could have added emotional depth and continuity, especially given the parallels in responsibility and loss. Kirk’s indecision here could have been framed as a consequence of lingering guilt; his hesitation rooted in a past disaster he blames himself for. While the audience never witnessed that original encounter, drawing on it could have enriched the tapestry of who Kirk is, showing how past trauma shapes present leadership. It would also reinforce the idea that starships routinely face unpredictable and dangerous situations, with the key difference here being that Kirk is no longer following orders. He is the one making them.

Yet Kirk’s early arrogance in this episode suggests that the Farragut incident never happened, at least not in the way “Obsession” portrayed it. That reinforces the notion that this is a new timeline. Despite repeated claims from the producers that Strange New Worlds exists within the same continuity as The Original Series, the depiction on screen suggests a departure from that timeline. Characters are reimagined, relationships are restructured, and chronology is reshaped. Scotty, for example, is portrayed as younger than Kirk, despite canon placing him as older. These changes allow for fresh storytelling, but they also confirm that this is not the same timeline. The contradiction between what is claimed and what is depicted undermines the integrity of both approaches.

Kirk’s arrogance works well in the context of the situation. He believes that taking risks is the way to win and treats the upper limits of the ship’s capabilities as flexible rather than fixed. It is a dangerous mindset, because eventually he will be wrong and the consequences will be catastrophic. Scotty is the one who pushes back, clearly articulating the reality of what Kirk is asking. His objections are heard but ultimately ignored.

From Scotty’s perspective, this is a compelling dilemma. A boss is telling him to do something he is certain will not work. That dynamic is deeply relatable. Most people have experienced the frustration of being given an instruction they believe will fail, voicing that concern, and being told to do it anyway. Scotty knows he has to follow orders, but he also knows what failure looks like, and he cannot stay silent. His resistance characterises him as stroppy and insubordinate in moments, but it is grounded in experience and fear.

That reaction makes sense when considering Scotty’s recent history. He lost his ship to the Gorn and is still processing the trauma of that loss. The current situation mirrors that experience, and he sees Kirk’s command style as a path toward repeating it. More than anyone else, Scotty is distressed by the possibility of the scavenger ship catching up with them and tearing them apart. He cannot bear the thought of another crew being lost, and he is not emotionally equipped to play a role in that outcome. Even though he has been repeatedly assured that the loss of the Stardiver was not his fault, believing it is another matter entirely. Kirk’s apparent recklessness triggers him in deeply visceral ways.

That emotional tension is resolved when Kirk declares that he has no intention of abandoning the Enterprise just to save themselves. Scotty responds by saying he “needed to hear that.” It is a moment that signals his shift from resistance to trust. Kirk’s statement of intent reassures him that this is not a repeat of the Stardiver, and it allows Scotty to back Kirk as a captain who has his priorities in order.

The moment of indecision for Kirk is well handled. Spock nominating himself to speak with him after the other Enterprise officers discuss removing him from command provides the perfect opportunity to set up the future friendship that will come to define them both. In The Original Series, Kirk relies on Spock for clarity, logic, and a dispassionate perspective to inform his decisions. The beginnings of that dynamic are visible here. Kirk admits he has no idea what to do and laments the absence of his Captain, wishing she were there to make the decision for him.

He references an ongoing game of chess between them, believing he was close to winning. In that game, he had her in a corner and was trying to anticipate her next move. It’s an apt analogy for the current situation, as he is now trying to imagine what she would do in his place. Spock reminds him that the decision is his to make and that people are waiting for it, but Kirk can only focus on how unprepared he feels. He compares himself to a dog that catches the car it has been chasing and then has no idea what to do next. Kirk admits that he has been laser focused on becoming a Captain, without truly considering the reality of achieving it. Now that he has, the weight of command is sobering, and the failure of his gamble has shaken his confidence to the point of questioning whether he is cut out for the job.

Spock responds with a similar Vulcan story, “The Sehlat Who Ate its Tail,” and points out that Kirk has a key advantage over the animals in those stories. His instincts allow him to adapt to change and rise to the challenge. It’s a tenuous link, but the strength of the performances makes it land. Kirk regains his composure and returns to the task at hand, his earlier swagger now tempered by the benefit of bitter experience

From this point, the solution to the problem comes fairly easily, but it serves as a strong example of the crew working together under more confident leadership than they had before. The moment is clearly meant to show that Kirk has grown, that he now understands the value of collaboration and is capable of inspiring those around him. However, the execution undercuts that message. The point would have been stronger if the other characters had contributed ideas, with Kirk selecting the best suggestions to form a cohesive plan. Instead, he tells everyone what to do and they carry out his orders without question.

It plays as if Kirk has become a better leader by drawing on the skills and knowledge of his crew, but the reality is that he has already made up his mind and simply delegates tasks. What happens on screen runs counter to the lesson Kirk has supposedly learned, which weakens its impact. That said, the moment still works. Paul Wesley’s performance is charismatic and assured, and the enthusiasm he brings is infectious. With a few small tweaks, the scene could have achieved something truly resonant.

The action aboard the Enterprise is far less meaningful. The crew faces a dire situation, with an umbilical cord draining the ship’s power and a boarding party attacking. Pike and La’an work to repel the invaders and detach the umbilical, while others coordinate their escape. Pelia’s idea to use 1980s landline phones to set up a temporary communications network is undeniably charming. However, it clashes with the established logic of the ship’s technology. The Enterprise has communication panels built into the walls, and it stands to reason that would be wired to resist interference and maintain internal connectivity. The scene overlooks these basic capabilities in order to deliver a dose of retro ingenuity.

It is a fun idea, and it makes clever use of Pelia’s age and eccentricity. Many viewers will find it entertaining, and it adds a moment of levity to an otherwise tense sequence. However, it breaks the internal logic of the show by ignoring the fundamental functions of the technology at play. The result is a moment that feels inventive on the surface but undermines the credibility of the

There are also resources available to the crew that go unused. One notable example is the absence of Batel. She was aboard the Enterprise in the previous episode while the crew was on a mission, and the implication was that she remained on the ship to monitor her condition before assuming command of a new vessel. This scenario would have been an ideal opportunity to make use of an additional Captain. Batel could have taken the bridge while Pike was repelling the invaders and Una was focused on establishing communications. Even if she were trapped in Pike’s quarters, a single line of dialogue could have clarified her status.

Her absence does not detract from what is shown on screen, but it introduces a continuity gap that could have been easily addressed.. If external factors such as budget constraints prevented Melanie Scrofano’s involvement, acknowledging that limitation in-universe would have preserved narrative cohesion. As it stands, Batel’s unexplained absence is a missed opportunity to enhance the episode with a character who could have added depth and strategic value to the crisis.

The reveal that the scavengers are Human opens the door to a compelling discussion about morality. Kirk is disgusted with himself for celebrating the destruction of their ship. His celebration was rooted in overcoming overwhelming odds and achieving victory against a hostile attacker, but in that moment, he forgot that he was fighting people.

This realisation hits him hard. His decisions led to their deaths. Pike tells him that empathy for adversaries is part of the job, and that it is not conditional. As bad as Kirk feels, the fact that he feels that way is what sets him apart from those who attacked them.

Kirk points out that the attackers being Human somehow makes it worse, likely because it holds a mirror up to him. The scavengers descended from a mission that once represented the best of Humanity, launched to ensure the species could survive even if another global conflict like the Third World War occurred. At some point after launch, the ship disappeared, and its people began a descent into corruption that led to the attackers they have now become. Kirk worries that anyone has the potential to end up like them, but Pike has faith that they are better than that precisely because they worry about that possibility. Learning that they are not so different from their enemies is an important lesson for Kirk. He is asked to internalise the weight of the decisions he makes, and Pike’s experience as a Captain gives the moment real gravity. He assures Kirk that self-doubt is not unique to him, and that part of the job is making decisions they will regret and have to live with. It is a lesson Pike learned, and one every Captain must learn eventually.

The moral discussion is engaging and well performed, but the reveal of the attackers’ identity is rushed and underdeveloped. Their origin is quickly summarised in dialogue, raising open questions about what could prompt such profound corruption. The episode offers no answers. It introduces a concept far too large to resolve within the final act. The core narrative is a simple trial by fire for Kirk, and that could have been achieved with an alien attacker whose motivations were basic. Instead, the reveal demands exploration that never comes and is left as an enduring mystery.

Exploring this premise would require an entirely different story, one built around the identity of the scavengers and the potential for Humans to be corrupted under extreme circumstances. It could have contrasted the fall of a pioneering space mission with the evolved ideals of the Federation, asking whether progress is truly permanent or always at risk of regression. That kind of story would echo Star Trek’s legacy of moral allegory, turning a cautionary tale into a mirror for the present. Instead, this compelling idea becomes a forgotten footnote in an origin story about Kirk. Ending with such a big unexplored question does not diminish the quality of what came before, but it does distract from the true aim of the episode.

In the end, this episode succeeds as a character study of James T. Kirk, offering a layered and often compelling look at his early steps toward command. It stumbles in its broader ambitions, introducing ideas too large to resolve and sidelining characters who could have added depth. But its core remains intact. Through hesitation, missteps, and hard-won clarity, Kirk begins to understand what it means to lead, not just to give orders, but to carry their weight.

---

Verdict

A strong episode that succeeds as a character study of James T. Kirk, presenting a grounded and emotionally resonant look at his early steps toward command, with confident storytelling and assured performances throughout.

We’d love to know your thoughts on this and anything else you want to discuss. You can find us on Facebook, Twitter, BlueSky and Discord or just leave a comment in the comment section below. You’ll need an account for Disqus but it’s easy to set up. Don’t forget to share your rating in the “User Review” box.