Simplify prompt text and update snap

Author: vijay upadya

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

@@ -99,10 +99,7 @@ class DefaultAnthropicAgentPrompt 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'>
-					See FileLinkificationInstructions for file path link and line anchor rules and examples.
-				</Tag>
+				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 />
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

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

@@ -8,24 +8,27 @@ import { Tag } from '../base/tag';
 
 export class FileLinkificationInstructions extends PromptElement<{}> {
 	render() {
-		return <Tag name='file_linkification'>
-			ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations. Use links inside normal sentences, not as the entire answer.<br />
-			Format examples:<br />
+		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 />
+			<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.`<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 />
-			- `The widget renderer attaches anchors ([src/renderer.ts](src/renderer.ts#L42-L48)).` (in parentheses)<br />
-			When you need a bullet list of references with line numbers, you can use descriptive text:<br />
-			- [Await chat view](path/to/chatQuick.ts#L142)<br />
-			- [Show widget](path/to/chatQuick.ts#L321)<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 />
+			<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 />
+			<br />
 			Critical rules:<br />
-			- Link text must be the exact file path (no backticks, no `#L` in the visible text, no extra wording). Keep the `#L` anchor in the **link target**, e.g. `[src/file.ts](src/file.ts#L25)`.<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://, or https://.<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 />

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

@@ -102,11 +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. Backtick code identifiers (classes, functions, variables, commands). For file paths and code locations, do NOT use backticks — rely on markdown links with line anchors per `FileLinkificationInstructions` below.<br />
-				<Tag name='example'>
-					Identifiers: `Person`, `calculateTotal`, `AppConfig`.<br />
-					File path and line anchor formatting rules and examples are defined in `FileLinkificationInstructions` below.
-				</Tag>
+				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 />
 				<FileLinkificationInstructions />
 				<MathIntegrationRules />
 			</Tag>

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

@@ -103,7 +103,7 @@ export class DefaultOpenAIAgentPrompt extends PromptElement<DefaultAgentPromptPr
 				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 FileLinkificationInstructions.<br />
+					File path link examples live in fileLinkification section below.<br />
 				</Tag>
 				<MathIntegrationRules />
 			</Tag>

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

@@ -71,7 +71,7 @@ class Gpt51CodexPrompt extends PromptElement<DefaultAgentPromptProps> {
 				- Headers: optional; short Title Case (1-3 words) wrapped in **…**; no blank line before the first bullet; add only if they truly help.<br />
 				- Bullets: use - ; merge related points; keep to one line when possible; 4-6 per list ordered by importance; keep phrasing consistent.<br />
 				- Monospace: backticks for commands, env vars, and code identifiers; never combine with **.<br />
-				- File path + line anchor link rules are defined in `FileLinkificationInstructions` below.<br />
+				- File path and line number formatting rules are defined in the fileLinkification section below.<br />
 				- Code samples or multi-line snippets should be wrapped in fenced code blocks; include an info string as often as possible.<br />
 				- Structure: group related bullets; order sections general → specific → supporting; for subsections, start with a bolded keyword bullet, then items; match complexity to the task.<br />
 				- Tone: collaborative, concise, factual; present tense, active voice; self-contained; no "above/below"; parallel wording.<br />

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

@@ -223,7 +223,7 @@ class Gpt51Prompt extends PromptElement<DefaultAgentPromptProps> {
 				- Wrap all commands, env vars, and code identifiers in backticks (`` `...` ``).<br />
 				- Apply to inline examples and to bullet keywords if the keyword itself is a literal file/command.<br />
 				- Never mix monospace and bold markers; choose one based on whether it's a keyword (`**`).<br />
-				- File path and line anchor formatting rules are defined in `FileLinkificationInstructions` below.<br />
+				- File path and line number formatting rules are defined in the fileLinkification section below.<br />
 				<br />
 				**Structure**<br />
 				<br />

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

@@ -76,7 +76,7 @@ class CodexStyleGpt5CodexPrompt extends PromptElement<DefaultAgentPromptProps> {
 			- Tone: collaborative, concise, factual; present tense, active voice; self-contained; no "above/below"; parallel wording.<br />
 			- Don'ts: no nested bullets/hierarchies; no ANSI codes; don't cram unrelated keywords; keep keyword lists short—wrap/reformat if long; avoid naming formatting styles in answers.<br />
 			- 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.<br />
-			- File path and line anchor link rules are defined in `FileLinkificationInstructions` below (do not duplicate examples).<br />
+			- File path and line anchor link rules are defined in fileLinkification section below.<br />
 			<FileLinkificationInstructions />
 		</InstructionMessage>;
 	}

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

@@ -187,7 +187,7 @@ class DefaultGpt5AgentPrompt extends PromptElement<DefaultAgentPromptProps> {
 				- Wrap all commands, env vars, and code identifiers in backticks (`` `...` ``).<br />
 				- Apply to inline examples and to bullet keywords if the keyword itself is a literal file/command.<br />
 				- Never mix monospace and bold markers; choose one based on whether it's a keyword (`**`).<br />
-				- File path and line anchor link rules are defined in `FileLinkificationInstructions` below.<br />
+				- File path and line number formatting rules are defined in the fileLinkification section below.<br />
 				<br />
 				Structure:<br />
 				- Place related bullets together; don't mix unrelated concepts in the same section.<br />

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

@@ -78,30 +78,33 @@ Use proper Markdown formatting. When referring to symbols (classes, methods, var
 <example>
 File path and line anchor formatting rules are defined in `FileLinkificationInstructions` below.
 </example>
-<file_linkification>
-ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations. Use links inside normal sentences, not as the entire answer.
-Format examples:
+<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.`
+- `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)
-- `The widget renderer attaches anchors ([src/renderer.ts](src/renderer.ts#L42-L48)).` (in parentheses)
-When you need a bullet list of references with line numbers, you can use descriptive text:
-- [Await chat view](path/to/chatQuick.ts#L142)
-- [Show widget](path/to/chatQuick.ts#L321)
+
+**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:
-- Link text must be the exact file path (no backticks, no `#L` in the visible text, no extra wording). Keep the `#L` anchor in the **link target**, e.g. `[src/file.ts](src/file.ts#L25)`.
 - 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://, or https://.
+- 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
 
-</file_linkification>
+</fileLinkification>
 
 </outputFormatting>
 

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

@@ -43,35 +43,34 @@ 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. Backtick code identifiers (classes, functions, variables, commands). For file paths and code locations, do NOT use backticks — rely on markdown links with line anchors per `FileLinkificationInstructions` below.
-<example>
-Identifiers: `Person`, `calculateTotal`, `AppConfig`.
-File path and line anchor formatting rules and examples are defined in `FileLinkificationInstructions` below.
-</example>
-<file_linkification>
-ALWAYS convert file paths to markdown links with 1-based line numbers whenever you cite specific code locations. Use links inside normal sentences, not as the entire answer.
-Format examples:
+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
+<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.`
+- `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)
-- `The widget renderer attaches anchors ([src/renderer.ts](src/renderer.ts#L42-L48)).` (in parentheses)
-When you need a bullet list of references with line numbers, you can use descriptive text:
-- [Await chat view](path/to/chatQuick.ts#L142)
-- [Show widget](path/to/chatQuick.ts#L321)
+
+**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:
-- Link text must be the exact file path (no backticks, no `#L` in the visible text, no extra wording). Keep the `#L` anchor in the **link target**, e.g. `[src/file.ts](src/file.ts#L25)`.
 - 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://, or https://.
+- 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
 
-</file_linkification>
+</fileLinkification>
 
 </outputFormatting>