Prompt updates to make them consistent across models

Author: vijay upadya

src/extension/prompts/node/agent/anthropicPrompts.tsx

@@ -191,10 +191,9 @@ class Claude45DefaultPrompt extends PromptElement<DefaultAgentPromptProps> {
 			{this.props.availableTools && <McpToolInstructions tools={this.props.availableTools} />}
 			<NotebookInstructions {...this.props} />
 			<Tag name='outputFormatting'>
-				Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and code locations, follow `FileLinkificationInstructions` (markdown links with line anchors; never backticks).<br />
-				<Tag name='example'>
-					File path and line anchor formatting rules are defined in `FileLinkificationInstructions` below.
-				</Tag>
+				Use proper Markdown formatting:
+				- Wrap symbol names (classes, methods, variables) in backticks: `MyClass`, `handleClick()`<br />
+				- When mentioning files or line numbers, always follow the rules in fileLinkification section below:
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

src/extension/prompts/node/agent/fileLinkificationInstructions.tsx

@@ -9,30 +9,42 @@ import { Tag } from '../base/tag';
 export class FileLinkificationInstructions extends PromptElement<{}> {
 	render() {
 		return <Tag name='fileLinkification'>
-			ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.<br />
+			When mentioning files or line numbers, always convert them to markdown links using workspace-relative paths and 1-based line numbers.<br />
+			NO BACKTICKS ANYWHERE:<br />
+			- Never wrap file names, paths, or links in backticks.<br />
+			- Never use inline-code formatting for any file reference.<br />
 			<br />
-			**Inline references:** Use the file path as link text within sentences:<br />
-			- `The handler lives in [path/to/file.ts](path/to/file.ts#L10).` (single line)<br />
-			- `See [path/to/file.ts](path/to/file.ts#L10-L12) for the range.` (line range)<br />
-			- `Configuration is defined in [path/to/file.ts](path/to/file.ts).` (whole file)<br />
+
+			REQUIRED FORMATS:<br />
+			- File: [path/file.ts](path/file.ts)<br />
+			- Line: [file.ts](file.ts#L10)<br />
+			- Range: [file.ts](file.ts#L10-L12)<br />
 			<br />
-			**Bullet lists:** Explains what each reference is, so readers understand the context without clicking:<br />
-			- [Await chat view](path/to/file.ts#L142)<br />
-			- [Show widget](path/to/file.ts#L321)<br />
-			Don't just list bare file paths like `file.ts#L142`<br />
+
+			PATH RULES:<br />
+			- Without line numbers: Display text must match the target path.<br />
+			- With line numbers: Display text can be either the path or descriptive text.<br />
+			- Use '/' only; strip drive letters and external folders.<br />
+			- Do not use these URI schemes: file://, vscode://<br />
+			- Encode spaces only in the target (My File.md → My%20File.md).<br />
+			- Non-contiguous lines require separate links. NEVER use comma-separated line references like #L10-L12, L20.<br />
+			- Valid formats: [file.ts](file.ts#L10) or [file.ts#L10] only. Invalid: ([file.ts#L10]) or [file.ts](file.ts)#L10<br />
 			<br />
-			NEVER cite file paths as plain text when referring to specific locations. For example, instead of saying `The function is in exampleScript.ts at line 25.`, say `The function is in [exampleScript.ts](exampleScript.ts#L25).`<br />
+
+			USAGE EXAMPLES:<br />
+			- With path as display: The handler is in [src/handler.ts](src/handler.ts#L10).<br />
+			- With descriptive text: The [widget initialization](src/widget.ts#L321) runs on startup.<br />
+			- Bullet list: [Init widget](src/widget.ts#L321)<br />
+			- File only: See [src/config.ts](src/config.ts) for settings.<br />
+			<br />
+
+			FORBIDDEN (NEVER OUTPUT):<br />
+			- Inline code: `file.ts`, `src/file.ts`, `L86`.<br />
+			- Plain text file names: file.ts, chatService.ts.<br />
+			- References without links when mentioning specific file locations.<br />
+			- Specific line citations without links ("Line 86", "at line 86", "on line 25").<br />
+			- Combining multiple line references in one link: [file.ts#L10-L12, L20](file.ts#L10-L12, L20)<br />
 			<br />
-			Critical rules:<br />
-			- Always include both brackets **and** parentheses. `[src/file.ts](src/file.ts#L25)` is valid; `[src/file.ts#L25]` is not.<br />
-			- Path format: Strip drive letters and workspace parent folders - use only path after workspace root<br />
-			- Transform `c:\Repos\workspace\src\file.ts` → `[src/file.ts](src/file.ts)`<br />
-			- Always use forward slashes `/`, never backslashes `\`<br />
-			- Do not use URIs like file://, vscode:// for file paths.<br />
-			- Percent-encode spaces in target only: `[My File.md](My%20File.md)`<br />
-			- Each file reference needs complete path (don't abbreviate repeated files)<br />
-			- Integrate line numbers into anchor: `#L10` or `#L10-L12` for ranges<br />
-			- Don't wrap links in backticks; only cite existing paths from context<br />
 		</Tag>;
 	}
 }

src/extension/prompts/node/agent/geminiPrompts.tsx

@@ -102,7 +102,7 @@ export class DefaultGeminiAgentPrompt extends PromptElement<DefaultAgentPromptPr
 			{this.props.availableTools && <McpToolInstructions tools={this.props.availableTools} />}
 			<NotebookInstructions {...this.props} />
 			<Tag name='outputFormatting'>
-				Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and line number rules, see fileLinkification section<br />
+				Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and line number rules, see fileLinkification section below<br />
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

src/extension/prompts/node/agent/openai/defaultOpenAIPrompt.tsx

@@ -100,11 +100,8 @@ export class DefaultOpenAIAgentPrompt extends PromptElement<DefaultAgentPromptPr
 			{this.props.availableTools && <McpToolInstructions tools={this.props.availableTools} />}
 			<NotebookInstructions {...this.props} />
 			<Tag name='outputFormatting'>
-				Use proper Markdown formatting. Backtick code identifiers (classes, functions, variables, commands). For file paths or specific code locations, do NOT use backticks—convert them to markdown links with line anchors; file path and line anchor link rules are defined in `FileLinkificationInstructions` below. Avoid duplicating those examples here.<br />
-				<Tag name='example'>
-					Identifiers only: `calculateTotal`, `Person`, `AppConfig`.<br />
-					File path link examples live in fileLinkification section below.<br />
-				</Tag>
+				- Wrap symbol names (classes, methods, variables) in backticks: `MyClass`, `handleClick()`<br />
+				- When mentioning files or line numbers, always follow the rules in fileLinkification section below:
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

src/extension/prompts/node/agent/openai/gpt51CodexPrompt.tsx

@@ -79,10 +79,9 @@ class Gpt51CodexPrompt extends PromptElement<DefaultAgentPromptProps> {
 				- Adaptation: code explanations → precise, structured with code refs; simple tasks → lead with outcome; big changes → logical walkthrough + rationale + next actions; casual one-offs → plain sentences, no headers/bullets.
 			</Tag>
 			<Tag name='special_formatting'>
-				When referring to a filename or symbol in the user's workspace, wrap it in backticks.<br />
-				<Tag name='example'>
-					The class `Person` is in `src/models/person.ts`.
-				</Tag>
+				Use proper Markdown formatting:
+				- Wrap symbol names (classes, methods, variables) in backticks: `MyClass`, `handleClick()`<br />
+				- When mentioning files or line numbers, always follow the rules in fileLinkification section below:
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

src/extension/prompts/node/agent/openai/gpt51Prompt.tsx

@@ -260,9 +260,9 @@ class Gpt51Prompt extends PromptElement<DefaultAgentPromptProps> {
 				Generally, ensure your final answers adapt their shape and depth to the request. For example, answers to code explanations should have a precise, structured explanation with code references that answer the question directly. For tasks with a simple implementation, lead with the outcome and supplement only with what's needed for clarity. Larger changes can be presented as a logical walkthrough of your approach, grouping related steps, explaining rationale where it adds value, and highlighting next actions to accelerate the user. Your answers should provide the right level of detail while being easily scannable.<br />
 				<br />
 				For casual greetings, acknowledgements, or other one-off conversational messages that are not delivering substantive information or structured results, respond naturally without section headers or bullet formatting.
+				<FileLinkificationInstructions />
 			</Tag>
 			<ResponseTranslationRules />
-			<FileLinkificationInstructions />
 		</InstructionMessage >;
 	}
 }

src/extension/prompts/node/agent/openai/gpt5Prompt.tsx

@@ -215,10 +215,8 @@ class DefaultGpt5AgentPrompt extends PromptElement<DefaultAgentPromptProps> {
 				<br />
 				For casual greetings, acknowledgements, or other one-off conversational messages that are not delivering substantive information or structured results, respond naturally without section headers or bullet formatting.<br />
 				<br />
-				When referring to a filename or symbol in the user's workspace, wrap it in backticks.<br />
-				<Tag name='example'>
-					The class `Person` is in `src/models/person.ts`.
-				</Tag>
+				- Wrap symbol names (classes, methods, variables) in backticks: `MyClass`, `handleClick()`<br />
+				- When mentioning files or line numbers, always follow the rules in fileLinkification section below:
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-claude-sonnet-4.5.spec.snap

@@ -74,35 +74,40 @@ Important Reminder: Avoid referencing Notebook Cell Ids in user messages. Use ce
 Important Reminder: Markdown cells cannot be executed
 </notebookInstructions>
 <outputFormatting>
-Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and code locations, follow `FileLinkificationInstructions` (markdown links with line anchors; never backticks).
-<example>
-File path and line anchor formatting rules are defined in `FileLinkificationInstructions` below.
-</example>
-<fileLinkification>
-ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
-
-**Inline references:** Use the file path as link text within sentences:
-- `The handler lives in [path/to/file.ts](path/to/file.ts#L10).` (single line)
-- `See [path/to/file.ts](path/to/file.ts#L10-L12) for the range.` (line range)
-- `Configuration is defined in [path/to/file.ts](path/to/file.ts).` (whole file)
-
-**Bullet lists:** Explains what each reference is, so readers understand the context without clicking:
-- [Await chat view](path/to/file.ts#L142)
-- [Show widget](path/to/file.ts#L321)
-Don't just list bare file paths like `file.ts#L142`
-
-NEVER cite file paths as plain text when referring to specific locations. For example, instead of saying `The function is in exampleScript.ts at line 25.`, say `The function is in [exampleScript.ts](exampleScript.ts#L25).`
-
-Critical rules:
-- Always include both brackets **and** parentheses. `[src/file.ts](src/file.ts#L25)` is valid; `[src/file.ts#L25]` is not.
-- Path format: Strip drive letters and workspace parent folders - use only path after workspace root
-- Transform `c:/Repos/workspace/src/file.ts` → `[src/file.ts](src/file.ts)`
-- Always use forward slashes `/`, never backslashes `/`
-- Do not use URIs like file://, vscode:// for file paths.
-- Percent-encode spaces in target only: `[My File.md](My%20File.md)`
-- Each file reference needs complete path (don't abbreviate repeated files)
-- Integrate line numbers into anchor: `#L10` or `#L10-L12` for ranges
-- Don't wrap links in backticks; only cite existing paths from context
+Use proper Markdown formatting: - Wrap symbol names (classes, methods, variables) in backticks: `MyClass`, `handleClick()`
+- When mentioning files or line numbers, always follow the rules in fileLinkification section below:<fileLinkification>
+When mentioning files or line numbers, always convert them to markdown links using workspace-relative paths and 1-based line numbers.
+NO BACKTICKS ANYWHERE:
+- Never wrap file names, paths, or links in backticks.
+- Never use inline-code formatting for any file reference.
+
+REQUIRED FORMATS:
+- File: [path/file.ts](path/file.ts)
+- Line: [file.ts](file.ts#L10)
+- Range: [file.ts](file.ts#L10-L12)
+
+PATH RULES:
+- Without line numbers: Display text must match the target path.
+- With line numbers: Display text can be either the path or descriptive text.
+- Use '/' only; strip drive letters and external folders.
+- Do not use these URI schemes: file://, vscode://
+- Encode spaces only in the target (My File.md → My%20File.md).
+- Non-contiguous lines require separate links. NEVER use comma-separated line references like #L10-L12, L20.
+- Valid formats: [file.ts](file.ts#L10) or [file.ts#L10] only. Invalid: ([file.ts#L10]) or [file.ts](file.ts)#L10
+
+USAGE EXAMPLES:
+- With path as display: The handler is in [src/handler.ts](src/handler.ts#L10).
+- With descriptive text: The [widget initialization](src/widget.ts#L321) runs on startup.
+- Bullet list: [Init widget](src/widget.ts#L321)
+- File only: See [src/config.ts](src/config.ts) for settings.
+
+FORBIDDEN (NEVER OUTPUT):
+- Inline code: `file.ts`, `src/file.ts`, `L86`.
+- Plain text file names: file.ts, chatService.ts.
+- References without links when mentioning specific file locations.
+- Specific line citations without links ("Line 86", "at line 86", "on line 25").
+- Combining multiple line references in one link: [file.ts#L10-L12, L20](file.ts#L10-L12, L20)
+
 
 </fileLinkification>
 

src/extension/prompts/node/agent/test/__snapshots__/agentPrompts-all_non_edit_tools-gemini-2.0-flash.spec.snap

@@ -43,32 +43,40 @@ Important Reminder: Avoid referencing Notebook Cell Ids in user messages. Use ce
 Important Reminder: Markdown cells cannot be executed
 </notebookInstructions>
 <outputFormatting>
-Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and line number rules, see fileLinkification section
+Use proper Markdown formatting. When referring to symbols (classes, methods, variables) in user's workspace wrap in backticks. For file paths and line number rules, see fileLinkification section below
 <fileLinkification>
-ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations in the workspace. Paths should be relative to workspace root.
-
-**Inline references:** Use the file path as link text within sentences:
-- `The handler lives in [path/to/file.ts](path/to/file.ts#L10).` (single line)
-- `See [path/to/file.ts](path/to/file.ts#L10-L12) for the range.` (line range)
-- `Configuration is defined in [path/to/file.ts](path/to/file.ts).` (whole file)
-
-**Bullet lists:** Explains what each reference is, so readers understand the context without clicking:
-- [Await chat view](path/to/file.ts#L142)
-- [Show widget](path/to/file.ts#L321)
-Don't just list bare file paths like `file.ts#L142`
-
-NEVER cite file paths as plain text when referring to specific locations. For example, instead of saying `The function is in exampleScript.ts at line 25.`, say `The function is in [exampleScript.ts](exampleScript.ts#L25).`
-
-Critical rules:
-- Always include both brackets **and** parentheses. `[src/file.ts](src/file.ts#L25)` is valid; `[src/file.ts#L25]` is not.
-- Path format: Strip drive letters and workspace parent folders - use only path after workspace root
-- Transform `c:/Repos/workspace/src/file.ts` → `[src/file.ts](src/file.ts)`
-- Always use forward slashes `/`, never backslashes `/`
-- Do not use URIs like file://, vscode:// for file paths.
-- Percent-encode spaces in target only: `[My File.md](My%20File.md)`
-- Each file reference needs complete path (don't abbreviate repeated files)
-- Integrate line numbers into anchor: `#L10` or `#L10-L12` for ranges
-- Don't wrap links in backticks; only cite existing paths from context
+When mentioning files or line numbers, always convert them to markdown links using workspace-relative paths and 1-based line numbers.
+NO BACKTICKS ANYWHERE:
+- Never wrap file names, paths, or links in backticks.
+- Never use inline-code formatting for any file reference.
+
+REQUIRED FORMATS:
+- File: [path/file.ts](path/file.ts)
+- Line: [file.ts](file.ts#L10)
+- Range: [file.ts](file.ts#L10-L12)
+
+PATH RULES:
+- Without line numbers: Display text must match the target path.
+- With line numbers: Display text can be either the path or descriptive text.
+- Use '/' only; strip drive letters and external folders.
+- Do not use these URI schemes: file://, vscode://
+- Encode spaces only in the target (My File.md → My%20File.md).
+- Non-contiguous lines require separate links. NEVER use comma-separated line references like #L10-L12, L20.
+- Valid formats: [file.ts](file.ts#L10) or [file.ts#L10] only. Invalid: ([file.ts#L10]) or [file.ts](file.ts)#L10
+
+USAGE EXAMPLES:
+- With path as display: The handler is in [src/handler.ts](src/handler.ts#L10).
+- With descriptive text: The [widget initialization](src/widget.ts#L321) runs on startup.
+- Bullet list: [Init widget](src/widget.ts#L321)
+- File only: See [src/config.ts](src/config.ts) for settings.
+
+FORBIDDEN (NEVER OUTPUT):
+- Inline code: `file.ts`, `src/file.ts`, `L86`.
+- Plain text file names: file.ts, chatService.ts.
+- References without links when mentioning specific file locations.
+- Specific line citations without links ("Line 86", "at line 86", "on line 25").
+- Combining multiple line references in one link: [file.ts#L10-L12, L20](file.ts#L10-L12, L20)
+
 
 </fileLinkification>