PATH added in Windows Environment variable setting does not take effect

Resolved 💬 1 comment Opened Jun 6, 2026 by Jason5Lee Closed Jun 13, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.602.40724

What subscription do you have?

Free

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I added a path in the PATH variable in the Windows Environment variables setting, and verify that the corresponding binary can be found in system PowerShell by running it and by the output of the Get-Command. But when Codex tries to run the command, it reports that the command cannot be found, and Get-Command run by Codex returns empty. I tried restarts Codex, and restarts the system, but the added path is still not picked.

What steps can reproduce the bug?

Added a path in the PATH variable of Windows system Environment variable settings, then makes Codex run the command.

What is the expected behavior?

The command run successfully since the path is added to PATH.

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗