Repository navigation
--enable-manager flag appears to disable ComfyUI‑Manager instead of enabling it #1562
Description
What happened?
On Ubuntu 24.04, using the latest Stability Matrix release with the latest ComfyUI, enabling the --enable-manager launch option causes ComfyUI‑Manager to be blocked by policy.
When launching ComfyUI through Stability Matrix with --enable-manager enabled, I get:
[START] ComfyUI-Manager
[ComfyUI-Manager] network_mode: public
Blocked by policy: /home/server/Data/Packages/ComfyUI2/custom_nodes/ComfyUI-Manager
If I disable the --enable-manager flag, ComfyUI‑Manager loads normally.
Launching ComfyUI manually via the venv (python main.py) also loads ComfyUI‑Manager without issues.
This suggests the --enable-manager flag is inverted or interfering with ComfyUI‑Manager’s policy handling.
Environment:
Ubuntu 24.04
Latest Stability Matrix release
Latest ComfyUI installed to use Python 3.12.11
ComfyUI‑Manager installed in custom_nodes/ComfyUI-Manager
Steps to reproduce
No response
Relevant logs
Version
2.15.6
What Operating System are you using?
Linux
Activity
NeuralFault commentedon Mar 8, 2026
The --enable-manager is for the new comfyui manager that is part of comfy now (as a python module) as per comfyUI's repo readme.
If both are enabled, the old custom node based one will conflict.
As of SM 2.15.6, comfy installs automatically handle the installation of the new official manager along with the launch argument to enable it.
It is pretty much the same manager but part of comfy now.
saccie commentedon Mar 8, 2026
Thanks, I will close the ticket.
icf20 commentedon Jul 22, 2026
still not solved