Most business owners open a new tool and skip the settings screen entirely. They go straight to the thing they want to do. With Codex, that instinct costs you — sometimes your entire credit balance, sometimes a 36-hour goal that dies halfway through because your laptop went to sleep.
These six settings are not preferences. They are operational decisions. Each one has a consequence if you get it wrong, and none of them are obvious without context.
For the complete framework behind all of this, read the full guide. You can also watch me explain this live to see the settings screen walked through in real time.
Where to Find These Settings
Inside Codex, go to Settings, then Settings again. Yes, it is nested. You are looking for the general configuration panel — not the Sandbox settings or Plugins (those are separate and covered in adjacent steps). This is the top-level behavioral control panel for how Codex runs on your machine.
These six settings live there. Here is what each one actually means and why it matters.
The Six Settings
1. Work Mode: Set It to "Coding" and Leave It There
This surprises people. If you are a business owner doing email, project management, client work — not coding — why would you set Codex to "Coding" mode?
Because "Coding" mode is how Codex operates at its full agentic capability. It is the mode that allows Codex to execute tasks, write files, run commands, and function as an autonomous operator. The name is misleading. The function is not. Other modes constrain what Codex can do. Coding mode does not. Leave it there regardless of what kind of work you are giving Codex.
2. Show in Menu Bar: Toggle On
This puts Codex at the bottom of your screen so you can access it without hunting through your applications. A small thing, but when you are mid-task and need to check on a running goal or issue a quick instruction, not having to dig for the app window matters. Toggle it on when you set up the rest of these settings.
3. Windows Users: Always Run as Administrator
If you are on a Mac, this does not apply. If you are on Windows, this is non-negotiable. Every time you open the Codex app, right-click it and select "Run as Administrator." Without it, Codex will hit permission walls on your own machine — blocked from accessing folders, running commands, or writing files it has every right to access. It will look like Codex is broken. Codex is not broken. Windows is restricting it because you did not escalate its privileges.
This is one of those settings that causes significant frustration when skipped and is invisible as a cause of the problem unless you know to look for it.
4. Prevent Sleep While Running: Toggle On — This One Is Critical
Codex can run goals that operate continuously for 24 to 36 hours or more. That is not a typo. A goal is not a single prompt-response exchange. It is a sustained autonomous operation that Codex works through over an extended period.
If your computer goes to sleep in the middle of that, Codex stops. The goal does not pause and resume. It stops. You lose the work in progress and have to restart from wherever it broke.
Toggle "Prevent Sleep While Running" on. Your computer will stay awake as long as Codex has an active goal running. This is especially important if you tend to close your laptop or step away from your desk during a long session. The setting exists specifically for this reason.
5. Speed: Keep It at Standard
The speed setting is not about how fast results appear on your screen. It is about how quickly Codex consumes your usage credits.
Fast mode burns credits significantly faster than Standard. For most tasks, the output quality is not meaningfully different — you are paying a premium for time, not for better work. If you are on the $100/month plan and running Codex as a real operational tool, burning through your credits at accelerated speed means hitting your usage limit earlier in the month and losing the operational continuity you paid for.
Treat the speed setting the way you would treat data roaming on a phone plan. Standard is the default for a reason. Reach for Fast only when a specific task has genuine urgency and you have consciously decided the credit burn is worth it. Do not let it default to Fast and wonder why your usage is depleted.
For more context on usage limits and how plans interact with credit consumption, learn about usage limits and plan selection.
6. Suggested Prompts: Toggle Off
Suggested prompts are the pre-written prompt ideas Codex surfaces to help you get started. They are useful for the first day. After that, they are clutter. Once you know how to direct Codex, these take up attention without adding value. Toggle them off and reclaim the clean interface.
Why These Decisions Compound
These settings feel small in isolation. Individually, each one is a toggle or a dropdown. Collectively, they determine whether Codex functions like a real operational system or a tool that breaks at unpredictable moments for invisible reasons.
The most common failure pattern: a business owner runs a long goal, steps away, comes back to find Codex stopped mid-task because the computer slept. They assume something went wrong with Codex. They restart. It happens again. They conclude Codex is unreliable. The setting that would have prevented every one of those failures is one toggle in a menu they skipped.
Settings Quick Reference
| Setting | Recommended Value | What Happens If You Skip It |
|---|---|---|
| Work Mode | Coding | Restricted agentic capability; Codex cannot execute at full function |
| Show in Menu Bar | On | No quick access; have to hunt for the app during active sessions |
| Run as Administrator (Windows only) | Always | Permission walls on your own machine; Codex blocked from basic file operations |
| Prevent Sleep While Running | On | Computer sleeps mid-goal; 36-hour task dies halfway through with no recovery |
| Speed | Standard | Credits burn faster; usage limit hit earlier in the month |
| Suggested Prompts | Off | Screen clutter once you know what you are doing |
Common Mistakes on This Screen
Leaving Speed at Fast because it sounds better. It is not better. It is more expensive. The output is equivalent for the vast majority of tasks. This is a billing decision dressed as a performance setting.
Ignoring the sleep setting because your computer doesn't usually sleep. The sleep setting is relevant precisely when you are not actively using your machine — when you step away, close the lid slightly, or let it idle during a long run. That is exactly when the computer will sleep. Toggle it on before you ever run your first goal.
Windows users not checking administrator status every session. This is a per-session action on Windows. It does not persist. Right-click, Run as Administrator, every time you open the app.
The Bigger Picture
Settings are infrastructure. They are not cosmetic. The speed decision is a financial decision. The sleep setting is a reliability decision. The work mode is a capability decision. Getting these right before you give Codex its first real task means every task after that runs on stable ground.
The Foundation Phase — the full sequence of setup decisions that precede any productive agent work — is covered in detail in the full guide. Settings are one piece of it. They are also one of the fastest to get right, which is why they deserve their own treatment before you proceed.
Learn about the next step: configuring full permissions, which is where most business owners make the costly mistake of over-restricting what Codex can do.
-- This article was drawn from a live Codex tutorial session. Watch me explain this live to see the settings screen in context.
— Shanee
Additional Context: The Codex Speed Setting Is a Billing Decision, Not a Performance Preference
Most business owners who hit their Codex usage limit faster than expected never look at the speed setting. They assume they're running more tasks than their plan supports, or that something went wrong. The real culprit is often a single toggle they changed early in setup and forgot about.
The speed setting in Codex controls how fast the model processes requests. What it doesn't advertise clearly is that faster processing burns through your usage credits at a proportionally higher rate. This is not a minor difference. It is the difference between a $100/month plan lasting the full month versus running dry in two weeks.
For the complete framework on setting up Codex as an operational system, read the full guide.
Watch me explain this live to see the settings walkthrough in real time.
Why the Speed Setting Catches Business Owners Off Guard
When you set up Codex for the first time, the speed setting appears alongside other configuration options in the settings panel. It sits next to things like whether to show Codex in your menu bar, whether to prevent sleep while running, and whether to display suggested prompts. These are all treated visually as equivalent preferences.
They are not equivalent.
Showing Codex in the menu bar has no cost attached. Turning off suggested prompts has no cost attached. Changing your speed from Standard to Fast has a direct, measurable impact on how quickly you burn through your monthly usage allocation.
The problem is that the UI does not make this cost visible at the point of decision. You toggle Fast because you want faster results — which is a reasonable thing to want — and you don't connect that choice to the usage limit warning you hit eight days later.
This is what I mean when I call the speed setting a billing decision disguised as a performance setting. The consequences belong in a completely different mental category than the UI suggests.
How Token Consumption and Speed Are Connected
Codex operates under two usage limits: a rolling 5-hour cap and a weekly cap tied to your monthly plan. When you run tasks at Standard speed, you consume credits at a baseline rate. When you switch to Fast speed, you consume credits at a significantly higher rate because the model is processing more aggressively to return results faster.
Think of it as data roaming on your phone plan. Your plan includes a set amount of data. Standard speed is WiFi — it works at a reasonable pace and doesn't count against your roaming allowance. Fast speed is like enabling data roaming: everything works faster, but you're burning through your allocation at a rate the plan wasn't designed to sustain.
The $100/month plan — which I recommend as the actual entry point for running Codex as a real operational system — gives most business owners more than enough headroom when the speed is left at Standard. When you switch to Fast, that same plan can run dry far earlier than expected.
At the $200/month tier, the headroom is larger, but the principle is identical. The speed setting affects your effective plan capacity regardless of which tier you're on.
When Fast Speed Is Actually Worth It
Standard speed is the right setting for the overwhelming majority of tasks Codex handles. Routine operations — file organization, plugin verification, business intelligence gathering, building the agent home base, running recurring automations — don't benefit meaningfully from faster processing. The quality of the output is identical. You're only getting a result sooner.
The cases where Fast speed justifies the cost are narrow:
| Situation | Use Fast? | Reasoning |
|---|---|---|
| Time-sensitive client deliverable with a hard deadline | Yes | Urgency is real and defined |
| Routine file organization or cleanup | No | No time pressure; Standard is identical quality |
| Building the Agent Home Base | No | Long-running setup; Standard is sufficient |
| Plugin verification and testing | No | Speed doesn't affect verification accuracy |
| Recovering from a multi-agent conflict under deadline | Yes | Cost of delay exceeds cost of faster credits |
| Running the Business Intelligence Gathering Skill | No | Thoroughness matters more than speed |
| One-off research or email analysis | No | Standard produces the same output |
| Live demo or client-facing session where wait time matters | Situational | Acceptable if the visibility is worth the cost |
The honest answer is that most operational use of Codex doesn't require Fast speed. The tasks that make up the actual value of an agentic system — reading your inbox, organizing your files, running automations, gathering intelligence — are not meaningfully improved by processing them faster. You're paying a premium for a result that lands a few minutes sooner.
Save Fast for genuine urgency. Leave Standard as your default.
The Setup Mistake That Costs the Most
I've seen this pattern consistently: a business owner sets up Codex for the first time, moves through the settings quickly, toggles Fast because faster sounds better, and doesn't revisit the setting again. Weeks later they hit their usage cap and conclude that Codex is too expensive for their plan or that their plan is too low.
Neither is necessarily true. The plan may be right. The speed setting is wrong.
The fix is straightforward — go back into settings and return the speed to Standard. But the broader lesson is worth holding onto: not every setting in a tool is equivalent, even when the UI presents them as if they are. In an agentic system where you're paying per token consumed, processing speed is a cost variable. Treat it accordingly.
This falls under a principle I apply across the entire Foundation Phase: default to resource-conserving settings and change them deliberately when there is a specific, defined reason to. Don't change them because a faster option exists.
For the configuration context that surrounds this setting — including Work Mode, Prevent Sleep While Running, and Suggested Prompts — read the full settings walkthrough.
Practical Application: What to Do Right Now
If you're setting up Codex for the first time:
- Leave the speed setting at Standard. Do not change it during initial setup.
- Check your current setting now if you've already set up Codex and have been hitting usage limits sooner than expected.
- Establish a rule for yourself: Fast speed is only on the table when a deadline is real and defined. Not when you're impatient.
- If you're on the $20/month plan and hitting limits frequently, investigate the speed setting before concluding you need to upgrade. Upgrading to $100/month is the right move for sustained agentic use, but upgrading while keeping Fast speed on will reproduce the same problem at a higher cost basis.
- Treat every setting in Codex that affects output rate as a billing decision. Speed is the most visible example. It won't be the last.
Understanding what burns your credits — and why — is part of operating Codex as a system rather than using it as a chatbot. This is one of the smaller decisions in the setup process, but it compounds over time. A month of Standard speed versus a month of Fast speed is a meaningful difference in what your plan actually delivers.
For context on the usage limits themselves — the 5-hour rolling cap and the weekly cap — and how they interact with your plan tier, read the usage limits breakdown.
The speed setting is not a preference. It is a cost dial. Leave it where it conserves your plan unless urgency earns the spend.
Every operational decision in Codex should be made with the same frame: default to what lasts, change it when there's a reason, and know what the change actually costs.
— Shanee
*
Use the prompts behind this system
The Growth Academy Skills Dashboard includes 100+ Codex skills and prompts for SMB owners.
See the Skills Dashboard →