Codex app for Windows

Set up Codex on Windows and complete a first project inspection before asking it to edit your site. Current documentation places Codex inside the ChatGPT desktop app; the Windows-native agent runs commands in PowerShell.

Before you start

• A Windows computer allowed to install the current ChatGPT desktop app, and a ChatGPT account with Codex access.
• A local project folder you recognize, preferably a spare copy or a repository with a saved working version.
• The project’s setup instructions. Install only the developer tools it actually needs; Git is needed for Git review features, and a JavaScript project commonly needs Node.js.

Want to do it yourself?

Difficulty

6 out of 10

Estimated completion time

45–90 minutes

Skills you’ll need: Install the app, open the right project folder, and run its documented checks. Windows and WSL path issues may need troubleshooting.

I’ll do it myselfI’d rather get help

How this helps your brand

A working project setup is the foundation for maintaining your business site or software. Identifying the real runtime and check commands helps avoid edits made against the wrong folder or an untested environment.

1. 1

   Step 1: Install the current desktop app

   Use the Windows download linked from OpenAI’s Windows app documentation and finish the installation. Open the app and sign in with your ChatGPT account. In the ChatGPT dropdown, select Codex for software work.

   This guide uses ChatGPT sign-in. API-key sign-in is also supported, but some features may not be available. If your organization manages installation or account access, use its approved setup instead of changing machine-wide settings.

2. 2

   Step 2: Open one recognizable project folder

   Choose Add new project or press Ctrl+O, then select your project directory. Use a folder on your Windows filesystem for this first walkthrough. Check that the project name matches the files you intended Codex to inspect.

   Keep the default Windows-native agent for this test unless the project specifically requires Linux. It runs commands in PowerShell. Changing the integrated terminal to WSL does not change the agent environment; those settings are independent.

3. 3

   Step 3: Inspect the project before changing it

   Select Ask for approval beneath the composer before sending a Codex message so sandbox protections apply. Paste the prompt below and ask Codex to read the setup instructions, identify the project type, and report what tools it needs.

   Compare the reported project name and files with your folder. Ask for a plain-language explanation of any proposed command you do not understand. Keep this first task read-only so you can tell whether the app is working in the correct place.

   Illustrated exampleMatch the inspection report to your Windows project

   Example selected foldernorthline-siteC:\Projects\northline-site

   Recognize these files?

   • README.mdSetup instructions
   • package.jsonTools and scripts
   • src/Website source

   Sample inspection report

   Project

   Northline website · JavaScript

   Instructions read

   README.md

   Agent environment

   Windows native · PowerShell

   Required tools found

   Node.js and Git

   Documented next check

   npm run dev

   Files changed: 0. Compare this report with your folder before asking Codex to run the next command.

   Before sending the inspection request: choose Ask for approval.

4. 4

   Step 4: Run the project’s documented check

   After the inspection, ask Codex to run the project’s existing test or development command. For a website, ask it to open the exact local URL reported by the server in the built-in browser. Review command output and the visible page; do not assume that starting a process means the site loaded.

   If a required tool is missing, install the version your project requires and retry. Git enables the app’s Git review features, while Node.js, Python, or the .NET SDK may be needed depending on the project. You do not need every tool for every project.

5. 5

   Step 5: Handle Windows and WSL mismatches

   If a command fails, keep the exact error and check whether it ran in PowerShell or WSL. An npm.ps1 execution-policy error is different from a missing dependency. Ask for an explanation before changing execution policy, especially on a managed computer.

   If the project requires the agent itself to use WSL2, change the agent from Windows native to WSL in Settings and restart the app. WSL1 is not supported starting with Codex 0.115. For WSL folders opened through the file picker, enter \\wsl$\ and choose the distribution and project.

   If Git is not detected while using a Windows-native agent with a WSL folder, OpenAI recommends storing the project on the Windows drive and accessing it from WSL through /mnt/[drive]/[path]. Keep the original copy until the relocated project works.

   Illustrated exampleThe terminal and the agent can use different environments

   Illustrated configuration · two independent settings

   Agent settingWindows native

   Task commands run in

   PowerShell

   Integrated terminal settingWSL2

   Terminal tab opens in

   Linux shell

   In this example, the terminal uses WSL2 while the agent still uses PowerShell.

   Does the project require the agent to use Linux?

   1. 1Change the agent to WSL in Settings.
   2. 2Restart the app.
   3. 3Check that task commands now use WSL2.

Inspect this project on Windows before changing anything. Read [README or setup-instructions filename], identify what the project does, and list the documented setup, test, and development commands. State whether your commands will run in Windows-native PowerShell or WSL, and check which required tools are available. Do not edit files, install dependencies, change execution policy, or deploy. Tell me the smallest next step to run the project, and report any missing instructions or access blockers.