ComfyUI Model Hub

ComfyUI Model Hub

中文说明

A model management and download extension for ComfyUI, powered by Hanakura.

Open Hanakura inside ComfyUI using the compact Lucide Package toolbar button (tooltip: Model Manager). Browse local models, discover online models, download repositories or direct links, and use the original Hub settings interface.

• Closing the window preserves its state and leaves downloads running.
• Uses ComfyUI's registered model directories, including extra paths and legacy aliases.
• The first directory option, 所有模型目录 (All model directories), opens ComfyUI's main models folder and its subdirectories; external paths keep their own entries.
• All folders leads the directory list and is where the library opens: the folders of every directory side by side, including external paths. A directory with model files at its top level, such as a WebUI's models/Lora, appears as one folder under its own name (Lora) so its files stay together; same-named folders are labelled by their directory. The extension keeps it on, so Hub's settings switch is disabled; COMFYUI_MODEL_HUB_COMBINED_VIEW=0 turns it off.
• A local model file can be saved to your computer through the browser's own download manager.
• Refreshes ComfyUI model lists after downloads and file operations.
• Starts the Hub on demand, with no model scan during ComfyUI startup.
• Reuses the dependency installation framework from ComfyUI-HakuImg. No Node.js build is needed.

Installation

From the ComfyUI directory, clone the extension using Git:

git clone https://github.com/licyk/comfyui-model-hub.git custom_nodes/comfyui-model-hub

Restart ComfyUI and refresh the browser. The prestartup script automatically installs missing/incompatible dependencies using ComfyUI's own Python interpreter.

Behavior

Use the top button or Tools → Open Model Manager. The window opens the local library and supports maximize, close, and retry. Hub directories are read when first opened and fixed by ComfyUI; restart after changing ComfyUI path configuration.

The toolbar button, with a Lucide Package icon, uses the frontend's action bar on frontend 1.32.4 and newer; older frontends get a legacy top-menu button with the same native sizing as comfyui-browser. Open in new tab is always available in the dialog header, including after startup failure. The new tab starts Hub independently from its own origin before opening the library.

Each registered model directory becomes a stable Hub root, deduplicated by resolved path. Default destinations follow ComfyUI's per-category path order. Auxiliary VAE and latent upscaler directories do not replace primary defaults. Unknown extension model categories remain browsable without an assumed model kind. Discovery does not create missing directories. Root locking does not restrict Hub's existing absolute download destinations or server-side imports.

One Hub and download queue are shared by the ComfyUI instance. Settings, credentials, the database and caches live under <ComfyUI user directory>/__model_hub/, separate from the extension and standalone Hub data.

Startup errors show the HTTP status and request path. For 404 / 405, check extension loading and proxy routes; for 401 / 403, check authentication and the public URL configuration. A 200 response without a Hub startup result may be a login page or frontend HTML. Restart ComfyUI and hard-refresh the browser after updating the extension.

Remote access

All browser traffic uses ComfyUI's same-origin /model-hub/ path. The private Hub binds a random loopback port and is authenticated using a backend-only token. The proxy supports streaming HTTP, WebSocket and Socket.IO polling. No additional public port is needed.

Forward the entire ComfyUI deployment path, including WebSocket upgrades. Valid browser origins accompanied by Sec-Fetch-Site: same-origin remain accepted after proxy TLS termination or Host rewriting. Cross-site and opaque (Origin: null) requests remain rejected; use Open in new tab if ComfyUI is embedded in a sandbox or another website.

The dialog embeds /model-hub/ in a same-origin iframe. Proxied Hub responses carry Content-Security-Policy: frame-ancestors 'self', so browsers ignore an X-Frame-Options: DENY that a reverse proxy or CDN adds. A restrictive frame-ancestors in the proxy's own Content-Security-Policy, or a proxy that strips or replaces backend CSP headers, still blocks the embed even though the parent page is the same origin, and the dialog reports the refused framing. Allow frame-ancestors 'self' for the ComfyUI host, or use Open in new tab, which is a top-level navigation and stays unaffected.

For Civitai OAuth, or proxies that remove browser origin metadata, explicitly set the public Hub URL, including any proxy prefix:

export COMFYUI_MODEL_HUB_PUBLIC_BASE_URL=https://example.com/comfy/model-hub

Register https://example.com/comfy/model-hub/api/v1/auth/civitai/callback with the OAuth provider as required by Hub. Client-supplied forwarding headers do not choose callback URLs. Manual source tokens work without OAuth configuration.

Hub inherits access to ComfyUI; ComfyUI user IDs do not provide separate Hub authorization. Existing deployment authentication must cover both HTTP and WebSocket paths.

All folders is fixed on, and Hub's settings switch is disabled. Set COMFYUI_MODEL_HUB_COMBINED_VIEW=0 to fix it off instead.

Set COMFYUI_MODEL_HUB_AUTO_INSTALL=0 to manage dependencies manually. Installer logging can be configured through COMFYUI_MODEL_HUB_LOGGER_NAME, COMFYUI_MODEL_HUB_LOGGER_LEVEL (default 20) and COMFYUI_MODEL_HUB_LOGGER_COLOR (0 disables color).

Development

python -m playwright install chromium
python -m pytest -q
python -m ruff check .
python -m ruff format --check .
python -m ty check --python /path/to/comfy/python
node --check js/model_hub.js
node --check js/dialog.js
node --test tests/*.mjs

Type checking expects ComfyUI at ../ComfyUI; otherwise pass --extra-search-path /path/to/ComfyUI. Browser tests optionally accept PLAYWRIGHT_CHROMIUM_EXECUTABLE.

Tests use the real released Hub, temporary model directories, and a local download source. Chromium tests use the real Hub UI inside a small host implementing the public ComfyUI extension registration contract. They do not substitute for a full ComfyUI frontend/GPU workflow check.

Licensed under GPL-3.0-only.