Incorrect priority of API nodes in search Title: Incorrect priority of API nodes in search Description: ### Prerequisites - [x] I am running the latest version of ComfyUI
Test focus: Verify that searching for 'Get' does not return unrelated API nodes as the first results. Prerequisites: ComfyUI loaded with default workflow Steps: Wait for the UI to fully load → Click 'Nodes' to open the Node Library sidebar → Wait for the Node Library sidebar to open → Capture the Nodes sidebar → Double click on an empty area of the canvas to open the node search dialog → Wait for the search dialog to appear → ...
# linux QA Video Report
- Generated at: 2026-04-12T13:30:28.989Z
- Model: `gemini-3-flash-preview`
- Target: https://github.com/Comfy-Org/ComfyUI_frontend/issues/10394
- Source video: `./qa-artifacts/qa-report-Linux-24307531956/qa-session.mp4`
- Video size: 325.3 KB
## AI Review
## Summary
The bug report states that the new node search incorrectly prioritizes certain nodes (referred to as "API nodes") even when they do not contain the search term in their display name. The video confirms this behavior: when searching for "Get", nodes like "Convert Image to Mask", "Wan Image to Video", and "Wan Image to Image" appear in the "Most relevant" results, despite lacking the word "Get" in their labels. The narration explains this is due to the search engine matching internal camelCase names rather than just display names.
## Confirmed Issues
### Incorrect search result prioritization and relevance
`HIGH` `00:04` `Confidence: High`
Searching for a specific keyword ("Get") returns results that do not contain the keyword in their display name within the "Most relevant" section. This results in poor search quality and cluttering of the top results with irrelevant nodes. Based on the narration and issue context, this is happening because the search logic is matching internal API/code names (e.g., camelCase strings) that might contain the substring, rather than prioritizing the user-facing display names.
**Evidence:** In the video at 0:04, after the user types "Get", the search results list includes "Convert Image to Mask" (3rd item), "Wan Image to Video" (4th item), and "Wan Image to Image" (5th item). None of these display names contain the word "Get".
**Suggested Fix:** Adjust the search ranking algorithm to heavily prioritize exact or prefix matches in the display name over internal property names. Consider excluding internal camelCase name matches from the "Most relevant" category if they don't match the display name.
## Overall Risk
The risk is **medium** because while the software remains functional, the primary method for adding nodes is significantly degraded, leading to user frustration and difficulty in finding relevant tools within the workflow editor.
## Narration
The video contains a TTS narration:
"The search dialog appears. We type 'Get' to find nodes related to getting values. Look at positions 2, 4 and 5 in the results: 'Convert Image to Mask', 'Wan Image to Image', and 'Wan Image to Video' - none of these contain the word 'Get' in their display names. They are incorrectly ranked above more relevant results because the node search matches their internal camelcase names."
*Note: The narrator says "positions 2, 4 and 5", but "Convert Image to Mask" is visually at position 3 in the list.*
## Verdict
{"verdict": "REPRODUCED", "risk": "medium", "confidence": "high", "narrationDetected": true}