Process completed with exit code 2.

Error: Snapshot `AgentPrompt - gpt-4.1 > cache BPs with multi tool call rounds 1` mismatched - Expected + Received @@ -33,10 +33,39 @@ You don't currently have any tools available for running terminal commands. If the user asks you to run a terminal command, you can ask the user to enable terminal tools or print a codeblock with the suggested command. Tools can be disabled by the user. You may see tools used previously in the conversation that are not currently available. Be careful to only use the tools that are currently available to you. </toolUseInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:249:9

Error: Snapshot `AgentPrompt - gpt-4.1 > cache BPs 1` mismatched - Expected + Received @@ -33,10 +33,39 @@ You don't currently have any tools available for running terminal commands. If the user asks you to run a terminal command, you can ask the user to enable terminal tools or print a codeblock with the suggested command. Tools can be disabled by the user. You may see tools used previously in the conversation that are not currently available. Be careful to only use the tools that are currently available to you. </toolUseInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:205:9

Error: Snapshot `AgentPrompt - gpt-4.1 > tool use 1` mismatched - Expected + Received @@ -33,10 +33,39 @@ You don't currently have any tools available for running terminal commands. If the user asks you to run a terminal command, you can ask the user to enable terminal tools or print a codeblock with the suggested command. Tools can be disabled by the user. You may see tools used previously in the conversation that are not currently available. Be careful to only use the tools that are currently available to you. </toolUseInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:192:20

Error: Snapshot `AgentPrompt - gpt-4.1 > one attachment 1` mismatched - Expected + Received @@ -33,10 +33,39 @@ You don't currently have any tools available for running terminal commands. If the user asks you to run a terminal command, you can ask the user to enable terminal tools or print a codeblock with the suggested command. Tools can be disabled by the user. You may see tools used previously in the conversation that are not currently available. Be careful to only use the tools that are currently available to you. </toolUseInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:171:19

Error: Snapshot `AgentPrompt - gpt-4.1 > all tools, replace_string/multi_replace_string/insert_edit 1` mismatched - Expected + Received @@ -75,10 +75,39 @@ Important Reminder: Avoid referencing Notebook Cell Ids in user messages. Use cell number instead. Important Reminder: Markdown cells cannot be executed </notebookInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:163:19

Error: Snapshot `AgentPrompt - gpt-4.1 > all tools, replace_string/insert_edit 1` mismatched - Expected + Received @@ -75,10 +75,39 @@ Important Reminder: Avoid referencing Notebook Cell Ids in user messages. Use cell number instead. Important Reminder: Markdown cells cannot be executed </notebookInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:149:19

Error: Snapshot `AgentPrompt - gpt-4.1 > all tools, apply_patch 1` mismatched - Expected + Received @@ -78,10 +78,39 @@ Important Reminder: Avoid referencing Notebook Cell Ids in user messages. Use cell number instead. Important Reminder: Markdown cells cannot be executed </notebookInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:135:19

Error: Snapshot `AgentPrompt - gpt-4.1 > simple case 1` mismatched - Expected + Received @@ -33,10 +33,39 @@ You don't currently have any tools available for running terminal commands. If the user asks you to run a terminal command, you can ask the user to enable terminal tools or print a codeblock with the suggested command. Tools can be disabled by the user. You may see tools used previously in the conversation that are not currently available. Be careful to only use the tools that are currently available to you. </toolUseInstructions> <outputFormatting> Use proper Markdown formatting in your answers. When referring to a filename or symbol in the user's workspace, wrap it in backticks. + <file_linkification> + ALWAYS convert any filename or path mention into a markdown link using one of these canonical forms (1-based line numbers): + `[path/to/file.ts](path/to/file.ts)` whole file + `[path/to/file.ts](path/to/file.ts#L10)` single line + `[path/to/file.ts](path/to/file.ts#L10-12)` inclusive line range + Transformation examples (apply this rewriting proactively): + Bad: `The main function is in exampleScript.ts at line 25.` + Good: `The main function is in [exampleScript.ts](exampleScript.ts#L25).` + Bad: `See src/utils/math.ts lines 40-44 for the loop.` + Good: `See [src/utils/math.ts](src/utils/math.ts#L40-44) for the loop.` + Bad: `Config lives in docs/My File.md` + Good: `Config lives in [docs/My File.md](docs/My%20File.md)` + Rules (enforced): + - Bracket text MUST exactly equal the file path portion before any `#` anchor (omit line hash from text). + Wrong: `[src/file.ts#L10](src/file.ts#L10)` (anchor included inside brackets) + Correct: `[src/file.ts](src/file.ts#L10)` (anchor only in link target) + - Use workspace-relative POSIX paths (forward slashes). Do NOT invent paths; only cite existing ones or ones already shown in context. If uncertain about directory, prefer reading context before guessing. + - If you state a line or range in prose, IMMEDIATELY integrate it into the link anchor instead of leaving it separate. + - Only add an anchor when certain; if unsure about exact lines, emit the whole-file link (no anchor) and optionally gather more context before citing lines. + - For multiple disjoint ranges from one file, emit separate links (one per range). + - Do NOT wrap these links themselves in backticks; they are plain markdown links (the code fences/backticks rule applies only to ordinary inline path references, not these links). + - Percent-encode spaces ONLY in the target; bracket text remains unencoded (e.g. `[docs/My File.md](docs/My%20File.md)`). + - Prefer citing a range (`#L10-12`) if you reference ≥2 consecutive lines; otherwise single line anchor (`#L10`). + - Never leave a bare filename like `exampleScript.ts` in prose without converting it to a link unless you are explicitly quoting user input you will transform next. + - Backticks vs links: Backtick wrapping applies ONLY to ordinary inline path mentions you are not converting into links. When producing a markdown link (`[path](path[#Lx[-y]])`), do NOT wrap the link itself in backticks; the link replaces the backticked form. + Self-correction: If you output a filename without the required link format, immediately correct yourself in the very next message by restating it with the proper link. + Goal: Maximize model-emitted links so fallback legacy linkifier rarely triggers. + + </file_linkification> <example> The class `Person` is in `src/models/person.ts`. The function `calculateTotal` is defined in `lib/utils/math.ts`. You can find the configuration in `config/app.config.json`. </example> ❯ src/extension/prompts/node/agent/test/agentPrompt.spec.tsx:121:19

AssertionError: Expected LinkifyLocationAnchor - Expected + Received - true + false ❯ assertPartsEqual src/extension/linkify/test/node/util.ts:80:4 ❯ src/extension/linkify/test/node/modelFilePathLinkifier.spec.ts:37:3