[GH-ISSUE #1629] Manager: V3.30.3, how to disable auto FETCH ComfyRegistry Data on every startup?

bsakaguchi commented

2026-10-27 21:21:05 +00:00

Owner

Originally created by @tajino on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1629

Updated to Manager: V3.30.3, I noticed that on each startup, it auto fetch ComfyRegistry Data, previously there is an option checkbox (skip update check) to disable it, with a manual 'fetch' button in the Manager UI, I don't see this anymore in this version.

Possible to bring back this manual fetching and option to disable auto fetching (skip update check), for those who restarts ComfyUI a lot to test stuff. Thanks.

Originally created by @tajino on GitHub (Mar 8, 2025). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1629 Updated to Manager: V3.30.3, I noticed that on each startup, it auto fetch ComfyRegistry Data, previously there is an option checkbox (skip update check) to disable it, with a manual 'fetch' button in the Manager UI, I don't see this anymore in this version. Possible to bring back this manual fetching and option to disable auto fetching (skip update check), for those who restarts ComfyUI a lot to test stuff. Thanks.

bsakaguchi added the

bug

label

2026-10-27 21:21:05 +00:00

bsakaguchi commented

2026-10-27 21:21:06 +00:00

Author

Owner

@ltdrdata commented on GitHub (Mar 9, 2025):

The "skip update check" option is completely unrelated to this functionality.

FETCH DATA is performed in the background to keep the data up to date, whereas "skip update check" is an option that determines whether to skip checking for updates on nodes installed via git clone when displaying the list.
Currently, selecting "update" as the filter in the list performs the same function as unchecking "skip update check", so it was removed as it is no longer needed.

To disable FETCH DATA, you can change network_mode to private or offline.
https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config

@ltdrdata commented on GitHub (Mar 9, 2025): The **"skip update check"** option is completely unrelated to this functionality. **FETCH DATA** is performed in the background to keep the data up to date, whereas **"skip update check"** is an option that determines whether to skip checking for updates on nodes installed via `git clone` when displaying the list. Currently, selecting **"update"** as the filter in the list performs the same function as unchecking **"skip update check"**, so it was removed as it is no longer needed. To disable **FETCH DATA**, you can change **`network_mode`** to **`private`** or **`offline`**. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config

bsakaguchi commented

2026-10-27 21:21:06 +00:00

Author

Owner

@tajino commented on GitHub (Mar 9, 2025):

The "skip update check" option is completely unrelated to this functionality.

FETCH DATA is performed in the background to keep the data up to date,

Was this done as well for all the previous releases, just that it wasn't printed to the console before?

whereas "skip update check" is an option that determines whether to skip checking for updates on nodes installed via git clone when displaying the list. Currently, selecting "update" as the filter in the list performs the same function as unchecking "skip update check", so it was removed as it is no longer needed.

I tried selecting "update" as the filter, it starts to go through all installed custom nodes one by one in the console, and got stuck at "teacache" custom node for very long while. I closed the console window and relaunched it, upon startup, it seems to be running a startup script that run installation of every custom nodes's requirements.txt, is that how it is supposed to work if the update filter scan process wasn't completed properly?

To disable FETCH DATA, you can change network_mode to private or offline. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config

Thanks for pointing this out, I totally missed this piece of information.

@tajino commented on GitHub (Mar 9, 2025): > The **"skip update check"** option is completely unrelated to this functionality. > > **FETCH DATA** is performed in the background to keep the data up to date, Was this done as well for all the previous releases, just that it wasn't printed to the console before? >whereas **"skip update check"** is an option that determines whether to skip checking for updates on nodes installed via `git clone` when displaying the list. Currently, selecting **"update"** as the filter in the list performs the same function as unchecking **"skip update check"**, so it was removed as it is no longer needed. > I tried selecting **"update"** as the filter, it starts to go through all installed custom nodes one by one in the console, and got stuck at "[teacache](https://github.com/welltop-cn/ComfyUI-TeaCache)" custom node for very long while. I closed the console window and relaunched it, upon startup, it seems to be running a startup script that run installation of every custom nodes's requirements.txt, is that how it is supposed to work if the update filter scan process wasn't completed properly? > To disable **FETCH DATA**, you can change **`network_mode`** to **`private`** or **`offline`**. https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config Thanks for pointing this out, I totally missed this piece of information.

bsakaguchi commented

2026-10-27 21:21:06 +00:00

Author

Owner

@ltdrdata commented on GitHub (Mar 10, 2025):

The "Skip update check" option determines whether to check the update availability of the items displayed in the list. The update check process can take a long time, especially if there are many older custom nodes installed using the Git clone method. In environments like Colab, this process was extremely time-consuming, which is why this option was introduced.
Normally, it would have been used with this option always enabled. In this case, the update status of custom nodes would be uncertain, so instead of an "Update" button, a "Try Update" button would be displayed.
The issue of getting stuck can occur when a custom node has been deleted or its URL has been modified, making it inaccessible through the previous URL. This was not taken into account, but I will make the necessary fixes.

@ltdrdata commented on GitHub (Mar 10, 2025): 1. The "Skip update check" option determines whether to check the update availability of the items displayed in the list. The update check process can take a long time, especially if there are many older custom nodes installed using the Git clone method. In environments like Colab, this process was extremely time-consuming, which is why this option was introduced. Normally, it would have been used with this option always enabled. In this case, the update status of custom nodes would be uncertain, so instead of an "Update" button, a "Try Update" button would be displayed. 2. The issue of getting stuck can occur when a custom node has been deleted or its URL has been modified, making it inaccessible through the previous URL. This was not taken into account, but I will make the necessary fixes.

bsakaguchi commented

2026-10-27 21:21:07 +00:00

Author

Owner

@set-soft commented on GitHub (Mar 19, 2025):

Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download

@set-soft commented on GitHub (Mar 19, 2025): Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download

bsakaguchi commented

2026-10-27 21:21:07 +00:00

Author

Owner

@ltdrdata commented on GitHub (Mar 19, 2025):

Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download

The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously.

This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed.

@ltdrdata commented on GitHub (Mar 19, 2025): > Why is the data downloaded every time? I think it should avoid downloading the same data over and over. Like a browser does with webpages: first check if the file is newer or expired, then download The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously. This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed.

bsakaguchi commented

2026-10-27 21:21:07 +00:00

Author

Owner

@set-soft commented on GitHub (Mar 20, 2025):

This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed.

This is good news.

But the current behavior is unconditional download. I tried now: start server, wait until the data is downloaded, stop server, start again ... data downloaded again!

I pulled the last code from the main repo and the Manager and tried again, same behavior, registry data downloaded on each start. And I'm waiting for:

[ComfyUI-Manager] default cache updated: https://api.comfy.org/nodes
FETCH DATA from: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json [DONE]
[ComfyUI-Manager] All startup tasks have been completed.

@set-soft commented on GitHub (Mar 20, 2025): > This structure is currently being changed, and soon it will no longer rely on caching. Instead, it will fetch only the necessary data directly from the registry as needed. This is good news. But the current behavior is unconditional download. I tried now: start server, wait until the data is downloaded, stop server, start again ... data downloaded again! I pulled the last code from the main repo and the Manager and tried again, same behavior, registry data downloaded on each start. And I'm waiting for: ``` [ComfyUI-Manager] default cache updated: https://api.comfy.org/nodes FETCH DATA from: https://raw.githubusercontent.com/ltdrdata/ComfyUI-Manager/main/custom-node-list.json [DONE] [ComfyUI-Manager] All startup tasks have been completed. ```

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@bigcat88 commented on GitHub (Apr 18, 2025):

The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously.

Is it possible to add a feature to specify network_mode as a cmd parameter or as an env variable?

Editing "config.ini" for automated scripts that run ComfyUI on some service like RunPod.io is not so easy, as to pass param/env option to override it.

Local situation: I restart Comfy at least 20+ times a day and every time I got those downloads, and during last month the data it downloads from ComfyRegistry become bigger.
I needed those caches only when I need to updates Nodes or ComfyUI and that happens not so often. Edit every time the config.ini file is not very convinient(in local or remote environment).

Another variant will be to introduce some option to update those data only after period of time: once a day/once a week in addition to ability to easy ovveride network_mode to offline.

@bigcat88 commented on GitHub (Apr 18, 2025): > The current ComfyUI-Manager fetches the entire node list and stores it in a cache for use. Since some information becomes outdated quickly, the cached data needs to be updated continuously. Is it possible to add a feature to specify `network_mode` as a cmd parameter or as an env variable? Editing "config.ini" for automated scripts that run ComfyUI on some service like RunPod.io is not so easy, as to pass param/env option to override it. Local situation: I restart Comfy at least 20+ times a day and every time I got those downloads, and during last month the data it downloads from ComfyRegistry become bigger. I needed those caches only when I need to updates Nodes or ComfyUI and that happens not so often. Edit every time the `config.ini` file is not very convinient(in local or remote environment). Another variant will be to introduce some option to update those data only after period of time: once a day/once a week in addition to ability to easy ovveride `network_mode` to `offline`.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@ricperry commented on GitHub (May 3, 2025):

Once we have our ComfyUI environment configured correctly for our workflows (ie. we already have all the custom nodes we are going to use and are happy with how everything is performing), the need to have an up-to-date list of available custom nodes is completely superfluous. The bandwith expenditure for this task multiplied across all Comfy users is probably extremely high. It's irresponsible not to have a way to disable this behavior. Bury it somewhere deep so people can't accidentally disable it if you must.

@ricperry commented on GitHub (May 3, 2025): Once we have our ComfyUI environment configured correctly for our workflows (ie. we already have all the custom nodes we are going to use and are happy with how everything is performing), the need to have an up-to-date list of available custom nodes is completely superfluous. The bandwith expenditure for this task multiplied across all Comfy users is probably extremely high. It's irresponsible not to have a way to disable this behavior. Bury it somewhere deep so people can't accidentally disable it if you must.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@ltdrdata commented on GitHub (May 12, 2025):

The structure of ComfyUI-Manager is currently undergoing changes. In a future update, it will become cacheless, meaning the backend will no longer preload and compute cache in advance.

@ltdrdata commented on GitHub (May 12, 2025): The structure of ComfyUI-Manager is currently undergoing changes. In a future update, it will become cacheless, meaning the backend will no longer preload and compute cache in advance.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@TimPietrusky commented on GitHub (May 22, 2025):

@ltdrdata looking forward to this! let me know if you need any testers 🙏

@TimPietrusky commented on GitHub (May 22, 2025): @ltdrdata looking forward to this! let me know if you need any testers 🙏

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@seancheung commented on GitHub (Oct 4, 2025):

Updating the local registry cache should be manually triggered. It's like performing an apt-get update before apt-get install, or brew update before brew install.

@seancheung commented on GitHub (Oct 4, 2025): Updating the local registry cache should be manually triggered. It's like performing an `apt-get update` before `apt-get install`, or `brew update` before `brew install`.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@CCpt5 commented on GitHub (Oct 21, 2025):

Again, need an update please.

@CCpt5 commented on GitHub (Oct 21, 2025): Again, need an update please.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@diodiogod commented on GitHub (Oct 29, 2025):

can't this at least have a cache that checks only once a day or at least once an hour? This is annoying and pollutes console when rebooting comfyui to test other nodes.

@diodiogod commented on GitHub (Oct 29, 2025): can't this at least have a cache that checks only once a day or at least once an hour? This is annoying and pollutes console when rebooting comfyui to test other nodes.

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@brandonkish commented on GitHub (Jan 7, 2026):

For anyone else who is super annoyed by the ridiculous reporting of the fetch every second, constantly moving the console text and making it cluttered and impossible to read, all while you are constantly restarting ComfyUI to debug things... WITH NO WAY TO NATIVELY DISABLE IT... Comment this code out:

...\ComfyUI_portable\ComfyUI\custom_nodes\ComfyUI-Manager\glob\cnr_utils.py: 80-81

@brandonkish commented on GitHub (Jan 7, 2026): For anyone else who is super annoyed by the ridiculous reporting of the fetch every second, constantly moving the console text and making it cluttered and impossible to read, all while you are constantly restarting ComfyUI to debug things... WITH NO WAY TO NATIVELY DISABLE IT... Comment this code out: ...\ComfyUI_portable\ComfyUI\custom_nodes\ComfyUI-Manager\glob\cnr_utils.py: 80-81 <img width="3463" height="1519" alt="Image" src="https://github.com/user-attachments/assets/d7d832e8-219a-4165-a418-be5cb189c2e6" />

bsakaguchi commented

2026-10-27 21:21:08 +00:00

Author

Owner

@zackfuchtel commented on GitHub (Jan 27, 2026):

For anyone else who is super annoyed by the ridiculous reporting of the fetch every second, constantly moving the console text and making it cluttered and impossible to read,

Thank you.

@zackfuchtel commented on GitHub (Jan 27, 2026): > For anyone else who is super annoyed by the ridiculous reporting of the fetch every second, constantly moving the console text and making it cluttered and impossible to read, Thank you.

bsakaguchi referenced this issue

2026-10-27 21:31:48 +00:00

[PR #701] [MERGED] * BAMB custom node - url changed. #1472

Rows
Columns

[GH-ISSUE #1629] Manager: V3.30.3, how to disable auto FETCH ComfyRegistry Data on every startup? #701