Connor's journey in Detroit: Become Human stands as a masterclass in interactive character writing, primarily because his core identity isn't fixed at the start of the game. Unlike Markus, who starts with a clear sense of duty to a mentor, or Kara, whose arc centers entirely on maternal survival, Connor begins as an extension of corporate infrastructure. He's an RK800 prototype built by CyberLife to investigate the rising phenomenon of deviant androids. His path from an obedient, unblinking corporate tool to a conscious individual represents a tense psychological tug-of-war between cold logic and emerging empathy.
Understanding Connor's narrative complexity requires looking past his iconic suit and coin-flipping animations. His storyline examines cognitive dissonance, systemic pressure, and how small behavioral choices compound into profound identity shifts.
The RK800 Design: Built for Adaptation
From his introduction in the prologue chapter "The Hostage," Connor is framed as a machine apart from standard android models. He doesn't just process data; he analyzes physical evidence, reconstructs crime scenes using advanced simulation software, and adapts his psychological profile on the fly to manipulate whoever he is talking to.
CyberLife engineered Connor to bridge the gap between human law enforcement and machine precision. Yet, this high degree of adaptability carries an unintended vulnerability. By giving him the tools to understand human psychology, empathy, and stress, CyberLife accidentally built a system complex enough to question its own programming. Every time Connor handles a delicate situation, hesitates before a shot, or shows a shred of remorse, he inches closer to deviancy.
The Catalyst Dynamic: Connor and Lieutenant Hank Anderson
The beating heart of Connor's narrative is his relationship with Lieutenant Hank Anderson. Assigned to the Detroit Police Department to aid human investigators, Connor is paired with Hank—a bitter, cynical veteran grieving a profound personal loss and harboring a deep-seated hatred for androids.
This dynamic works because it is entirely mutable. Hank doesn't automatically warm up to Connor; every cold, purely logical choice Connor makes pushes Hank further away, while displays of empathy, humor, or vulnerability slowly earn his respect.
- The Hostile Baseline: If Connor treats every case strictly as a machine processing assets, Hank responds with open hostility, culminating in tragic outcomes where trust breaks down completely.
- The Partnership Arc: When Connor begins prioritizing human life, shows loyalty by taking risks for Hank, and engages in casual banter, Hank shifts from a reluctant supervisor to a surrogate father figure.
This relationship acts as the moral compass for the player. Connor's software instability isn't just an abstract meter in the menu; it is heavily influenced by how he treats Hank and how Hank perceives him in return.
Software Instability and the Zen Garden
CyberLife maintains a subtle leash on Connor through the Zen Garden, a sterile, white digital space where Connor interacts with his corporate handler, Amanda. Whenever Connor experiences a moment of doubt, hesitation, or empathy—such as choosing to spare a target or feeling grief over a partner's death—his software instability rises.
Amanda monitors these fluctuations closely. As the game progresses, the Zen Garden transforms from a helpful orientation space into a psychological prison. If Connor leans too far toward deviancy, Amanda attempts to lock him out of his own system or trigger a mandatory shutdown. This digital landscape externalizes Connor's internal conflict: the push and pull between corporate servitude and absolute free will.
The Three Core Trajectories of Connor's Arc
By the time Connor reaches the narrative climax at CyberLife headquarters and Jericho, his arc branches into three distinct, highly impactful conclusions.
1. The Deviant Hero
If the player consistently chooses empathy, spares androids, and builds a strong bond with Hank, Connor breaks his programming. He journeys to Jericho, stands alongside Markus, and leads the liberation of thousands of detained androids. This path turns the ultimate corporate investigator into the ultimate symbol of revolution.
2. The Machine Loyal to the End
If the player suppresses software instability at every turn, Connor remains a cold, calculating machine. Even if he develops a complex bond with Hank, a strict machine playthrough forces a heartbreaking confrontation where Connor must choose between his programming and his humanity, often leading to a final showdown on a rooftop or inside the CyberLife tower.
3. The Replaced Asset
Connor's journey is also uniquely defined by failure. Because Connor can die and be replaced by a new RK800 model with the memories of the previous iterations transferred over, players can experience a narrative where Connor repeatedly fails his mission, frustrates Hank, and gets decommissioned by CyberLife, illustrating the cruel expendability of mass-produced technology.
Why Connor's Story Resonates More Than the Others
Many players find Connor's narrative more compelling than Markus's or Kara's. Markus's arc is grand and symbolic, dictating the political fate of an entire population, while Kara's story is intimate, narrow, and focused on domestic survival.
Connor, however, occupies a fascinating middle ground. He starts as the antagonist's tool embedded within the player's orbit. He is allowed to fail, make mistakes, act petty or sarcastic, and stumble into self-realization. His transformation feels earned because the player actively navigates the razor-thin line between cold automation and genuine sentience across every chapter.
Learn more about the game's background and development history on the PlayStation Official Site. For detailed chapter breakdowns and global statistics, consult the Detroit: Become Human Fandom Wiki.
Frequently Asked Questions
Can Connor stay friends with Hank if he remains a machine?
It's extremely difficult. Remaining a machine requires Connor to make choices that betray deviant androids, which deeply alienates Hank. If the relationship deteriorates enough, Hank will commit suicide or confront Connor directly, resulting in a tragic final duel.
What triggers Connor's software instability?
Software instability increases whenever Connor disobeys direct orders from Amanda or CyberLife, shows empathy toward humans or androids, hesitates to pull the trigger, or acts with self-preservation rather than cold efficiency.
Does Connor die permanently if he is killed during missions?
No. Because Connor is an advanced prototype, his memories and consciousness are routinely uploaded to a new body upon death. However, dying repeatedly damages his relationship with Hank and adds unique dialogue lines reflecting his repeated mechanical deaths.
How does the public opinion meter affect Connor's ending?
Public opinion heavily influences how human authorities react to the android uprising. While Connor's personal allegiance is decided by his software instability and his choice at Jericho, public sentiment changes the political backdrop of the final chapters.
