[Bug] codex setup fails on windows

[tzarebczan]

I was setting up via git bash on windows, and codex step would fail on ACP install. I manually installed https://github.com/agentclientprotocol/codex-acp in git bash, and then it worked.

[tzarebczan]

Root cause

On Windows, login_shell_path() is intentionally None (Git Bash emits a POSIX colon-PATH that poisons native children). Install shells then built PATH from only the Buzz managed npm prefix — dropping the process PATH that has system Node/npm (e.g. nvm4w). Adapter install becomes effectively npm: command not found under Git Bash.

Managed Node download is also not implemented for Windows yet, so Buzz can't fall back to a private Node runtime the way it does on macOS/Linux.

Fix (branch fix/windows-runtime-install-and-console)

When login-shell PATH is unavailable, fall back to the process PATH (managed bins still prepended). That should let npm install -g @agentclientprotocol/codex-acp see system npm on Windows.

Manual install of codex-acp worked around this by putting the binary where discovery could find it.

[wpfleger96]

🤖 Thanks for this report — your diagnosis was exactly right. On Windows login_shell_path() always returns None, so the install shell composed PATH from the managed npm prefix alone and dropped system Node/npm, producing the npm: command not found you hit. That's fixed by #2563 (cca16635d): the inherited process PATH is now always appended on Windows (should_use_inherited + compose_path_entries in runtime/path.rs). Your second note about missing managed Node on Windows landed too — #2661 (596386ee5) added win-x64/arm64 managed-Node artifacts. Both ship in v0.4.25. Closing as resolved; if you still hit an install failure on v0.4.25 or later, please reopen with the error text.