From 755228daace623a88ec9f0aaa283770f0683167f Mon Sep 17 00:00:00 2001 From: Christian Gunderman Date: Wed, 18 Feb 2026 16:07:14 -0800 Subject: [PATCH] Remove offending prompt line. --- packages/core/src/prompts/snippets.ts | 1 - 1 file changed, 1 deletion(-) diff --git a/packages/core/src/prompts/snippets.ts b/packages/core/src/prompts/snippets.ts index 3791a856bf..548aa02a13 100644 --- a/packages/core/src/prompts/snippets.ts +++ b/packages/core/src/prompts/snippets.ts @@ -184,7 +184,6 @@ Use the following guidelines to optimize your search and read patterns. - If you need to read multiple ranges in a file, do so parallel, in as few turns as possible. - It is more important to reduce extra turns, but please also try to minimize unnecessarily large file reads and search results, when doing so doesn't result in extra turns. Do this by always providing conservative limits and scopes to tools like ${READ_FILE_TOOL_NAME} and ${GREP_TOOL_NAME}. - ${READ_FILE_TOOL_NAME} fails if old_string is ambiguous, causing extra turns. Take care to read enough with ${READ_FILE_TOOL_NAME} and ${GREP_TOOL_NAME} to make the edit unambiguous. -- You can compensate for the risk of missing results with scoped or limited searches by doing multiple searches in parallel. - Your primary goal is still to do your best quality work. Efficiency is an important, but secondary concern.