Codex Installation, Update & Setup Errors

Installation problems can start before Codex runs: a missing executable, an outdated installation, an editor extension that will not load or a Windows sandbox setup failure. Start with the client and operating system you actually use.

What to check first

• Identify whether you installed the CLI, desktop app or IDE extension.
• Record your operating system and the installed version.
• Check the relevant installation path before reinstalling or deleting configuration.

Installation troubleshooting guides

• Where is the Codex config file? (config.toml location and layers)

  Open ~/.codex/config.toml on macOS or Linux, or %USERPROFILE%\.codex\config.toml on Windows.

  Codex CLI, Desktop app, IDE extension · Windows, macOS, Linux

• codex: command not found after installing

  Check which shell you are in, then open a brand-new terminal.

  Codex CLI · Any platform

• Codex: stdin is not a terminal — interactive shell or script?

  Check whether you want an interactive conversation or an automated script; they use different CLI entry points.

  Codex CLI · Any platform

• Codex: update failed, wrong version, or installed with the wrong method

  Identify which install method you used (standalone installer, npm, Homebrew, or a manual archive), because that decides how you update.

  Codex CLI, Desktop app · Windows, macOS

• Codex not loading in VS Code: find what the spinner is hiding

  Record whether VS Code is local or remote, then inspect the Codex extension log for the first repeated error.

  IDE extension · Windows, Linux

• Codex Windows setup didn't finish: helper_failed and UAC checks

  Record the exact setup error and whether a Windows administrator prompt appeared; these distinguish different failure stages.

  Desktop app · Windows

Reached a usage limit instead? Check Codex usage limits and reset times.