VNCCS Model Manager

There's a class of ComfyUI pain that has nothing to do with prompting: managing models. You've got checkpoints and LoRAs scattered across a dozen HuggingFace pages, and every fresh workflow needs you to remember where the file lives and whether the version you have is current. VNCCS Model Manager is the backend half of an answer - a node that points at a HuggingFace-hosted model manifest and quietly handles downloads and updates for you.

The key word is backend. By itself this node looks almost comically empty: one input, one passthrough output. All the interesting machinery lives behind it - an API endpoint that ComfyUI's frontend talks to, a background downloader, and a local registry that tracks what's installed. Its companion, VNCCS Model Selector, is the part you actually look at.

How it works

The model is a manifest file called model_updater.json, hosted on a HuggingFace repo. It lists the models, their versions, and where each file should land in your ComfyUI model folders. The Manager's job is to read that manifest and manage the downloads: it queues them in the background, tracks state in a local vnccs_installed_models.json registry, and exposes status through the /vnccs/manager/status endpoint the frontend polls. It also handles Civitai - restricted models need an API key, which the Manager supports for authentication.

The default repo is MIUProject/VNCCS, which is the author's own model hub (same MIUProject that hosts the weights for the parent VNCCS suite). But the whole point is that you can point it at your repo. The pack ships a configuration guide and a template-model_updater.json so you can publish your own manifest and have a personal, one-click model store.

The inputs and outputs

Exactly what it says on the tin:

• repo_id - the HuggingFace repository ID hosting your model_updater.json (default MIUProject/VNCCS).
• repo_id output - a plain pass-through of the same string, so you can wire it into the Model Selector and keep both nodes pointed at the same repo without typing it twice.

Everything else - the download list, the progress, the status badges - lives in the node's UI and the manager endpoints, not in sockets.

Installing it

Standard VNCCS Utils install:

cd ComfyUI/custom_nodes
git clone https://github.com/AHEKOT/ComfyUI_VNCCS_Utils.git
cd ComfyUI_VNCCS_Utils
pip install -r requirements.txt

or search VNCCS Utils in ComfyUI Manager and restart. No extra model files to fetch - this node manages models, it doesn't need one itself.

Honest notes

The mental model matters more than the wiring: Model Manager = the downloader, Model Selector = the picker. If you add just the Manager and expect a pretty card UI, you'll be confused - that's the Selector's job. The two are a pair, and the natural flow is Manager's repo_id → Selector's repo_id, then pick your model in the Selector's UI.

Also worth knowing: this only manages what's in your manifest. It's a great fit if you're maintaining a shared model library across a few machines or a team, and overkill if your whole setup is one checkpoint you downloaded once. If that's you, this node is more infrastructure than you need - but it's zero-cost to have around.