Comfy-Org / Comfy-Org/ComfyUI

No clue where the files go

Open
#15,941 1 comment 0 reactions 0 assignees View on GitHub
Potential Bug
Dominant language
Python
Stars
133k
Forks
15.7k
Avg merge
1d 6h
Merged PRs (30d)
155

Description

### Custom Node Testing

- [ ] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

A half year ago, ComfyUI worked perfectly out-of-the-box because the UI was actually logical: when a model was missing, it explicitly showed the exact folder path (like models/checkpoints/). The expected behavior is that you either make the download button actually work server-side, or you bring back the path display so users don't have to waste hours on Google trying to guess your secret folder logic.

### Actual Behavior

You deliberately broke a feature that worked fine. In this new UI, you hid the destination paths completely. Clicking 'Download' now just triggers a lazy browser download that dumps 11GB+ files into the local ~/Downloads folder, leaving the server completely broken. Filenames like sdxl_onestep_t2i.safetensors give zero clues where they belong. Removing the path visibility is pure user harassment and a massive step backward. Fix this garbage and show the paths again. Or do like you can actually code and place them right away where they belong.

### Steps to Reproduce

You know exactly how

### Debug Logs

```powershell
No
```

### Other

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the model download from the UI and observe whether it only reaches the browser's ~/Downloads folder or can be placed on the server. Trace the download action and model destination handling; done means either server-side placement works or the UI again displays the exact destination path, such as models/checkpoints/.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.