[GH-ISSUE #1762] Node pack id mismatch when installing missing custom nodes #759

New issue

Closed

opened 2026-10-27 21:21:49 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

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

Owner

Originally created by @purzbeats on GitHub (Apr 20, 2025).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1762

Often on the standalone and portable/web versions of Comfy, when you click Install Missing Custom Nodes, some node packs come up as the incorrect id's.

As you can imagine this could cause the wrong node pack to be installed and in certain cases that could be dangerous.

In this case it works in the old manager, but not the new manager.

Old manager (correct)

New manager (wrong node pack)

Originally created by @purzbeats on GitHub (Apr 20, 2025). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/1762 Often on the standalone and portable/web versions of Comfy, when you click Install Missing Custom Nodes, some node packs come up as the incorrect id's. As you can imagine this could cause the wrong node pack to be installed and in certain cases that could be dangerous. In this case it works in the old manager, but not the new manager. Old manager (correct) ![Image](https://github.com/user-attachments/assets/eb5434d2-adee-4bb5-8ca6-0fec8fd48257) New manager (wrong node pack) ![Image](https://github.com/user-attachments/assets/5a9bb2f3-6aa5-4cd2-9342-3a64089dba4b)

bsakaguchi closed this issue

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

bsakaguchi commented

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

Author

Owner

@christian-byrne commented on GitHub (Apr 20, 2025):

Thank you for reporting that.

Workflows made prior to February will not have node pack (cnr_id or aux_id) embedded in them. In that case, we try our best to infer the node pack based on the individual node names.

In the new Manager, we are simply calling api.comfy.org/nodes/search?comfy_node_search={NodeClassName} and using the first result. It seems we also need to port over the ranking algorithm for determing which node pack to use when multiple possible candidates exist.

What's strange is, in the database, that node pack doesn't even have any individual nodes list:

https://api.comfy.org/nodes/ComfyUI_agilly1989_motorway/versions/1.1.4/comfy-nodes

@purzbeats Can you share either the workflow or the individual node in the workflow that was missing?

@christian-byrne commented on GitHub (Apr 20, 2025): Thank you for reporting that. Workflows made prior to February will not have node pack (`cnr_id` or `aux_id`) embedded in them. In that case, we try our best to infer the node pack based on the individual node names. In the new Manager, we are simply calling `api.comfy.org/nodes/search?comfy_node_search={NodeClassName}` and using the first result. It seems we also need to port over the ranking algorithm for determing which node pack to use when multiple possible candidates exist. What's strange is, in the database, that node pack doesn't even have any individual nodes list: https://api.comfy.org/nodes/ComfyUI_agilly1989_motorway/versions/1.1.4/comfy-nodes @purzbeats Can you share either the workflow or the individual node in the workflow that was missing?