[GH-ISSUE #931] don't allow same name node packs #407

New issue

Open

opened 2026-10-27 21:17:13 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-27 21:17:13 +00:00

Owner

Originally created by @klinter007 on GitHub (Aug 5, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/931

hi, this is very confusing that people use the same names for nodes pack.
not to mention that it's sometimes for probably gaming the system and get clout, this breaks workflows when we share to others, as they are getting the wrong nodes when they do "install missing nodes".

so please, don't allow same name node packs.

Originally created by @klinter007 on GitHub (Aug 5, 2024). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/931 hi, this is very confusing that people use the same names for nodes pack. not to mention that it's sometimes for probably gaming the system and get clout, this breaks workflows when we share to others, as they are getting the wrong nodes when they do "install missing nodes". so please, don't allow same name node packs.

bsakaguchi commented

2026-10-27 21:17:13 +00:00

Author

Owner

@sumeetprashant commented on GitHub (Aug 5, 2024):

second that, sometimes the similar/same named node does not get imported and I end up thinking that the one that I use did not import and go on troubleshooting it just to learn that it was some other node with the same name.

@sumeetprashant commented on GitHub (Aug 5, 2024): second that, sometimes the similar/same named node does not get imported and I end up thinking that the one that I use did not import and go on troubleshooting it just to learn that it was some other node with the same name.

bsakaguchi commented

2026-10-27 21:17:13 +00:00

Author

Owner

@ltdrdata commented on GitHub (Aug 5, 2024):

hi, this is very confusing that people use the same names for nodes pack. not to mention that it's sometimes for probably gaming the system and get clout, this breaks workflows when we share to others, as they are getting the wrong nodes when they do "install missing nodes".

so please, don't allow same name node packs.

TBH, It's out of my control.
To achieve that, a new type of custom node that can control those is needed.

@ltdrdata commented on GitHub (Aug 5, 2024): > hi, this is very confusing that people use the same names for nodes pack. not to mention that it's sometimes for probably gaming the system and get clout, this breaks workflows when we share to others, as they are getting the wrong nodes when they do "install missing nodes". > > so please, don't allow same name node packs. TBH, It's out of my control. To achieve that, a new type of custom node that can control those is needed.

bsakaguchi commented

2026-10-27 21:17:14 +00:00

Author

Owner

@klinter007 commented on GitHub (Aug 7, 2024):

thank you for taking the time to answer.

Since i was referring only to the way that nodes are registered with the manager, can't it be be implied when adding the node packs to main?
(not that i know exactly how it would work, you guys are smarter than me :) )

@klinter007 commented on GitHub (Aug 7, 2024): thank you for taking the time to answer. Since i was referring only to the way that nodes are registered with the manager, can't it be be implied when adding the node packs to main? (not that i know exactly how it would work, you guys are smarter than me :) )

bsakaguchi referenced this issue

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

[PR #407] [MERGED] Update ComfyUI-Prediction in databases. #1314