-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Bug]: Windows - Codex CLI version check failed. "node" is not recognized as an internal or external command #1789
Copy link
Copy link
Open
Labels
bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Install Codex CLI with npm, login.
- Install T3 Code.
- Restart because you're are on a shitty OS.
- Can't run anything:
Node is installed raw, meaning I didn't use any node manager like nvm. I checked the user and system PATH and node binary path is here on both. Reinstalled T3 Code and restarted a zillion times.
Expected behavior
T3 Code should be able to find my node version? node is running fine everywhere I tested (PowerShell and cmd).
Actual behavior
Either it's node or codex that are not recognized, pick your poison. I guess it has to be with how the env vars are loaded. I can run node and codex CLI fine in my terminal though.
Impact
Blocks work completely
Version or commit
0.0.15
Environment
Windows 10, node 24.14.1
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.Issue needs maintainer review and initial categorization.