Upstream model manager to ComfyUI core

[huchenlei]

Hi @hayden-fr,

Thank you for your excellent contributions on both ComfyUI-Model-Manager and ComfyUI-Image-Browsing. The features you've implemented address two critical gaps in ComfyUI's functionality that would benefit the entire user base.

I'd like to propose upstreaming both projects to the core repositories (ComfyUI_frontend and ComfyUI). This integration could help standardize these essential features for all users.

If you're interested in discussing this further, I'm available on the ComfyUI Discord server (username: HCL). I'd be happy to help facilitate the process or discuss any concerns you might have.

[hayden-fr]

Thx for invitation.

There are some questions. If upstreaming the project to the core repository, how should I resolve the conflict for users who already have the extension installed. I mean what should I do to avoid possible conflict like duplication UI, and whether users who have installed extensions need to be prompted to remove existing, etc

[huchenlei]

We currently have a disabled extension list that you can use to disable extensions that have been upstreamed to core: https://github.com/Comfy-Org/ComfyUI_frontend/blob/ee5c1271461f90194dfa032d61f035d49a52eeab/src/stores/extensionStore.ts#L71-L83

You can just add Comfy.ModelManager there to bypass the extension hooks after you upstreamed the feature.