Missing Models Fetcher Status
The Node That Just Says 'I'm Installed' — and Why That's the Point
- status
This node does exactly one thing: it confirms that ComfyUI Missing Models Fetcher is installed. No inputs, no settings, no sliders. Drop it on the canvas, run it, and the status output hands you the string ComfyUI Missing Models Fetcher is installed. That's the entire job.
Which sounds useless, and on its own it kind of is. The reason it exists is the pack it ships in.
A marker node, on purpose
ComfyUI Missing Models Fetcher is the more interesting half: it scans the workflow you just loaded, finds every model reference that isn't sitting in one of ComfyUI's registered model folders, resolves where to get it (Hugging Face, ModelScope, or Civitai), and shows you a confirmation list with source, type, size, hash, and destination before downloading anything. The author's own docstring for this status node says it exists "so managers can identify this extension as a node pack" - this is a sentinel, not a tool.
That's a real pattern in the ecosystem. A token node like this is how a pack becomes visible: ComfyUI knows it's installed because the class is registered, workflows can reference it, and when you load someone's workflow that contains it without having the pack, ComfyUI flags it as missing and ComfyUI Manager offers to fix it. If you've ever hit the classic "why does no workflow I download work" wall - where the first thing you do is chase down a string of missing packs before you've generated a single image - you've already met the problem this node quietly helps solve. The node is the pack's front door, and this is the "OPEN" sign.
Inputs and outputs
There are none you set. info_schema gives it zero required and zero optional inputs, and a single output:
status- aSTRINGthat always returns the same fixed sentence.
There's nothing to wire it into, and nothing to configure. You can leave it floating on the canvas as a bookmark, or just let it sit there as proof-of-install. It's not even an output node, though it has no side effects either way, so wiring it in is harmless theater.
Installing it
Here's the catch: the pack is a pre-release and not yet on the ComfyUI Registry, so Manager's search won't find it by name. You install manually:
cd ComfyUI/custom_nodes
git clone https://github.com/Adomess/ComfyUI-Missing-Models-Fetcher.git
python -m pip install -r ComfyUI-Missing-Models-Fetcher/requirements.txt
Then restart ComfyUI. Portable builds should use their bundled Python instead of the bare python. The good news: dependencies are featherweight - just certifi and PySocks. No torch, no torchvision, no giant model downloads. The downloader it needs is all bundled backend code.
Gotchas
- No node in the menu? The pack's route registration is wrapped in a try/except in
__init__.py- if the backend failed to start, it logs and moves on, so check your ComfyUI console for a "Failed to register routes" line. - Workflow says this node is missing? That means the pack itself isn't installed, or Manager can't see it because it's not on the Registry yet. Do the manual clone above.
- Don't expect community threads about it yet. As of writing this thing has zero Reddit footprint and zero search impressions - it's brand new, so the README is your troubleshooting manual, not Google.
One more thing to internalize: this node is not a health check for the downloader. The fetcher does its real work through a frontend panel and an action-bar button, not through anything this status node outputs. All it verifies is that the pack loaded. Which, when you've just spent an afternoon chasing missing nodes, is honestly the one check you actually want.
Inputs (0)
No inputs
Outputs (1)
| Name | Type | Description |
|---|---|---|
| status | STRING | — |