Codex uses bundled pnpm instead of host toolchain

[kkaatii]

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

26.623.42026

What subscription do you have?

Pro

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

Codex is consistently failing to run my build script because that script invokes pnpm install.

As per its own diagnosis:

• My local projects uses PNPM v10
• Codex comes bundled with PNPM v11 in ~/.cache/codex-runtimes/codex-primary-runtime/dependencies/bin/pnpm
• When running the build script, Codex uses the bundled one, leading to failure to resolve dependencies, whereas the build script is run fine in any local terminal

What steps can reproduce the bug?

1. Create a pnpm v10 project with dependencies in package.json
2. Run pnpm install in terminal to install the dependencies
3. Create a js script

   import { spawn } from "node:child_process";
      
   const child = spawn("pnpm", ["install"], {
     cwd: process.cwd(),
     stdio: ["ignore", "pipe", "pipe"],
   });
   
   child.on("close", (code) => {
     process.exit(code ?? 1);
   });

4. Ask Codex (with pnpm v11 bundled) to run node script.mjs inside project dir

What is the expected behavior?

Codex should use my local pnpm binary, and ask for permission elevation when needed.

In fact, using this to run the build script is fine: PATH="path-to-my-local-nodejs/bin:$PATH" CI=true node script.mjs

Additional information

No response

[zhuscat]

I encountered the same problem in Codex Desktop App

[cubicj]

I am seeing the same issue on Windows Codex Desktop.

Codex App: 26.623.8305.0
OS: Windows 11 Education x64, 10.0.26200
Project packageManager: pnpm@10.34.1
User-global pnpm: 10.34.1
Bundled Codex pnpm: 11.7.0

Inside Codex, Get-Command pnpm -All resolves the bundled runtime first:

C:\Users\<user>\.cache\codex-runtimes\codex-primary-runtime\dependencies\bin\pnpm.cmd
C:\Users\<user>\AppData\Roaming\npm\pnpm.ps1
C:\Users\<user>\AppData\Roaming\npm\pnpm.cmd

Running pnpm check uses the bundled pnpm and fails before the project script runs:

ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY
Aborted removal of modules directory due to no TTY

Explicitly calling the user-global pnpm works:

& "$env:APPDATA\npm\pnpm.cmd" check

This uses pnpm 10.34.1 and passes. pnpm test and pnpm build also pass with the user-global pnpm.

I opened #30541 before noticing this issue. I will close it as a duplicate, but leaving the Windows reproduction details here since the same bundled pnpm shadowing happens on Windows too.

[RickVM]

Running into this as well on my mac, exactly the same diagnoses.

[Javierg9n4]

I am also running into this same issue since the last codex app update on my mac.

[Alt-er]

how to solve