Comfy-Org / Comfy-Org/ComfyUI-Manager

Updating from manger quit support for Mage in comfyui

Open
#3,109 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
16.1k
Forks
2.5k
Avg merge
5d 4h
Merged PRs (30d)
13

Description

I'm not sure whether I should report this to ComfyUI Support, ComfyUI Manager, or somewhere else, so I'll explain what happened.

I updated ComfyUI using "update.bat", and after that I got Mage support. However, because I also have Kohya's Anima ControlNet node installed, ComfyUI starts loading the native ControlNet Nodes 2.0 (Beta) implementation instead.

When that happens, my Anima workflow breaks because I can no longer select a ControlNet model unless I enable Nodes 2.0. The ControlNet model selector simply doesn't appear/work correctly.

Then I tried updating through ComfyUI Manager instead of "update.bat". In that case, Kohya's ControlNet works again and I can use my Anima workflow normally. However, I lose Mage support.

So right now I seem to have two mutually exclusive situations:

Updating with "update.bat" (I use the portable version) → Mage works, but Kohya's Anima ControlNet breaks because Nodes 2.0 (Beta) gets loaded.,
Updating through ComfyUI Manager → Kohya's Anima ControlNet works again, but Mage support is lost.,

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the two update paths described: portable update.bat and the ComfyUI Manager, with Mage and Kohya's Anima ControlNet installed. Compare which components load, including native ControlNet Nodes 2.0, and document or verify a supported outcome in which Mage and the Anima workflow both work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.