How to Install ComfyUI Manager (2026): Every Method + Fixes

ComfyUI Manager is the first thing everyone installs, because it lets you add custom nodes, fix “missing node” errors and download models from inside ComfyUI. In 2026 the way you install it changed: the Manager is now built into ComfyUI core and you just switch it on.

This guide covers every install method (Desktop, Windows portable, manual, the old git clone route and comfy-cli), how to use the new Manager UI, how to fix the security level error, and every common problem I see people hit.

TL;DR

Desktop app: nothing to install. Manager ships with it and starts with --enable-manager.
Portable: run .\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt, then start with --enable-manager.
Manual install: pip install -r manager_requirements.txt, then python main.py --enable-manager.
Old method still works: git clone into custom_nodes/comfyui-manager.
Want the old look? Add --enable-manager-legacy-ui.
“Not allowed with this security level”? Edit config.ini in ComfyUI/user/__manager/.

What ComfyUI Manager Does

ComfyUI Manager is the official extension for managing everything you add to ComfyUI. It is maintained in the Comfy-Org/ComfyUI-Manager repository.

Custom nodes: search, install, update, disable and remove node packs.
Missing nodes: detect the nodes a downloaded workflow needs and install them in one click.
Models: download and manage models from several sources.
Snapshots: save the state of your install and restore it if an update breaks something.

If you are new to custom nodes, my must-have ComfyUI custom nodes list is a good next stop once the Manager is working.

Which Install Method Should You Use?

Your ComfyUI	Method	Effort
ComfyUI Desktop app	Already included	None
Windows portable (ComfyUI_windows_portable)	pip install from manager_requirements.txt + flag	2 commands
Manual install with venv (Windows, Linux, Mac)	pip install from manager_requirements.txt + flag	2 commands
Older ComfyUI without manager_requirements.txt	git clone into custom_nodes	1 command + restart
Fresh install from scratch	comfy-cli	4 commands

How to tell which you have: look in your ComfyUI folder. If you see manager_requirements.txt next to main.py, use the new built-in method. If not, update ComfyUI first or use the git clone method.

Method 1: ComfyUI Desktop

The Desktop app installs the Manager with every installation and starts it with --enable-manager automatically. There is nothing to install.

Open ComfyUI Desktop and go to the installation’s Manage panel.
Open the Startup Args tab.
Pick a Manager Security Level: Strict, Standard (recommended), Relaxed or Permissive.
Pick a Manager Network Mode: Public, Private, Offline or Personal cloud.
Restart. Settings apply on the next launch.

Prefer the old Manager window? In Desktop, go to Server Settings, UI Settings and turn on Use legacy manager interface.

Method 2: Windows Portable

Open a terminal (PowerShell or Command Prompt) inside your ComfyUI_windows_portable folder. The quickest way is to type cmd in the Explorer address bar and press Enter.

Install the Manager’s requirements with the embedded Python:
.\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt
Start ComfyUI with the Manager enabled:
.\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --enable-manager
To make this permanent, open run_nvidia_gpu.bat in Notepad and add --enable-manager to the end of the line that starts ComfyUI. Save it, then start ComfyUI with that file as usual.

Tip: Copy the .bat file first, for example to run_nvidia_gpu_manager.bat, so an update does not overwrite your change. My ComfyUI command line arguments guide explains the other flags you can add to the same line.

Yes, “python_embeded” is spelled that way on purpose. It is the real folder name, so do not correct it.

Method 3: Manual Install (venv)

If you installed ComfyUI with git and a virtual environment, do this from the ComfyUI folder.

Activate your virtual environment.
Windows: venv\Scripts\activate
Linux and macOS: source venv/bin/activate
Install the Manager:
pip install -r manager_requirements.txt
Start ComfyUI with it:
python main.py --enable-manager

ComfyUI core pins the Manager version in manager_requirements.txt. That keeps the Manager matched to your ComfyUI version.

Method 4: Git Clone (Legacy, Custom Node)

This is the classic way, and it still works. Use it on older ComfyUI builds or if you prefer the Manager as a normal custom node.

Install Git for Windows if you are on Windows.
Open a terminal in ComfyUI/custom_nodes.
Run:
git clone https://github.com/Comfy-Org/ComfyUI-Manager comfyui-manager
Go into the new folder and install its requirements with the same Python ComfyUI uses:
cd comfyui-manager
pip install -r requirements.txt
Restart ComfyUI.

For the portable build there is also a one-click script. Save install-manager-for-portable-version.bat from the scripts folder of the Manager repository into ComfyUI_windows_portable (right-click the link and choose Save As) and double-click it.

Folder must be exact: the Manager has to live at ComfyUI/custom_nodes/comfyui-manager. Do not unzip a ZIP download into custom_nodes, and avoid ComfyUI-Manager-main or a double folder like ComfyUI-Manager/ComfyUI-Manager. It may seem to work but will not update properly.

Note that switching between the new and legacy UI only works for the pip (built-in) install. The git clone version uses its own interface.

Method 5: comfy-cli

comfy-cli installs ComfyUI and the Manager together. You need Python 3 and git.

Windows:

python -m venv venv
venv\Scripts\activate
pip install comfy-cli
comfy install

Linux and macOS:

python -m venv venv
. venv/bin/activate
pip install comfy-cli
comfy install

On Linux there is also an install-comfyui-venv-linux.sh script in the Manager repository. Run it in an empty folder, then start with ./run_gpu.sh or ./run_cpu.sh.

Manager Startup Flags

Flag	What it does
`--enable-manager`	Turns the built-in Manager on
`--enable-manager-legacy-ui`	Uses the old Manager window instead of the new one (needs `--enable-manager`)
`--disable-manager-ui`	Hides the Manager UI and endpoints but keeps background features (needs `--enable-manager`)
`--user-directory`	Moves the user folder, which also moves the Manager’s `config.ini`

Example for the legacy UI on a manual install: python main.py --enable-manager --enable-manager-legacy-ui

How to Use the New Manager

After starting with --enable-manager, open the Manager from the ComfyUI menu bar. In the new UI it opens as a full panel with node pack cards.

Install a node pack

Type the name in the top search bar. Use the Filter dropdown to switch between Node Pack and Individual Node search.
Click the pack’s card to open its details.
Click Install, or choose a specific release under Version first.
Restart ComfyUI when asked, then refresh the browser tab.

Install missing nodes for a workflow

Load the workflow (drag the JSON or PNG into ComfyUI).
A prompt lists the missing nodes. Click Install All, or Open Manager to check them first.
You can also select a red node and click Missing in the preview panel.
Restart ComfyUI. If nodes are still red, read the terminal log, because a pack may have failed to install its Python packages.

Update and uninstall

Update: pick the Update available filter in the left sidebar. Packs with an update show an arrow. Choose a version and click Update.
Uninstall: select the pack and click Uninstall in the preview panel.

Installed a pack and models still will not load? Check you put the files in the right folder with my ComfyUI model folders cheat sheet.

Security Levels and config.ini

Custom nodes run Python code on your PC, so the Manager limits risky actions by default. The setting lives in config.ini:

ComfyUI v0.3.76 and newer: ComfyUI/user/__manager/config.ini
Older versions: ComfyUI/user/default/ComfyUI-Manager/config.ini

Set security_level = normal (or another value) in the [default] section.

Level	What it blocks	Use when
`strong`	High and middle risk actions	Shared or exposed servers
`normal`	High risk actions	Default for most people
`normal-`	High risk only when `--listen` uses a non-127 address	Local PC that is sometimes shared on LAN
`weak`	Nothing	Only briefly, to install a trusted git URL or nightly pack

High risk actions are installs from a git URL, pip installs, installs from non-default channels and “fix” actions. Middle risk covers uninstall, update, default-channel installs, snapshots and restart.

Newer Manager versions also have separate switches, allow_git_url_install and allow_pip_install, which are false by default. Flagged pack versions are controlled by allow_flagged_nodepack_install.

Safety: if you set weak to install something, set it back to normal afterwards. Never use weak on a ComfyUI that is reachable from the internet, for example a cloud GPU.

How to Update ComfyUI Manager

Desktop: update the ComfyUI engine from the Manage panel’s Update tab.
Portable or manual (built-in): run the pip install -r manager_requirements.txt command again, then restart with --enable-manager. Updating ComfyUI alone may leave the Manager on the old version.
Git clone: run git pull inside ComfyUI/custom_nodes/comfyui-manager, then restart.

Take a snapshot in the Manager before big updates. If something breaks, restore the snapshot instead of reinstalling.

Troubleshooting

No Manager button after install

You probably started ComfyUI without --enable-manager. Check the first lines of the terminal for the command that ran. On portable, make sure you edited the .bat file you actually launch.

“This action is not allowed with this security level configuration”

You tried a git URL install or a nightly version. Open config.ini (see the paths above), set security_level = weak, restart, install, then set it back to normal.

ModuleNotFoundError after enabling the Manager

The requirements were installed into the wrong Python. On portable, always use .\python_embeded\python.exe -m pip, not your system pip. On a manual install, activate the venv first.

Manager installed twice or nodes show duplicates

You likely have both the built-in Manager and an old custom_nodes/comfyui-manager folder. Keep one. If you use the built-in version, move the old folder out of custom_nodes.

“Overlapped Object has pending operation at deallocation”

A Windows event loop issue. Add windows_selector_event_loop_policy = True to config.ini and restart.

SSL: CERTIFICATE_VERIFY_FAILED

Often caused by antivirus or a company proxy. Add bypass_ssl = True to config.ini. Only do this on a network you trust.

Git not found

Install Git, or set git_exe = C:\Program Files\Git\bin\git.exe (your full path) in config.ini.

Manager update fails (git clone install)

From the comfyui-manager folder, run:
git update-ref refs/remotes/origin/main a361cc1 && git fetch --all && git pull

Installed nodes are still red

Restart ComfyUI fully, not just the browser tab. Then read the terminal for “IMPORT FAILED” lines. My ComfyUI errors and fixes guide covers the most common ones, and the SageAttention install guide helps when a pack needs compiled packages.

My Take

On a portable install, the built-in route is the cleanest: two commands and one flag in your .bat file. It keeps the Manager matched to your ComfyUI version, which avoids a lot of strange breakage.

Keep the security level on normal and only drop to weak for a single trusted install. Custom nodes are code, and the Manager’s checks are your main protection.

Finally, make a snapshot before every big update. It takes seconds and saves hours.

FAQ

Is ComfyUI Manager built into ComfyUI now?

Yes. The Manager is part of ComfyUI core, but you must enable it with --enable-manager after installing manager_requirements.txt. The Desktop app enables it for you.

How do I install ComfyUI Manager on the portable version?

From the portable folder, run .\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt, then add --enable-manager to your run .bat file.

Can I still install ComfyUI Manager with git clone?

Yes. Clone https://github.com/Comfy-Org/ComfyUI-Manager into ComfyUI/custom_nodes/comfyui-manager, install its requirements and restart.

How do I get the old ComfyUI Manager interface back?

Start with --enable-manager --enable-manager-legacy-ui, or in Desktop turn on “Use legacy manager interface” in Server Settings.

Where is the ComfyUI Manager config.ini?

In ComfyUI/user/__manager/config.ini on ComfyUI v0.3.76 and newer, or ComfyUI/user/default/ComfyUI-Manager/config.ini on older versions.

How do I install missing nodes in ComfyUI?

Load the workflow, then click Install All in the missing nodes prompt. Restart ComfyUI afterwards.

Is ComfyUI Manager safe?

The Manager itself is official, but custom nodes run code on your machine. Keep the security level on normal and install popular, maintained packs.

How to Install ComfyUI Manager (2026): Built-in Method, Portable, Git and Fixes