Codex RescueCodex troubleshooting
Codex installation, update & setup errors
Fix Codex command-not-found errors, update failures and Windows sandbox setup problems. Follow platform-specific checks for your CLI or editor.
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.
Installation and update errors often involve more than one Codex entry point. A terminal command, an IDE extension and a desktop app can use different executable paths or packaged runtimes. First identify the client that produced the message. For a shell error, ask that shell which executable it resolves before reinstalling. For an update that appears to have succeeded, compare the active path and version with the installation method you actually used. For a Windows setup banner, record whether the administrator prompt appeared and the first helper error rather than assuming that a general reinstall is the next step.
The guides below are intentionally separate. “Command not found” is about command discovery; “update failed” covers the installer or a stale runtime; Windows sandbox setup concerns local command isolation after the app opens. An editor that does not load is another path. These distinctions protect your configuration and session history from broad cleanup advice. Keep the full error privately, redact credentials before sharing it, and follow platform-specific steps only in the environment where Codex is running.
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
codex: command not found after installing
Check which shell you are in, then open a brand-new terminal.
Codex config.toml location and overrides
Check CODEX_HOME in the affected environment before opening the default user configuration.
Codex stdin is not a terminal: fix
Check whether you want an interactive conversation or an automated script; they use different CLI entry points.
Codex update failed: five causes to check
Identify which install method you used (standalone installer, npm, Homebrew, or a manual archive), because that decides how you update.
Codex VS Code not loading: fixes
Record whether VS Code is local or remote, then inspect the Codex extension log for the first repeated error.
Codex Windows sandbox setup failed
Record the exact setup error and whether a Windows administrator prompt appeared; these distinguish different failure stages.
Back to all Codex error messages →
Reached a usage limit instead? Check Codex usage limits and reset times.