From e2d57e46fa248d3846628717cba750dfabd66c1c Mon Sep 17 00:00:00 2001 From: Roo Code Date: Mon, 3 Nov 2025 23:44:54 +0000 Subject: [PATCH] docs: update comment to reflect uniform mention parsing behavior --- src/core/mentions/processUserContentMentions.ts | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/src/core/mentions/processUserContentMentions.ts b/src/core/mentions/processUserContentMentions.ts index 148b3c5227..be3aee71f3 100644 --- a/src/core/mentions/processUserContentMentions.ts +++ b/src/core/mentions/processUserContentMentions.ts @@ -29,14 +29,10 @@ export async function processUserContentMentions({ }) { // Process userContent array, which contains various block types: // TextBlockParam, ImageBlockParam, ToolUseBlockParam, and ToolResultBlockParam. - // We need to apply parseMentions() to: - // 1. All TextBlockParam's text (first user message with task) - // 2. ToolResultBlockParam's content/context text arrays if it contains - // "" (see formatToolDeniedFeedback, attemptCompletion, - // executeCommand, and consecutiveMistakeCount >= 3) or "" - // (see askFollowupQuestion), we place all user generated content in - // these tags so they can effectively be used as markers for when we - // should parse mentions). + // We apply parseMentions() to all text content: + // 1. All TextBlockParam's text + // 2. ToolResultBlockParam's string content + // 3. ToolResultBlockParam's array content where blocks are text type return Promise.all( userContent.map(async (block) => { const shouldProcessMentions = (_text: string) => true