From 3f225cafca08190882a1b2bf0e8d544d07e9c636 Mon Sep 17 00:00:00 2001 From: Michael Drury Date: Thu, 15 Jan 2026 12:35:45 +0000 Subject: [PATCH] fix(ai-builder): Clarify with spec eval judge node type potential mis-matches (no-changelog) (#24345) --- .../evaluations/evaluators/pairwise/judge-chain.ts | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/packages/@n8n/ai-workflow-builder.ee/evaluations/evaluators/pairwise/judge-chain.ts b/packages/@n8n/ai-workflow-builder.ee/evaluations/evaluators/pairwise/judge-chain.ts index 523e200fa7e..fad5bfe88ca 100644 --- a/packages/@n8n/ai-workflow-builder.ee/evaluations/evaluators/pairwise/judge-chain.ts +++ b/packages/@n8n/ai-workflow-builder.ee/evaluations/evaluators/pairwise/judge-chain.ts @@ -58,7 +58,12 @@ const EVALUATOR_SYSTEM_PROMPT = prompt() - Provider-specific nodes (e.g., n8n-nodes-langchain.openAi, n8n-nodes-langchain.anthropic) are standalone nodes that directly call a provider's API. - Chat model sub-nodes (e.g., @n8n/n8n-nodes-langchain.lmChatAnthropic, @n8n/n8n-nodes-langchain.lmChatOpenAi) are NOT provider-specific nodes. They are required infrastructure for connecting generic nodes like the AI Agent to a language model. -If a criterion says "do not use provider-specific nodes" or similar, the presence of lmChat* sub-nodes should NOT count as a violation - these are necessary connectors, not provider-specific workflow nodes.`, +If a criterion says "do not use provider-specific nodes" or similar, the presence of lmChat* sub-nodes should NOT count as a violation - these are necessary connectors, not provider-specific workflow nodes. + +When evaluating whether a specific node type has been used: +- The "@n8n/" prefix in node types is OPTIONAL - ignore it when comparing +- "@n8n/n8n-nodes-langchain.chatTrigger" and "n8n-nodes-langchain.chatTrigger" are the SAME node type +- This applies regardless of which form appears in the criteria or the workflow`, ) .section( 'constraints',