Node and npm aren't available in Codex's shell path on Windows using a version manager

[gradyat]

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

26.306.11636

What subscription do you have?

Free

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

A couple of environment quirks showed up: plain npm isn’t available in this shell path, and some parallel reads timed out, so I’m rerunning those pieces in a more direct way. [...]

I can’t execute the package scripts in this shell because npm isn’t on the PATH here

node --version also failed because node isn’t recognized, so Node isn’t on the PATH either.

What steps can reproduce the bug?

Run a command in which Codex wants to use node or npm.

If it's relevant, I use fnm to install and manage my Node and npm versions.

What is the expected behavior?

Codex can find and run Node and npm on its shell

Additional information

I use fnm to install and manage my Node and npm versions. I am using a native Windows development environment, not WSL.

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Codex Windows app (WSL): non-interactive shell doesn’t load NVM, so node/pnpm are missing from PATH (command not found) #13566
• Windows: Codex launches tools with \\?\ namespace cwd, breaking pnpm/Node tooling #13845

Powered by Codex Action