You downloaded a workflow, dragged the JSON onto the canvas, and half the graph came back as red boxes reading Node type not found. That is the moment almost everyone meets ComfyUI Manager, and it is worth understanding properly rather than clicking "Install Missing" and hoping.
TLDR
ComfyUI Manager is a custom node that manages your other custom nodes — install, update, disable, and restore. Install it with comfy install via comfy-cli, or clone it into ComfyUI/custom_nodes/comfyui-manager. ComfyUI Desktop already ships with it.
Its most-used feature reads a workflow's JSON, works out which nodes you are missing, and installs them. Its most under-used feature is snapshots, which pin a known-good set so an update cannot break your graph.
Most "Manager is broken" reports are one of four things: the wrong install path, git not on PATH, an SSL failure, or a security level quietly blocking the install method you are trying to use.
Installing it
The Manager lives at Comfy-Org/ComfyUI-Manager — note that it moved from ltdrdata, so older guides point at a stale remote.
With comfy-cli, which installs ComfyUI and the Manager together:
python -m venv venv
source venv/bin/activate # Windows: venv\Scripts\activate
pip install comfy-cli
comfy install
By hand, if you already have ComfyUI:
cd ComfyUI/custom_nodes
git clone https://github.com/ltdrdata/ComfyUI-Manager comfyui-manager
The path matters more than people expect. It has to be ComfyUI/custom_nodes/comfyui-manager — not loose in custom_nodes, not nested a level deeper. A wrong path is the single most common reason the Manager tab never appears.
On Windows portable, run scripts/install-manager-for-portable-version.bat from inside the portable directory. On Linux with a venv, chmod +x and run scripts/install-comfyui-venv-linux.sh. If you use ComfyUI Desktop, it is already bundled — you do not install it separately.
The feature everyone comes for
Open a workflow with missing nodes, then Manager → Install Missing Custom Nodes. It parses the graph, matches each unknown node type against its registry, and offers you the packs that provide them.
Two things to know before you click install-all:
It resolves by node type, not by the pack the original author used. When two packs provide a same-named node, you can get a different implementation than the workflow was built against — the graph loads, and the output is subtly wrong. If a workflow has a README naming its dependencies, trust that over the Manager's guess.
And it installs the latest version of each pack, not the version the workflow was authored with. For a workflow you actually depend on, install it, confirm it runs, then snapshot immediately.
Snapshots: the feature to actually learn
Manager → Snapshot Manager saves the exact set of installed nodes and their commits. Restore rolls you back to that set on the next restart.
This is the answer to the most demoralising ComfyUI failure mode — you update one pack, three unrelated graphs stop loading, and you have no record of what worked yesterday. Take a snapshot when a complex workflow first runs correctly. It costs you one click and it is the only cheap undo the ecosystem offers.
When installs fail
Four causes cover nearly everything, and all four are configured in config.ini under [default]:
Git isn't found. Set git_exe = <full path to git>. Common on Windows where git is installed but not on PATH for the Python process.
SSL errors on install. Set bypass_ssl = True. Usual on corporate networks doing TLS inspection — and worth understanding you are turning off certificate verification, not fixing it.
Windows "overlapped object" errors. Set windows_selector_event_loop_policy = True.
The install method is blocked by your security level. This is the one that wastes the most time, because nothing tells you the block was deliberate. security_level takes strong (blocks high and middle-risk features), normal (blocks high-risk only), normal- (conditional on the listener address), or weak (everything allowed). Newer versions decouple two flags from that setting entirely: allow_git_url_install and allow_pip_install, both defaulting to false, and both only taking effect on loopback addresses like 127.0.0.1.
That last detail matters for anyone running ComfyUI on a remote box. If you reach the UI on a LAN or public address rather than 127.0.0.1, those two flags do not apply and "Install via Git URL" stays unavailable no matter what you set. Tunnel the port to localhost instead of loosening the config.
If the Manager itself will not update, its documented repair is to run this in the Manager directory:
git update-ref refs/remotes/origin/main a361cc1 && git fetch --all && git pull
Also note that v3.38 moved Manager data to a protected path as a security fix. If you upgraded across that version and your installed-node list looks empty, that migration is why — check the project's migration guide rather than reinstalling everything.
The part that bites on rented GPUs
Everything above assumes the machine persists. On a cloud GPU it usually does not.
A fresh pod gives you a clean custom_nodes directory. Manager is gone, your twenty packs are gone, and your checkpoints are gone. You reinstall, wait for the downloads, and pay GPU rates for all of it — then do it again next session. People end up scripting the reinstall, which works but silently drifts as packs move on, so scripting the setup is a partial answer rather than a complete one. We wrote separately about why custom nodes reinstall every session and about keeping the models folder off the download path.
Snapshots help here more than anywhere else: a snapshot restored onto a fresh pod at least gets you a reproducible node set rather than a hand-rebuilt one.
The other approach is to stop treating the machine as disposable — keep the whole environment, nodes and models included, and attach it to whatever GPU you rent next. That is what we built Aquanode around, and it is the reason our own ComfyUI writing keeps returning to persistence rather than to install commands. Read it as one option; a scripted rebuild plus disciplined snapshots gets most of the way there without changing anything about where you rent.
Worth remembering
The Manager is a package manager wearing a node's clothes, and it inherits every package manager's problems — resolution ambiguity, version drift, and a security model you have to actually read. Install missing nodes with it, absolutely. But snapshot the moment something works, keep the workflow author's dependency list when there is one, and check security_level before assuming a failed install is a bug.
