Comfy-Org / Comfy-Org/ComfyUI_frontend
Anima Beta Controlnet Breaks
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 699
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 490
Description
### Prerequisites
- [x] I am running the latest version of ComfyUI
- [x] I have custom nodes enabled
### What happened?
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" → 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.,
### Steps to Reproduce
1. Update from update.bat
2. Select anima apply controlnet and check the Node 2.0 version
3. Update from manager
### How is this affecting you?
Crashes ComfyUI completely
### ComfyUI Frontend Version
1.45.21
### Browser
Chrome/Chromium
### Console Errors
```javascript
```
### Logs
```shell
```
### Additional Context
_No response_
Contributor guide
Research direction
Start by reproducing the two update paths described: update.bat versus ComfyUI Manager, then inspect the Anima Apply ControlNet workflow and the Node 2.0 ControlNet model selector. Compare the resulting frontend behavior and console or startup logs; done means Mage support and Kohya's Anima ControlNet workflow both function together without a crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100