Version: 1.108.0-insider (Universal)
Commit: 9ba40f8
Date: 2025-12-12T14:19:49.836Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

Name: GitHub Copilot Chat
Id: GitHub.copilot-chat
Description: AI chat features powered by Copilot
Version: 0.36.2025121203
Publisher: GitHub
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat

This is a waste of the thinking budget.

GPT-5 mini complains in the thinking output:

I’m stuck navigating conflicting instructions about using backticks for filenames. On one hand, I'm told to wrap filenames in backticks in the user's workspace, but then there's a strict rule against backticks in file paths. To be cautious, I’ll avoid backticks altogether when referencing the file.

They are right:

- 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)

<importantReminders>
...
When referring to a filename or symbol in the user's workspace, wrap it in backticks.

</importantReminders>