TL;DR
- Oracle is the supercomputer that controls the Cassiopeia ship in Directive 8020.
- You get two linked choices early in Episode 1: consult Oracle, then reboot it.
- Consulting Oracle is the better pick. Skipping it locks you out of the reboot choice.
- Rebooting Oracle is generally the safer choice for a smooth first playthrough.
- Not rebooting causes a faulty door to block Carter’s path later and forces a QTE.
- For 100% completion, refusing the reboot reveals a hidden consequence called “Door Stuck.”
One of the very first decisions you face in Directive 8020 involves the ship’s AI, Oracle. It happens early in Episode 1, called Little Star, and it sets the tone for how choices work throughout the entire game. If you are confused about what to do or what the consequences are, this guide covers everything.
If you are still setting up the game on PC, check out our Directive 8020 best PC settings and optimization guide to get the smoothest experience before you start playing.
What Is Oracle in Directive 8020?
Oracle is the central supercomputer aboard the colony ship Cassiopeia. It controls all the ship’s major subsystems. When a mysterious meteorite strikes the ship at the start of Episode 1, it throws everything into chaos. The two crew members awake at the time, Carter and Simms, need to figure out how to assess the damage and get things under control.
That is when the first choice appears.
Should You Consult Oracle in Directive 8020?
Yes, you should consult Oracle.
After the meteorite hits, Simms asks Carter whether to speak to Oracle for help or go assess the damage themselves. Here is what happens with each option:
Option 1: Consult Oracle (Recommended)
Choosing this option takes Carter and Simms to Oracle’s chamber. It introduces you properly to the AI and triggers a second, more impactful choice about rebooting. This is also where the game introduces the Turning Point mechanic for the first time. Consulting Oracle is the better choice. It opens up more of the story and keeps your options open.
Option 2: Fix It Ourselves (Not Recommended on First Run)
If you skip Oracle and decide to fix the damage directly, Carter and Simms head out to assess things on their own. This does not break the game, but it has a notable downside. You will miss meeting Oracle for the first time, and you will be locked out of the reboot decision entirely. The reboot choice only appears if you consulted Oracle first.
Skipping Oracle does not change the main story, but you lose access to an important branch. For a first playthrough, always choose to consult Oracle.
Should You Reboot Oracle in Directive 8020?
Yes, you should reboot Oracle on your first playthrough.
After Carter asks Oracle for a damage report, the AI requests a full system reboot to accurately assess the damage and fix any anomalies in its subsystems. This is the Turning Point choice, and it has real consequences. Here is what each option leads to:
Option 1: Authorize the Reboot (Recommended for First Run)
Allowing Oracle to reboot fixes its subsystems and clears any errors. After the reboot, Oracle detects an unknown life form aboard the ship. Carter and Simms then continue to assess the damage and head out on a spacewalk to repair the hull. This is the smoother path for a first playthrough. The reboot removes obstacles that would otherwise block your way later.
There is a trait effect too. Choosing to reboot increases Carter’s Cautious trait and decreases his Decisive trait. Keep that in mind if you are shaping Carter toward a specific destiny.
Option 2: Delay the Reboot
If you choose not to reboot Oracle right away, the consequences are not immediate. Things feel fine at first. But once Carter and Simms complete the spacewalk repairs and return inside, things get dangerous. Something starts chasing Carter through the hallways. Because Oracle was not rebooted, one of the electronic doors becomes faulty and blocks Carter’s path. This forces a button-mash QTE to force the door open before Carter can reach the Crew Monitoring area.
Delaying the reboot increases Carter’s Decisive trait and decreases his Cautious trait.
Which Choice Is Best for 100% Completion?
This is where things get interesting. If you are going for full completion and want to see every consequence and hidden outcome, the answer flips.
For 100% completion, refuse the reboot. Only by refusing will you trigger a hidden outcome called Door Stuck, which is one of the branching consequences tracked in the game’s story tree. You will need to see this on at least one playthrough to fully complete the game.
However, for a clean and enjoyable first run, reboot Oracle. The faulty door and forced QTE that come from refusing the reboot can catch new players off guard and feel frustrating without context. Save the refusal for a second run when you are specifically hunting hidden consequences.
Summary: What Should You Choose?
- First playthrough: Consult Oracle → Authorize the Reboot. This is the smoother, safer path.
- Completionist run: Consult Oracle → Delay the Reboot. This unlocks the hidden Door Stuck consequence.
- Skipping Oracle entirely: Only worth doing on a second or third run to see the alternate path. You miss the reboot choice completely.
How the Turning Point System Works Here
The Oracle decision is also the game’s first real introduction to the Turning Point mechanic. Turning Points are key decisions that branch the story in meaningful ways. You cannot revisit them freely until you complete the game with at least one character alive. Once you finish your first playthrough, you can go back through the Story Tree and replay specific Turning Points to explore alternate outcomes without starting over from scratch.
This means there is no pressure to get everything right on your first run. Make the choice that feels natural, or follow this guide for the recommended path, then revisit later to see what you missed.
Note
The Oracle choice is a great example of how Directive 8020 handles decision-making. On the surface, it looks like a simple yes or no. But underneath, it shapes Carter’s personality traits, unlocks or locks off story branches, and has a practical impact on gameplay moments later in the episode. It is well worth consulting Oracle and authorizing the reboot on your first run. Then, when you come back for completionist cleanup, refuse the reboot and see what the game has hidden for you.
These early choices are just the beginning. Directive 8020 has eight full episodes of branching decisions, character deaths, and alternate endings to work through.
