[GH-ISSUE #3020] [Request] Add raw wget download URLs to the “Missing Models” panel for easier CLI downloads #1082

New issue

Open

opened 2026-10-27 21:25:35 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-27 21:25:35 +00:00

Owner

Originally created by @wes-kay on GitHub (Jun 25, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3020

When using the Missing Models panel in ComfyUI (e.g. under Workflow Overview → Missing Models → diffusion_models / loras / vae), each missing file currently provides:

Current Behavior

The copied URL looks like:

https://huggingface.co/Comfy-Org/Wan_2.1_ComfyUI_repackaged/blob/main/split_files/diffusion_models/wan2.1_t2v_14B_fp8_scaled.safetensors

This is a webpage URL and cannot be used directly with tools such as:

wget
curl
automated install scripts
remote deployment workflows

Expected Behavior

The copied URL should also include the raw file URL:

https://huggingface.co/Comfy-Org/Wan_2.1_ComfyUI_repackaged/resolve/main/split_files/diffusion_models/wan2.1_t2v_14B_fp8_scaled.safetensors

This URL works correctly with command-line download tools and automation.

Affected Model Types

This appears to affect all missing model categories

Why This Matters

Many ComfyUI users run on servers, cloud instances, Docker containers, or headless environments.
Large model files are frequently downloaded via wget, curl, or deployment scripts.
The current copied URL fails in these workflows and creates unnecessary confusion.
Users often assume the copied URL is intended for direct download because it is exposed through a "Copy URL" action.

Additional Issue: Download Destination

The current browser-based download workflow also creates friction for users who store models outside the ComfyUI installation directory using Additional Model Paths (yaml config).

Because downloads occur through the browser instead of ComfyUI itself:

Models must often be moved manually after download.
Users with custom model locations cannot easily download directly into their configured model directories.
Automated setup workflows become more difficult.
Remote and server-based installations require extra steps.

If ComfyUI handled model downloads directly and saved them to the resolved model path (including Additional Model Paths), users could avoid manual downloads entirely and models would be placed in the correct location automatically.

Suggested Improvements

Option 1 (Better UX)

Add a second action:

Copy Direct Download URL

Option 2 (Best Long-Term Solution)

Allow missing models to be downloaded directly by ComfyUI into the resolved model directory, including support for Additional Model Paths. This would:

Eliminate manual file movement
Improve remote/server workflows
Support automated setup processes
Avoid browser download limitations
Ensure models are placed in the correct configured location automatically

Originally created by @wes-kay on GitHub (Jun 25, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3020 When using the **Missing Models** panel in ComfyUI (e.g. under **Workflow Overview → Missing Models → diffusion_models / loras / vae**), each missing file currently provides: ### Current Behavior The copied URL looks like: ```text https://huggingface.co/Comfy-Org/Wan_2.1_ComfyUI_repackaged/blob/main/split_files/diffusion_models/wan2.1_t2v_14B_fp8_scaled.safetensors ``` This is a webpage URL and cannot be used directly with tools such as: * wget * curl * automated install scripts * remote deployment workflows ### Expected Behavior The copied URL should also include the raw file URL: ```text https://huggingface.co/Comfy-Org/Wan_2.1_ComfyUI_repackaged/resolve/main/split_files/diffusion_models/wan2.1_t2v_14B_fp8_scaled.safetensors ``` This URL works correctly with command-line download tools and automation. ## Affected Model Types This appears to affect all missing model categories ## Why This Matters * Many ComfyUI users run on servers, cloud instances, Docker containers, or headless environments. * Large model files are frequently downloaded via `wget`, `curl`, or deployment scripts. * The current copied URL fails in these workflows and creates unnecessary confusion. * Users often assume the copied URL is intended for direct download because it is exposed through a "Copy URL" action. ## Additional Issue: Download Destination The current browser-based download workflow also creates friction for users who store models outside the ComfyUI installation directory using **Additional Model Paths** (yaml config). Because downloads occur through the browser instead of ComfyUI itself: * Models must often be moved manually after download. * Users with custom model locations cannot easily download directly into their configured model directories. * Automated setup workflows become more difficult. * Remote and server-based installations require extra steps. If ComfyUI handled model downloads directly and saved them to the resolved model path (including Additional Model Paths), users could avoid manual downloads entirely and models would be placed in the correct location automatically. ## Suggested Improvements ### Option 1 (Better UX) Add a second action: * Copy Direct Download URL ### Option 2 (Best Long-Term Solution) Allow missing models to be downloaded directly by ComfyUI into the resolved model directory, including support for Additional Model Paths. This would: * Eliminate manual file movement * Improve remote/server workflows * Support automated setup processes * Avoid browser download limitations * Ensure models are placed in the correct configured location automatically

bsakaguchi referenced this issue

2026-10-28 21:03:22 +00:00

[PR #1082] [MERGED] fix duplicate repo in custom-node-list #1694