mirror of
https://github.com/Comfy-Org/desktop.git
synced 2026-11-04 23:47:43 +00:00
[GH-ISSUE #1402] [Bug]: Unable to interact Proceed (Y/n)? with cmd comfyui and I cannot start #398
Labels
No labels
area: desktop-app
Bounty
bug
bug-cop:answered
bug-cop:response-received
component: installer
component: preload
custom node
dependencies
Design
documentation
duplicate
enhancement
expected
frontend
good first issue
installation
Low-Priority
performance
Planned
platform: cross-platform
platform: windows
Potential Bug
Potential Bug
pull-request
question
refactor
Release
stale
User Support
V1
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/desktop#398
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Muruaaki on GitHub (Nov 18, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1402
App Version
0.5.5
Expected Behavior
can press y/n
Actual Behavior
Steps to Reproduce
install was-node-suite-comfyui
Debug Logs
Browser Logs
No response
Settings JSON
No response
Other
No response
┆Issue is synchronized with this Notion page by Unito
@dosubot[bot] commented on GitHub (Nov 18, 2025):
Hi @Muruaaki! I'm Dosu and I’m helping the desktop team.
This happens because the ComfyUI desktop app on Windows doesn't support interactive command-line prompts like "Proceed (Y/n)?". When a pip uninstall or install command triggers a prompt, the app's subprocess can't accept input, so you get an EOFError and can't continue. This is a known limitation of how the desktop app launches Python processes—stdin isn't connected to your keyboard, so you can't type a response, and the process fails (details, code reference).
The root cause of the prompt is a dependency conflict: NumPy 2.x is installed, but some packages (like OpenCV or custom nodes) were built for NumPy 1.x, so imports fail and the WAS Node Suite tries to fix it by reinstalling opencv-python, which triggers the prompt.
To fix this:
.venvfolder and let the desktop app recreate it, or manually reinstall all dependencies as above.custom_nodesfolder and restart to isolate the issue.Avoid using custom nodes that trigger pip prompts or require interactive fixes until they're updated for NumPy 2.x compatibility.
If you need to automate pip commands in the future, always use the
-yor--yesflag to auto-confirm prompts, but note that some custom node scripts may not do this by default.More troubleshooting tips are available here and here.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.