The exact “Loaded ComfyUI-Manager” wording does not appear in the current official Manager source, so it has no fixed modern meaning. Verify the installation with the markers your version actually prints: Manager config and log paths, [PRE], [START], import timing, errors, and the completed-startup line.
What the "Loaded ComfyUI-Manager" log message means
The exact "Loaded ComfyUI-Manager" wording is not present in the current official Manager source, so do not assign it a fixed meaning across versions. It can appear in version-specific or third-party output, while current builds use more specific markers. Verify the markers from the process you launched instead of treating one copied line as a health check.
The absence of that exact phrase does not prove that Manager failed or that its folder is wrong. Start with the messages your installed version actually writes, then check for an error after them and verify which Manager interface you enabled.
Current ComfyUI-Manager startup log markers
A healthy startup can include some—not necessarily all—of these lines:
[PRE] ComfyUI-Manager
** ComfyUI-Manager config path: .../user/__manager/config.ini
** Log path: .../user/comfyui.log
[START] ComfyUI-Manager
[ComfyUI-Manager] network_mode: public
[ComfyUI-Manager] All startup tasks have been completed.[PRE] ComfyUI-Managershows that Manager's pre-start hook began. A PRE-only sequence can be intentional when--disable-manager-uiis set.[START] ComfyUI-Managershows thatcomfyui_manager.start()ran. Do not expect this line when the UI-disable flag prevents that start call.ComfyUI-Manager config pathandLog pathtell you which user directory and log file this process is using.- A Manager entry under custom-node import or prestartup timing identifies the package path and how long it took to load.
All startup tasks have been completedconfirms Manager's post-start work ended. It belongs to the START path, not the PRE-only--disable-manager-uipath.
Log message → meaning → next fix
| What you see | What it means | What to do next |
|---|---|---|
| No Manager lines | Manager may not be enabled in this launch command. | Use the install mode below and confirm --enable-manager is on the process you actually started. |
[PRE] but no [START] | This is intentional with --disable-manager-ui; otherwise startup may have stopped before Manager's start call. | Check the real launch flags and read the first traceback between PRE and the server startup lines. |
| Manager starts, UI missing | You may be looking for the old layout, using a stale browser tab, or connected to another process. | Open the current interface as described below, then confirm the browser and terminal belong to the same ComfyUI process. |
(IMPORT FAILED) or import failed | The first traceback may show missing or incompatible dependencies, a syntax or runtime error, or ComfyUI API incompatibility. | Read the first traceback. Only when it reports ModuleNotFoundError or a missing package should you install that node's requirements with the exact Python executable printed in the log. |
Blocked by policy | Manager's security policy rejected an operation or legacy package path. | Use a registered package or the current built-in Manager where possible. Review the official security-level documentation before weakening policy. |
| Network, GitHub, or certificate error | Manager started but could not fetch registry or repository data. | Check proxy, DNS, Git, certificate trust, and the official troubleshooting steps. Do not treat a network failure as an install-path failure. |
Install or enable Manager for your ComfyUI setup
ComfyUI Desktop
Manager is included and enabled by default in current ComfyUI Desktop releases. Do not clone a second copy into custom_nodes unless the official instructions for your exact version tell you to use the legacy extension.
Windows Portable
From the portable root, install the built-in Manager dependencies:
.python_embededpython.exe -m pip install -r ComfyUImanager_requirements.txtThen launch the same installation with Manager enabled:
.python_embededpython.exe -s ComfyUImain.py --windows-standalone-build --enable-managerManual install or virtual environment
Activate the environment that runs ComfyUI, then use:
pip install -r manager_requirements.txt
python main.py --enable-managerContainer and service installs need the same two pieces in their image or service definition: Manager requirements in the active Python environment and --enable-manager in the real startup command.
Legacy custom-node installation
Older setups can still use the ComfyUI-Manager repository as a custom node. Put one repository checkout at ComfyUI/custom_nodes/comfyui-manager, install its requirements.txt with ComfyUI's Python environment, and restart. Avoid double-nested paths such as custom_nodes/comfyui-manager/ComfyUI-Manager.
Where the Manager UI moved
In the new interface, use the Plugin icon or Menu/Help → Manage Extensions. It has filters on the left, Node Pack and Node search at the top, and a detail panel on the right. The legacy interface places the Manager button on the main top menu. To request that layout from a non-Desktop launch, use both flags:
python main.py --enable-manager --enable-manager-legacy-uiThe flag --disable-manager-ui prevents Manager's start call and endpoints. Seeing [PRE] without [START] can therefore be intentional with that flag; a completed-startup line is not the expected combination.
ComfyUI-Manager update vs git pull
| What you installed | Supported update path |
|---|---|
| ComfyUI Desktop | Use automatic updates or Menu → Help → Check for Updates. |
| Windows Portable core | Run update\update_comfyui.bat, then run .\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt. |
| Manual or virtual-environment core | Run git pull, then install both requirements.txt and manager_requirements.txt in that active environment. |
| Built-in Manager source | The Manager UI's Update ComfyUI action updates core and installs Manager requirements for the updated core. |
| Registry custom node | Use the Update available filter, choose the version, update, and restart. |
| Manually cloned custom node | Run git pull inside that node repository, reinstall its requirements with the same ComfyUI Python, and restart. |
| Legacy cloned Manager | Use git pull and reinstall its requirements.txt. Use the official repair command only when that pull fails. |
Missing nodes after opening a workflow
The new Manager prompt can offer Install All or Open Managerwhen a workflow references missing registered nodes. Review the proposed packs before installing. Core nodes may indicate that ComfyUI itself needs an update, while unregistered custom nodes require the author's documented manual installation path.
ComfyUI-Manager log FAQ
Does "Loaded ComfyUI-Manager" mean the install is healthy?
No. The wording has no fixed meaning in the current official source. Check the version's PRE, START, config, log, import, and completion lines, then verify the intended UI mode.
Where is the full log file?
Use the ** Log path: line printed at startup. Current Manager versions also print the active ComfyUI-Manager config path, which helps catch cases where you launched a different user directory than expected.
Why do I see Manager startup lines but no button?
Check for --disable-manager-ui, confirm whether you are using the new or legacy interface, and make sure the browser is connected to the same ComfyUI process whose terminal you inspected.
Should I use git pull or the Manager Update button?
Use the Manager UI for registered custom-node versions. Use git pull only for a repository checkout you intentionally manage with Git, such as a legacy Manager installation.
Primary sources reviewed
- ComfyUI-Manager overview
- Official installation modes and launch flags
- Official troubleshooting and security policy
- New UI custom-node management
- Legacy Manager UI
- Official ComfyUI update paths
- Current ComfyUI Manager launch integration
- Comfy-Org/ComfyUI-Manager source repository
What to build with ComfyUI Manager installed
Once Manager is enabled, use its registry and missing-node tools carefully: custom nodes execute code in your ComfyUI environment, so review the author, repository, dependencies, and permissions before installing. For the broader character and content-production curriculum, see AI Influencers Academy.
Adjacent: ComfyUI installation guide, what is ComfyUI, LoRA training, and the full AI Influencers library.