-
Notifications
You must be signed in to change notification settings - Fork 4k
Windows: node not recognized in first Warp session until app restart #10213
Copy link
Copy link
Open
Labels
area:shell-terminalTerminal input/output, shell integration, prompt behavior, and block rendering.Terminal input/output, shell integration, prompt behavior, and block rendering.bugSomething isn't working.Something isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.More issue-specific reporter detail is needed before the problem can be confidently triaged.os:windowsWindows-specific behavior, regressions, or requests.Windows-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Description
Metadata
Metadata
Assignees
Labels
area:shell-terminalTerminal input/output, shell integration, prompt behavior, and block rendering.Terminal input/output, shell integration, prompt behavior, and block rendering.bugSomething isn't working.Something isn't working.needs-infoMore issue-specific reporter detail is needed before the problem can be confidently triaged.More issue-specific reporter detail is needed before the problem can be confidently triaged.os:windowsWindows-specific behavior, regressions, or requests.Windows-specific behavior, regressions, or requests.repro:mediumThe report suggests a plausible repro path, but some uncertainty remains.The report suggests a plausible repro path, but some uncertainty remains.triagedIssue has received an initial automated triage pass.Issue has received an initial automated triage pass.
Pre-submit Checks
Describe the bug
Summary
Intermittent startup environment issue on Windows where node is unavailable in the first Warp session and only works after restarting Warp.
Problem
In Warp on Windows, running node -v sometimes fails with “The term node is not recognized...” in a fresh session (often on first open or after updating Warp). Closing and reopening Warp makes the same command work.
Expected behavior
node should be resolvable and executable in every new Warp session without restarting the app.
Actual behavior
In some fresh launches, node -v fails with: node: The term 'node' is not recognized as a name of a cmdlet, function, script file, or executable program.... After closing and reopening Warp, node -v works.
Reproduction steps or desired workflow
Artifacts
Error text from affected session:
node: The term 'node' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.Warp version
v0.2026.04.29.08.57.stable_02
Operating system
Windows 10.0.26100
To reproduce
dont know how to reproduce.
Expected behavior
No response
Screenshots, videos, and logs
No response
Operating system (OS)
Windows
Operating system and version
Windows 10.0.26100
Shell Version
No response
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None