Extending ComfyUI with Manager, Models, and Custom Nodes

ComfyUI's base installation is only the starting point. Many advanced workflows depend on custom nodes, additional model files, and supporting libraries. ComfyUI Manager centralizes much of that installation work, but the user still needs to understand the difference between node code, model assets, dependencies, refreshes, and restarts.

ComfyUI Manager is installed as a custom node. In the Windows portable folder, the user opens the custom_nodes directory, opens a command prompt in that location, and clones the Manager repository. Git must already be installed for that command to work. The Git installation shown uses the default options throughout.

After Manager is placed in custom_nodes, ComfyUI is restarted. The startup process detects the new extension and installs its dependencies. A Manager button then appears in the interface.

The principal Manager functions used in the workflows are:

Custom Nodes Manager: Searches for and installs node packages such as Image Chooser, Ultimate SD Upscale, ArtVenture, and InstantID support.

Model Manager: Searches for and installs additional model files such as upscalers, ControlNet Union, and InstantID assets.

Install Missing Custom Nodes: Helps repair an imported workflow that references nodes or dependencies not present on the local computer.

Update ComfyUI / Update All: Updates the application or installed extensions.

Installing an item is not always the final step. Model installations generally require the interface's Refresh control before the new model appears. Custom-node installations commonly require a full ComfyUI restart. Some nodes trigger additional dependency downloads during that restart.

Advanced integrations may still require manual file placement. InstantID, for example, uses Manager for the node package and two major model files, but the AntelopeV2 InsightFace model is manually extracted into a specific nested directory. Manager reduces installation work; it does not eliminate the need to read and follow a node's model requirements.

A workflow imported from another user can be structurally correct but fail locally because its custom nodes or models are missing. The graph alone does not include every executable dependency.

Understanding the extension stack helps diagnose failures:

If a node type is missing, install the custom-node package.

If the node exists but its dropdown is empty, install the required model and refresh.

If startup reports missing libraries, restart after installation and allow dependency setup to complete.

If the extension documentation specifies a directory, place the asset exactly there.

This separation prevents repeated graph edits when the real problem is an incomplete environment.

Use this extension-installation sequence:

1. Confirm that Git is installed.
2. Open a command prompt inside ComfyUI/custom_nodes.
3. Clone ComfyUI Manager into that directory.
4. Restart ComfyUI and allow dependency installation to finish.
5. Open Manager.
6. Use Custom Nodes Manager to find the required node package.
7. Install the package and restart when requested.
8. Use Model Manager to install any corresponding model files.
9. Close Manager and select Refresh so the new models appear.
10. If an imported workflow still reports missing components, use Install Missing Custom Nodes.
11. Check whether the extension requires additional files in a manually created directory.

This pattern is repeated throughout the module. Upscaling adds model files and, for selective output control, an Image Chooser node. Tiled upscaling adds Ultimate SD Upscale. ControlNet adds a model and a multi-preprocessor node. InstantID adds a node package, dependencies, face-analysis assets, an IP-Adapter file, and a ControlNet file.

Custom nodes make ComfyUI much more capable, but each extension adds dependencies and another potential failure point. A node may install correctly while a required model is still absent.

Large assets can consume several gigabytes. The ControlNet Union model used here is approximately 2.5 GB. The InstantID IP-Adapter and ControlNet files add several more gigabytes.

Refresh and restart are not interchangeable. Refresh is needed to expose newly installed model files in dropdowns; a restart is needed to load newly installed custom nodes and dependencies.

An automatic missing-node installer simplifies imported workflows, but it cannot guarantee that every separately hosted model or manually placed asset is present.

Use Manager as an extension and asset coordinator, not as a substitute for understanding dependencies. Successful installation means the node code, model files, supporting libraries, directory structure, and restart or refresh cycle are all complete.