• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
  • Skip to footer
Best Free Web Resources — local AI tools and hardware guides

Best Free Web Resources

Local AI Tools & Digital Engineering Resources

What can I run?
  • AI Tools
    • Start: Local LLMs
    • Ollama Models & VRAM
    • LM Studio Models
    • GPU Comparison
    • AI Hardware Matrix
    • Local LLM Directory
    • VRAM Calculator
    • Hardware Compare
    • Local Model Recommender
    • API Pricing & ROI
  • Local AI Guides
  • Web Resources
    • Inspiration
    • Photography
    • Games
    • SEO
    • Tutorial
      • Coding
      • WordPress
    • Resume/CV
    • Graphics
      • Logo
    • Freebies
Cover illustration: Where the Manager Went

ComfyUI Manager Not Showing: Why, and How to Fix It in 2026

November 18, 2026 by Rupesh Kumar

If the Manager button is missing in ComfyUI, the usual reason is that it is switched off. Since December 2025, ComfyUI-Manager is a pip package that ComfyUI core loads only when it starts with --enable-manager, and Windows Portable and manual installs do not pass that flag. When it is on, the button is no longer labelled Manager: in the new interface it is an icon in the top bar whose tooltip reads Extensions. Comfy Desktop turns it on for you; Portable and manual installs need two steps, pip install -r manager_requirements.txt and the flag.

This guide explains each reason the button goes missing in ComfyUI v0.45.0 (released 10 November 2026), then gives the fix for Portable, manual and Desktop installs, how to get the old Manager button back, and the security settings that block installs once it appears. BFWR has not run these steps. They come from ComfyUI’s and ComfyUI-Manager’s own documentation, source code and GitHub issues, read on 15 November 2026.

Quick answer

  • Portable (Windows): run .\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt, then add --enable-manager to the line in run_nvidia_gpu.bat.
  • Manual install: activate your venv, run pip install -r manager_requirements.txt, start with python main.py --enable-manager.
  • Desktop: open the installation’s Manage panel, Startup Args tab, and check that --enable-manager is there. Installs you imported from Portable or git do not get it by default.
  • Look for the right button: a blocks icon with the tooltip Extensions, or C menu → Extensions. The dialog it opens is titled “Nodes Manager”.
  • “ComfyUI-Manager upgrade required” toast and no button: you passed the flag but the package is missing or older than 4.2.1. Install manager_requirements.txt again.
  • Want the old Manager button: pass both flags, --enable-manager --enable-manager-legacy-ui. The legacy flag on its own leaves the button hidden.

Why the Manager button disappeared

ComfyUI-Manager used to be a custom node you cloned into ComfyUI/custom_nodes/comfyui-manager. It added a Manager button to the menu bar, and it loaded on every start. That changed on 2 December 2025, when ComfyUI merged PR #7555, “feat: Support ComfyUI-Manager for pip version”. The Manager’s version 4 notes describe the change as “Modify the structure to be installable via pip instead of using git clone.”

ComfyUI’s documentation now says, for both Portable and manual installs, that “the new ComfyUI-Manager is built into ComfyUI core but needs to be enabled.” Eight days after the change, issue #2374 opened on the Manager repository, “ComfyUI-Manager disappered after updating comfyui desktop”. It has 51 comments and is still open.

Three things now have to line up before anything appears:

  1. The package is installed. ComfyUI pins the version it works with in manager_requirements.txt. On 15 November that file reads comfyui_manager==4.2.2, while PyPI’s newest release is 4.3 (18 September). The pin is not in ComfyUI’s main requirements.txt, so a normal install or update does not install it.
  2. ComfyUI starts with --enable-manager. The frontend reads ComfyUI’s raw command line, and in useManagerState.ts it hides every Manager control unless that exact argument is present.
  3. You look for the right label. The top-bar button is icon-only. Its tooltip, from the frontend’s English strings, is Extensions. A draft frontend PR (#17424) by a Comfy-Org member lists the problem plainly: “One feature had five names”, including Extensions for the toolbar button and Nodes Manager for the dialog. It proposes renaming the button “Custom Nodes”, but it has not merged.

There is a second trap in the C menu. It always lists Extensions, but when the Manager is off, the frontend’s openManager function opens Settings at the Extension panel instead. That panel lists ComfyUI’s JavaScript extensions, not custom node packs, which is why commenters on issue #2374 found the Extensions entry useless.

The common causes, by symptom

What you see Cause Fix
No button, no toast ComfyUI started without --enable-manager Add the flag (steps below)
Toast “ComfyUI-Manager upgrade required”, no button Flag passed, package missing or older than 4.2.1 Install manager_requirements.txt in the Python ComfyUI runs on
Old cloned Manager stopped loading With the flag, core skips any custom_nodes folder whose name contains comfyui-manager Use the built-in Manager, or remove the flag to keep the clone
Only --enable-manager-legacy-ui set, no button Frontend looks for the literal --enable-manager Pass both flags
Manager present but broken after hiding partner nodes --offline or the old --disable-api-nodes Use --disable-partner-nodes instead
Desktop, imported install, no button Imported Portable and git installs start without the flag Add it in Startup Args

The “upgrade required” toast when you never installed anything

This is the most confusing case. Draft PR #16258, opened from a Comfy-Org member’s account, explains it. If you add --enable-manager but the package is not installed, main.py prints a warning and switches the Manager off. The terminal shows:

To use the `--enable-manager` feature, the `comfyui-manager` package must be installed first.

The frontend, though, still sees the flag on the raw command line, and core always reports that it supports the version 4 Manager. With no package running to report the rest, the frontend decides the Manager is incompatible, hides the button and shows a toast that says “Please upgrade ComfyUI-Manager to version 4.2.1 or higher.” The PR puts it bluntly: the warning is “about a package the user never installed”. The fix is to install manager_requirements.txt into the same Python environment ComfyUI runs from.

The same toast appears if you installed an older 4.x package months ago and have since updated ComfyUI. ComfyUI’s docs warn that “Updating ComfyUI may leave the installed Manager package unchanged.” The Portable updater, update_comfyui.bat, checks requirements.txt and not the Manager pin, so re-run the Manager install after updating.

The old cloned Manager and the new one

If you still have the old clone in custom_nodes, the pip package switches it off. Its should_be_disabled function skips any custom node folder whose name contains comfyui-manager whenever --enable-manager is set. Without the flag, the clone (now version 3.42 on the repository’s main branch) still loads as an ordinary custom node. ComfyUI’s docs add that “Versions installed via custom nodes do not support switching to the new UI.” Pick one: the built-in package with the flag, or the clone without it.

Hiding paid partner nodes broke the Manager

Many people added --disable-api-nodes to hide the paid API nodes. Since v0.39.0 that flag is a “Deprecated alias for –offline”, and --offline blocks the frontend from reaching the internet with a strict Content-Security-Policy header. The Manager needs the internet to list node packs. In issue #14887, ComfyUI maintainer comfyanonymous answered that the option “is meant for people who don’t want core ComfyUI code (and frontend) to communicate in any way with online servers so of course it’s going to break manager a bit.” If you only want the partner nodes gone, the newer flag is --disable-partner-nodes, described in ComfyUI’s help text as “Disable loading partner nodes (the paid API nodes). The frontend keeps its internet access.”

Fix on Windows Portable

The Portable download still launches without the Manager: on 15 November, run_nvidia_gpu.bat contains .\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build and nothing else. PR #16258, which would turn the Manager on by default, is an open draft. Its author describes today’s situation: “Portable users must install a pip package and hand-edit a .bat file before the custom node manager appears.”

  1. Close ComfyUI. Open a terminal in the ComfyUI_windows_portable folder (the one that contains python_embeded).
  2. Install the Manager package with the embedded Python, exactly as ComfyUI’s docs give it:
    .\python_embeded\python.exe -m pip install -r ComfyUI\manager_requirements.txt
  3. Open run_nvidia_gpu.bat in a text editor (or run_amd_gpu.bat / run_intel_gpu.bat) and add the flag to the launch line:
    .\python_embeded\python.exe -s ComfyUI\main.py --windows-standalone-build --enable-manager
    pause
  4. Start ComfyUI from that file. In the terminal, look for [START] ComfyUI-Manager and the line giving the config.ini path.
  5. In the browser, find the blocks icon in the top bar (tooltip Extensions), or open C menu → Extensions.

If you launch from a file in the advanced folder, the paths start with ..\ instead of .\. The run_nvidia_gpu_disable_api_nodes.bat file there now passes --offline, which is the setting that breaks the Manager.

Fix on a manual (git) install

  1. Open a terminal in your ComfyUI folder and activate the virtual environment you run it from:
    # Windows
    venv\Scripts\activate
    
    # Linux/macOS
    source venv/bin/activate
  2. Install the pinned Manager package:
    pip install -r manager_requirements.txt

    If you use uv, ComfyUI’s own warning message offers uv pip install -r manager_requirements.txt as the alternative.

  3. Start ComfyUI with the flag:
    python main.py --enable-manager
  4. If a script or service file starts ComfyUI, add the flag there too.

The comfy-cli route (pip install comfy-cli, then comfy install) installs the Manager for you; its README lists comfy install --skip-manager as the way to leave it out.

Fix on Comfy Desktop

ComfyUI’s docs say “Comfy Desktop installs ComfyUI-Manager with every ComfyUI installation and starts it with” the --enable-manager flag. In Desktop’s source, new installs default to exactly --enable-manager. Installs you bring in are different: an adopted Portable install defaults to --windows-standalone-build --disable-auto-launch, and an adopted git install to no arguments at all. Neither turns the Manager on.

  1. In Comfy Desktop, open the installation, then go to the Manage panel and the Startup Args tab.
  2. In Startup Arguments, make sure --enable-manager is present, and that --disable-manager-ui is not. That second flag hides the Manager interface while its background tasks keep running.
  3. Relaunch the installation. Desktop’s docs note that Manager options apply “the next time you launch the installation.”

The legacy interface is a setting on Desktop: Server Settings → UI Settings → Use legacy manager interface.

Getting the old Manager button back

The version 4 package still ships the old interface. Start ComfyUI with both flags:

python main.py --enable-manager --enable-manager-legacy-ui

ComfyUI’s argument parser treats the legacy flag as implying the first one. The frontend does not. Its check needs the literal --enable-manager in the command line, so the legacy flag alone leaves you with no button. That fits issue #2993, “-enable-manager-legacy-ui isn’t working, no manager button in the bar”, open since June. A frontend fix, PR #13736 “fix: honor implied legacy Manager enablement”, has been open since 16 July. Until it merges, pass both.

The Manager appears but refuses to install

Once the Manager is back, its security settings decide what it may do. They live in config.ini, which for current ComfyUI is at ComfyUI/user/__manager/config.ini (the terminal prints the exact path at start-up). The default security_level in the 4.2.2 source is normal, which allows installing and updating registered node packs on a local machine.

Installing from a git URL and running arbitrary pip install are no longer controlled by security_level. In Manager 4.2.2 and later they have their own switches, allow_git_url_install and allow_pip_install, and both default to off. Any value other than true counts as off. To allow git-URL installs on your own machine:

[default]
security_level = normal
allow_git_url_install = true

The README adds that “Changes to these flags require a restart of ComfyUI to take effect”, and that even with a flag enabled, “the feature is denied when the server listener is non-local” unless network_mode is personal_cloud. Be aware that ComfyUI’s own troubleshooting page still says “To install custom nodes via git URL or nightly versions, set” security_level = weak. That advice predates the dedicated flags; the Manager’s README says weak no longer opens those two features.

Keep it on 127.0.0.1

ComfyUI listens on 127.0.0.1 by default, and --listen with no address opens it on every network interface. With the Manager on, that matters more. An open report on the Manager repository (#3440, filed 26 October by a user, not yet answered by the maintainers) says “The ComfyUI-Manager HTTP API has no authentication” and describes a compromised instance that was reachable over the network. Leave --listen off unless you need another machine to connect, and if you do, put authentication in front of ComfyUI.

FAQ

Is ComfyUI-Manager discontinued?

No. It moved. The repository is Comfy-Org/ComfyUI-Manager, it is not archived, and on 15 November its manager-v4 branch had 28 commits in the last 90 days, with the last one that morning. The main branch holds the old custom-node version (3.42) and is also still updated.

Why does the button say Extensions instead of Manager?

That is the frontend’s current English label for the new Manager’s top-bar button and C-menu entry. The dialog behind it is titled “Nodes Manager”. A rename to “Custom Nodes” is proposed in frontend PR #17424, which is still a draft.

Did ComfyUI v0.43 to v0.45 change any of this?

Not that the release notes show. None of the v0.43.0, v0.44.0 or v0.45.0 notes mentions the Manager, and v0.45.0 still pins comfyui_manager==4.2.2. A PR to move the pin to 4.3 (#16410) is open.

Related guides and tools

  • ComfyUI install in 2026: Desktop vs Portable vs manual
  • ComfyUI templates in 2026: 660 built in, and half need the cloud
  • Stability Matrix: one installer for ComfyUI, Forge and InvokeAI
  • SwarmUI in 2026: when to use it instead of ComfyUI
  • ComfyUI hub: models, VRAM and workflows
  • Image generation VRAM calculator

Sources

  • ComfyUI docs: ComfyUI-Manager installation and troubleshooting
  • Comfy-Org/ComfyUI-Manager, manager-v4 branch README (security policy and install flags)
  • ComfyUI manager_requirements.txt, main.py and cli_args.py
  • Portable launcher run_nvidia_gpu.bat
  • ComfyUI frontend useManagerState.ts
  • ComfyUI PR #16258 (Portable default-enable, draft)
  • Frontend PR #17424 (rename, draft) and PR #13736 (legacy flag fix)
  • Issues: Manager #2374, Manager #2993, Manager #3440, ComfyUI #14887
  • ComfyUI releases and comfyui-manager on PyPI

Updated 15 November 2026. ComfyUI v0.45.0, the manager_requirements.txt pin (4.2.2), PyPI’s comfyui-manager 4.3, the frontend source and labels (v1.61.2), Comfy Desktop’s default launch arguments, ComfyUI’s Manager docs and the cited issues and PRs were read on that date.

⚡ Free Interactive Tools

Work out what your hardware can actually run

Free calculators and directories, sized from real model weights — before you download gigabytes or order a card:

🎨 ComfyUI VRAM Peak memory per image model 🚀 Start: Local LLMs Hardware, runner and first model 📊 What Can I Run? Models by VRAM tier, 8GB–128GB 💻 Hardware Matrix 75 laptops & GPUs profiled

Filed Under: Technology, Tutorial

About Rupesh Kumar

Rupesh Kumar founded Best Free Web Resources in 2010 and edits the site. He writes about free web resources, web development and running open AI models locally. Learn more: About BFWR & our editorial standards → · Follow on X (@bestfreewebres) →

Primary Sidebar

⚡ FREE INTERACTIVE TOOLS

Local AI Hardware & VRAM Matrix

Benchmark your PC or Mac for local AI, calculate VRAM requirements, and compare cloud API costs vs local hardware ROI.

🚀 New here? Start with Local LLMs → 💻 Hardware Matrix (79 Devices) → 📚 Local LLM Directory (30 Models) → 🎮 AI GPU Comparison → ⚡ VRAM & KV Cache Calculator → 💰 API Pricing & Break-Even → 🍎 Mac VRAM Unlocker (90% Boost) →
📦 Ollama 🖥️ LM Studio ⚙️ llama.cpp 🚦 vLLM 💬 Open WebUI 🎨 ComfyUI 🔒 Self-Hosted 📊 VRAM Tiers 🎯 Recommender ⚖️ Comparisons

Search

  • Facebook
  • Instagram
  • RSS
  • Twitter
  • YouTube

Footer

Latest Guides

  • ComfyUI Manager Not Showing: Why, and How to Fix It in 2026
  • MiniMax H3 Image in ComfyUI: Files, VRAM, Settings and the Licence
  • LFM3 1.7B Locally: 256K Context in About 5GB, and the Licence Limit
  • Fooocus in 2026: Is It Still Worth Installing, and What to Use Instead
  • Gemma 4 31B Locally: VRAM, Context Length and Which GPU It Fits
  • 5 Ways You Can Make Business Operations Simple Without Upgrading Your Tech

AI Tools & Calculators

  • What can I run?
  • VRAM Calculator
  • GGUF Size Calculator
  • Fine-tuning VRAM
  • LoRA Training VRAM
  • Image Generation VRAM
  • Mac VRAM Optimizer

Browse & Compare

  • Models Directory (30 models)
  • Hardware Matrix (79 devices)
  • Image Models
  • Model Licences
  • Comparisons
  • Model Recommender
  • API Pricing & ROI

Guides & Resources

  • Technology
  • Coding
  • Tutorials
  • Freebies
  • Graphics

Copyright © 2026 · Best Free Web Resources · All Rights Reserved.  |  About · Privacy Policy · Contact · AI Tools Hub