Comfy-Org
Is there any way to stop manager from echoing "Fetch"?
I see no purpose in manager echoing "Fetch" 20 times every time ComfyUI is started. It just adds clutter to an already cluttered console window. Is there an option to stop it from echoing that unneeded info without stopping what it has to do? What good is that wall of "Fetch?"
There is a way to do it, it is in the homepage of this extension, here: https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config
Open the config.ini , then that value (( network mode )) , Make it = offline .
Setting it to offline stops it from getting the updated data. I don't want to do that, especially on new installs. I just want to stop it from cluttering up the log with "Fetch." It seems like they could @.*** off" somewhere in that script. Unless there is an error, no one has to see that "Fetch."
On Wed, Sep 3, 2025 at 3:09 PM Hazem Mahmoud @.***> wrote:
Mr-Hazem-Eng-Artist left a comment (Comfy-Org/ComfyUI-Manager#2117) https://github.com/Comfy-Org/ComfyUI-Manager/issues/2117#issuecomment-3250968311
There is a way to do it, it is in the homepage of this extension, here: https://github.com/ltdrdata/ComfyUI-Manager?tab=readme-ov-file#config
Open the config.ini , then that value (( network mode )) , Make it = offline .
— Reply to this email directly, view it on GitHub https://github.com/Comfy-Org/ComfyUI-Manager/issues/2117#issuecomment-3250968311, or unsubscribe https://github.com/notifications/unsubscribe-auth/BWWG4G5WOQLSUDI5LIBZRH33Q5RIDAVCNFSM6AAAAACFIC3UBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJQHE3DQMZRGE . You are receiving this because you authored the thread.Message ID: @.***>
It is up to the devs to help us in that case,, I have very weak coding skills so I can't make custome changes to achieve what you need. Actually the UI Manager suffers from some stability & compatibility issues lately.
PLEASE, remove this useless Fetch spam from the console! When trying to read the errors, it constantly makes the console scroll to bottom.
separate effort is underway to remove this step. It's not expected to be included in the next major update, but likely in the one after that.
