Beginner · 6 min read
Choose the right Codex setup: desktop or CLI, Mac or Windows
Choose an interface for your work, understand the platform differences, and separate historical Mac-first launches from current availability.
For choosing a local Codex interface. Platform availability was checked on September 9, 2026; individual features can also depend on account, region, and app version.
Choose the desktop app for a visual workspace and the CLI for a terminal workflow. Mac and Windows support the core desktop workflow; check each feature's current documentation before assuming it is exclusive to one platform.
1. Desktop app and CLI serve different workflows
Both interfaces can work with a local code project. The desktop app makes multiple tasks, file previews, and reviewing changes visible in one workspace. The CLI fits work you already do in a terminal and provides a non-interactive command for scripts.
Using the app does not mean every task runs in the cloud, and using the CLI does not require a separate model subscription by definition. Check the selected environment, sign-in method, and account access. The current desktop documentation calls the app ChatGPT and includes Codex as a selectable experience.
| Your need | Desktop app | CLI |
|---|---|---|
| Inspect a code change | Use the visual review panel and file previews. | Read terminal output and use Git or your editor. |
| Manage several tasks | Use the project and task workspace. | Keep track of terminal sessions and working directories. |
| Repeat a scripted job | Use supported app scheduling features where appropriate. | Use codex exec in an explicitly scoped script. |
| First small project | A useful choice if you prefer visual navigation. | A useful choice if terminal commands are familiar. |
Reference: OpenAI: Desktop app · OpenAI: Codex CLI
2. What differs between Mac and Windows?
The operating system changes the shell, paths, sandbox setup, and some desktop permissions. It does not make one platform a different coding model. Match instructions to the environment where the agent actually runs.
| Area | macOS desktop | Windows desktop |
|---|---|---|
| Local commands | Unix-style paths and the configured Mac shell. | Native PowerShell is supported; WSL2 is an optional agent environment. |
| Setup | macOS 14 or later; the current app supports Apple Silicon and Intel. | Use the official Store route and complete native sandbox setup if prompted. |
| Computer Use | Supported where available; requires Screen Recording and Accessibility permissions. | Supported where available; keep the target app visible on the active desktop. |
| Project portability | Check tool versions and local dependencies. | Check shell syntax, paths, and whether tools run in Windows or WSL. |
Reference: OpenAI: Windows desktop app · OpenAI: Computer Use · OpenAI: macOS requirements
3. Do new features always arrive on Mac first?
There is a real historical example: OpenAI introduced the Codex app for macOS on February 2, 2026, and added Windows availability on March 4. That supports saying the app launched on Mac first.
It does not establish a permanent policy that every feature must stabilize on Mac before reaching Windows. We did not find an official guarantee of that release sequence. Describe a staggered release with its feature name and date, rather than treating 'Mac first, Windows later' as a rule.
Current documentation lists Computer Use on both macOS and Windows in supported regions. A tutorial that still labels it Mac-only can therefore mislead readers. For a missing feature, compare the current feature page, installed version, account eligibility, region, and plugin or permission setup.
Reference: OpenAI: Introducing the Codex app · OpenAI: Computer Use
4. Avoid mixing Windows, WSL, and app settings
On Windows, the agent environment and integrated terminal shell are configured separately. A PowerShell terminal in the app does not by itself prove the agent runs natively. Confirm both before copying commands from a tutorial.
The native Windows app and a CLI inside WSL use different home directories by default. That can explain why one is signed in or configured while the other is not. Do not copy authentication files between environments merely to make their behavior look identical; begin with the documented setup for the environment you intend to use.
Reference: OpenAI: Windows desktop app
5. Choose one route for your first task
Try the desktop app if your first priority is seeing files and reviewing outputs. Try the CLI if you already navigate repositories in a terminal. Keep the first task small enough to compare the input, changed files, and result in a few minutes.
You can use both later. When switching, confirm the project directory, branch, active instructions, and available tools. A command or plugin being available in one session is not proof that it is available in another.
Try it in Codex
Check the environment you are actually using
Help me understand this Codex environment before I follow a tutorial. Inspect available information read-only.
Identify the operating system, current project directory, Git branch if any, and the shell used for commands. On Windows, distinguish native Windows from WSL if the evidence allows it. Do not infer the agent environment solely from the integrated terminal.
Explain which parts you verified and which remain unknown. Do not print credentials or private configuration values. Suggest whether a desktop or CLI workflow fits my current task, without installing software or changing settings.Read the prompt before sending it. Copying does not run it.
Check your result
- You know whether you are following desktop or CLI instructions.
- You can identify the actual operating system, shell, and project location.
- A missing feature is checked against its current documentation and eligibility.
- Mac-first history is not mistaken for a promised release schedule.
Sources and scope
Official references support the product behavior described above. The task prompts and practical checks are our community guidance.
- OpenAI: Desktop appThe visual workspace and current desktop naming.
- OpenAI: Windows desktop appNative/WSL environments, terminal configuration, and separate default Codex homes.
- OpenAI: Computer UseCurrent macOS/Windows availability and different operating-system permissions.
- OpenAI: Introducing the Codex appFebruary 2, 2026 macOS launch and March 4 Windows availability update.
- OpenAI: Codex CLIInteractive terminal work and non-interactive execution.
- OpenAI: macOS requirementsCurrent macOS and processor requirements.
Something changed in your version? Send a correction with the guide URL, platform, and version. Leave out credentials and private project content.