[GH-ISSUE #872] [Feature request] Devs can update node names #383

New issue

Open

opened 2026-10-27 21:16:55 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-27 21:16:55 +00:00

Owner

Originally created by @theUpsider on GitHub (Jul 16, 2024).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/872

The Problem

I have an issue with my repository, since the naming of the nodes in comfy must be unique. I updated the naming to include an emoji, since i thought that would be pretty rare. Now all users have to re-add their nodes and https://github.com/theUpsider/ComfyUI-Logic/issues/13 this issue arrises as well. Other packages using my nodes cant use them either.

The feature

I would love to have an option for renaming nodes in the manager as a dev. So that with the next update, the nodes naming is changed without affecting workflows. Maybe use some unique identifier instead of the name or sth.

Originally created by @theUpsider on GitHub (Jul 16, 2024). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/872 ## The Problem I have an issue with my repository, since the naming of the nodes in comfy must be unique. I updated the naming to include an emoji, since i thought that would be pretty rare. Now all users have to re-add their nodes and https://github.com/theUpsider/ComfyUI-Logic/issues/13 this issue arrises as well. Other packages using my nodes cant use them either. ## The feature I would love to have an option for renaming nodes in the manager as a dev. So that with the next update, the nodes naming is changed without affecting workflows. Maybe use some unique identifier instead of the name or sth.

bsakaguchi added the

feature request

label

2026-10-27 21:16:55 +00:00

bsakaguchi commented

2026-10-27 21:16:57 +00:00

Author

Owner

@ltdrdata commented on GitHub (Jul 16, 2024):

I have an idea, but since this is a somewhat risky feature, it might be better to provide it as a separate custom node rather than as part of the Manager.

@ltdrdata commented on GitHub (Jul 16, 2024): I have an idea, but since this is a somewhat risky feature, it might be better to provide it as a separate custom node rather than as part of the Manager.

bsakaguchi commented

2026-10-27 21:16:57 +00:00

Author

Owner

@theUpsider commented on GitHub (Jul 17, 2024):

@ltdrdata do you mean I should add my nodes twice?

Maybe a deprecated feature would be useful! To indicate that newer nodes are available and the current ones will not be supported long term.

@theUpsider commented on GitHub (Jul 17, 2024): @ltdrdata do you mean I should add my nodes twice? Maybe a deprecated feature would be useful! To indicate that newer nodes are available and the current ones will not be supported long term.

bsakaguchi commented

2026-10-27 21:16:57 +00:00

Author

Owner

@christian-byrne commented on GitHub (Jul 17, 2024):

If you want to patch node properteis without breaking workflows you can do it like this: https://gist.github.com/christian-byrne/4a74bedda6e798e00f1dacee7f39afa4

@christian-byrne commented on GitHub (Jul 17, 2024): If you want to patch node properteis without breaking workflows you can do it like this: https://gist.github.com/christian-byrne/4a74bedda6e798e00f1dacee7f39afa4

bsakaguchi commented

2026-10-27 21:16:57 +00:00

Author

Owner

@theUpsider commented on GitHub (Jul 24, 2024):

@christian-byrne Maybe an enduser friendly way of doing this would be awesome.

@theUpsider commented on GitHub (Jul 24, 2024): @christian-byrne Maybe an enduser friendly way of doing this would be awesome.

bsakaguchi referenced this issue

2026-10-27 21:29:58 +00:00

[PR #383] [MERGED] update custom node list #1304