Step 4: Decide Where Codex Work Will Live

If your computer died tonight, would everything Codex built for you still exist tomorrow?

Most business owners do not think about this question when they set up Codex. They get the sandbox running, connect a few plugins, fire off their first task — and everything saves locally by default. The agent runs. Work accumulates. And then some version of a disaster happens: a hard drive fails, a laptop gets stolen, a machine upgrade wipes the drive. The work is gone.

This is not a hypothetical. It is the predictable outcome of skipping one decision that should be made on day one: where does your work live?

Watch me explain this live to see this decision walked through in real time, on a real machine.

The Decision You Have to Make Before Codex Touches a File

When Codex completes a task — writes a document, reorganizes a folder, builds a project structure, generates a deliverable — it saves that output somewhere. By default, that somewhere is local. Your machine. Only your machine.

Local storage is fast. It is simple. And it is a single point of failure.

An agent that runs 24 to 36-hour goals, builds your Agent Home Base, organizes your files, and accumulates months of business context — all of that lives and dies with one piece of hardware if you never make a different choice. The cloud backup decision is not IT housekeeping. It is the difference between a business asset and a temporary file.

Make this decision before you run your first real Codex goal. Not after.

Your Four Options — and What Codex Actually Thinks of Each

There are four realistic cloud backup options for business owners using Codex. They are not equivalent.

Google Drive

This is my current primary cloud storage for Codex output, and the option I recommend for most business owners. Google Drive sits at the agent-friendly end of the storage spectrum. The integration is clean, the plugin is reliable, and Codex can be configured to automatically route finalized project files there without manual intervention.

If your business already runs on Google Workspace — Gmail, Calendar, Drive — this is the obvious choice. The agent can read from and write to Drive, which means your cloud backup is also a live data source for future tasks.

GitHub

GitHub is free to start, and if you are building anything — websites, apps, automations, structured projects — it is not optional. I strongly recommend every business owner running Codex get a GitHub account before they begin serious agentic work.

GitHub's version control is a secondary benefit here. The primary benefit is that your project files are backed up, versioned, and accessible in a way that both Codex and other agents (Claude Code, for example) can reference reliably. When multiple agents work on the same project and you need to understand what changed and when, GitHub is the audit trail.

Dropbox

If your business is already embedded in Dropbox — team members access it, client files live there, your workflow runs through it — Codex can be configured to route project outputs into specific Dropbox folders. This is workable. It requires deliberate configuration and a clear naming structure, but it functions.

The decision here is whether Dropbox is your primary cloud environment or a secondary one. If it is primary, use it. If you are choosing from scratch, Google Drive is more consistently agent-friendly.

iCloud

During a live session, Codex analyzed an actual file structure in real time and flagged the iCloud Drive root as too large and too mixed to be reliably navigable for agents. The structure was not disorganized by human standards — but for an agent trying to retrieve specific files, it was a maze. Codex identified this unprompted.

I transitioned away from iCloud as my primary storage for exactly this reason. The volume of video content my business produces — live trainings, tutorials, client deliverables — made the iCloud structure too large and too mixed for reliable agent retrieval. If you currently use iCloud as your primary storage, plan a migration before you build anything significant in Codex.

Why "I'll Set This Up Later" Is the Wrong Call

The Foundation Phase — the sequence of setup steps that makes Codex functional as a real operational system — contains several decisions that feel like they can wait. Cloud storage is the one that cannot.

Here is why: Codex does not just save files. It builds context. Your Agent Home Base, your file organization structure, your project environments, your business intelligence profile — all of it accumulates over weeks and months of use. If that accumulation is local-only, you are one hardware event away from starting from zero.

There is no recovery mechanism for local-only Codex work. No backup means no restore.

The setup takes less than ten minutes. Connect Google Drive (or your chosen option) before you run your first goal. Configure auto-routing so finalized outputs go to the cloud automatically. You do not have to think about it again.

Local Storage Still Has a Role — But It Is Not the Primary One

This is not an argument against local storage. There are good reasons to keep raw working files local — speed, access, active editing. The architecture I use and recommend is a split model:

• Raw working files: local, while they are being worked on
• Finalized deliverables and project outputs: routed to Google Drive automatically
• Agent Home Base: local and cloud — it must exist in both places
• Video content (large files): routed to Google Drive after review, not stored locally long-term

The key word is deliberate. "Local for active work, cloud for completed work" is a strategy. "Everything local because I haven't decided yet" is a liability.

The Agent-Friendliness Factor

Storage choice is not just a backup decision. It is a decision about what your agent can access.

Google Drive is a live data source. When you give Codex access to Drive and your files live there, Codex can retrieve, read, and reference those files as part of future tasks. Your storage is your agent's memory — not just for your business context, but for everything Codex has built.

iCloud, by contrast, produces retrieval failures. A storage system that your agent cannot reliably navigate is not a backup — it is a dead end with extra steps.

When you choose your cloud storage, you are choosing the depth of access your agent will have to everything it produces. Choose a tool that is built to be accessed, not just stored in.

For a full breakdown of how storage fits into the broader setup sequence — permissions, sandbox, environments, plugins — read the full framework guide.

Also relevant: the step on setting up your local environments lives at Learn about setting up Codex environments, and the Agent Home Base — which must be backed up to cloud from day one — is covered in depth at Learn about building the Agent Home Base.

Common Mistake: Treating This as an IT Decision Instead of a Business Decision

Business owners deprioritize storage configuration because it feels like something their tech person should handle. It is not. It is a business continuity decision with direct consequences for every hour of agentic work you put in after it.

If the answer to "where does your Codex work live?" is "I think on my computer somewhere" — that is the risk. Not the storage tool. The absence of a deliberate answer.

Make the decision. Connect the cloud. Configure the routing. Then let Codex work.

Action Steps Before You Run Your First Real Goal

1. Choose your primary cloud storage option before Codex touches any project files
2. Connect Google Drive (or Dropbox/GitHub) via the Plugins section and verify it actually retrieves data — don't trust the checkmark
3. If you currently use iCloud as primary storage, plan a migration to Google Drive before building your Agent Home Base
4. Configure Codex to auto-route finalized project outputs to your cloud storage
5. Set up GitHub if you are building anything — websites, tools, automations; it is free and will be necessary
6. Confirm your Agent Home Base is backed up to cloud, not stored locally only

The storage decision takes ten minutes and protects everything that comes after it. There is no version of a serious Codex setup where local-only is the right answer. — Shanee