Weekly GitHub Report for Vscode: July 14, 2025 - July 21, 2025 (12:12:19)

            Weekly GitHub Report for Vscode: July 14, 2025 - July 21, 2025 (12:12:19)

            Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

I. News
1.1. Recent Version Releases
1.2. Other Noteworthy Updates

II. Issues
2.1. Top 5 Active Issues
2.2. Top 5 Stale Issues
2.3. Open Issues
2.4. Closed Issues
2.5. Issue Discussion Insights

III. Pull Requests
3.1. Open Pull Requests
3.2. Closed Pull Requests
3.3. Pull Request Discussion Insights

IV. Contributors
4.1. Contributors

I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
Released on March 12, 2025, this version of Visual Studio Code focuses on resolving issues identified in the February 2025 Recovery 2 milestone, with detailed release notes available on the official website.

II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted. 

VSCode failing to keep the remote connection open: This issue involves Visual Studio Code (VSCode) failing to maintain a stable remote connection when using the Remote-SSH feature, particularly after a recent Windows upgrade. The problem persists despite attempts to resolve it by reinstalling VSCode, rebooting the virtual machine, and allocating more memory, and it appears to be related to the latest VSCode update affecting various extensions.

Multiple users report experiencing the same issue across different operating systems and configurations, with many confirming that disabling and re-enabling extensions temporarily resolves the problem. The Vue (Official) extension is frequently mentioned as a potential cause, and a workaround involving downgrading and re-upgrading extensions is suggested. The issue is reopened for further investigation, with discussions pointing to a possible connection with recent VSCode updates and extension compatibility.
Number of comments this week: 30

copilot-instructions.md not attached to prompts.: This issue highlights a problem where the copilot-instructions.md file is not being attached to prompts in the Copilot Chat Extension, despite the user ensuring that the "Use Instruction Files" setting is enabled. The user is experiencing this issue on a specific setup involving Copilot Chat Extension version 0.29.0, VS Code version 1.102.0, and Windows 10, and has provided steps to reproduce the problem, including the creation of a .github\copilot-instructions.md file with specific content.

The comments discuss troubleshooting steps, such as checking if the chat.promptFiles setting is enabled and examining logs for the [InstructionsContextComputer] entry. Users report that the issue persists even after reverting to previous versions, and some mention organizational policies disabling experimental features, which affects the functionality. There is a request for a hotfix to address the regression, as it impacts productivity, and a suggestion to remove the 'experimental' tag from chat.promptFiles or make useInstructionFiles work independently.
Number of comments this week: 16

Behaviour when entering Japanese in the terminal.: This issue is about a bug in Visual Studio Code's terminal where entering Japanese text does not work correctly, even when all extensions are disabled, and the problem persists in both the regular VS Code terminal and during Claude Code sessions. The user reports that the issue does not occur in iTerm2, suggesting it is specific to the IDE's terminal, and provides logs and a movie to demonstrate the problem.

The comments discuss confirming the issue in a regular VS Code terminal, gathering detailed logs, and identifying that a right prompt in the shell might be causing ghost text issues. A workaround of removing the right prompt resolves part of the issue, but the user still faces problems typing Japanese text in the middle of a sentence, even after switching to bash without a right prompt.
Number of comments this week: 9

Agent not waiting for VS Code tasks to complete: This issue involves a problem with the GitHub Copilot Chat extension in Visual Studio Code, where the agent does not wait for tasks to complete before responding, contrary to the expected behavior of blocking until task completion. The user reports that the task is triggered but the agent immediately responds without waiting, even when using different shells or task types, and suggests that the issue might be related to the task not blocking as intended.

The comments discuss updating to the latest version and setting the log level to debug for better diagnostics. It is noted that the current design only waits a short time to avoid hanging, but the user clarifies that the agent does not wait at all. Debug logs show the task runs in the background without blocking. Suggestions include increasing wait time or making it configurable, especially for long-running tasks like builds.
Number of comments this week: 9

Feature Request: Mechanism for extensions to augment the variables available for snippets with contextually-relevant information: This issue is a feature request for the Visual Studio Code Snippets system to allow extensions, such as the C# extension, to provide additional contextually-relevant variables that can be used in code snippets. The current limitation is that snippets rely on a centralized system with limited variables, which can lead to incorrect code generation, such as mismatched constructor names, when the filename does not match the class name or when dealing with nested classes.

The comments discuss whether the constructor snippet requires an extension, with initial confusion resolved by confirming it is part of the C# extension. The conversation shifts to the need for a feature allowing extensions to add contextual variables to snippets, with some suggesting that Language Server Protocol (LSP) completions could achieve similar functionality, though they are more complex to set up. Examples of LSP completions are requested and provided, highlighting their capabilities beyond basic snippets.
Number of comments this week: 8

2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible. 

Notebook>Outline: Show Code Cell Markdown: This issue is a feature request for Visual Studio Code to support the generation and display of markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request highlights the need for an option to render markdown generated by code cells in the output, allowing for dynamic titles and content to be displayed alongside markdown cells, enhancing the functionality and interactivity of notebooks within VS Code.
Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue describes a bug in Visual Studio Code where using a vscode:// link with parameters ?new-window or ?reuse-window does not function as expected, as it hijacks the existing window instead of opening a new one. The problem occurs when a user is connected to a remote server, and clicking such a link disconnects the current session and replaces it with a new one, rather than creating a separate window for the new connection.
${userHome} in a task command creates bad paths: This issue describes a problem in Visual Studio Code where using the ${userHome} variable in a task command of type "process" results in incorrect path formatting, leading to errors when attempting to execute the command. The issue does not occur when the task type is set to "shell" with PowerShell as the default shell, and a workaround is to use ${env:USERPROFILE} instead, which correctly formats the path for execution.
Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue involves a problem with the Visual Studio Code terminal when it is moved to a floating window during a remote connection, such as with WSL or SSH, where characters typed are not displayed in real time if the main window is minimized. The expected behavior is for the terminal to echo characters immediately, but currently, they only appear once the main window is restored, suggesting a potential "sleep" state in the remote connection when the main window is minimized.
Unicode character displayed as a question mark ?: This issue pertains to a bug in Visual Studio Code where a Unicode character, specifically the full-width quotation mark (U+FF02), is incorrectly displayed as a question mark when copied into the editor. The problem persists even when all extensions are disabled, and the character is displayed correctly in other applications like Firefox, indicating a rendering issue within VS Code itself.

2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository. 
Issues Opened This Week: 568
Summarized Issues:

AI Usage Metrics in Visual Studio Code: This topic covers the proposal to implement a feature in Visual Studio Code that visually displays metrics on AI usage. The feature aims to show the number of characters or lines added by AI, the extent of AI's contribution to the user's code, and potentially the time saved by AI, with suggestions for integrating these insights into the status bar or Copilot menu for easy access.
microsoft/vscode/issues/255655

Bugs in Visual Studio Code Extensions: Several issues report bugs in Visual Studio Code extensions, such as the failure of custom groq key requests, incorrect keybinding conditions, and AI component crashes. These bugs affect the functionality of the extensions, causing them to fail or behave unexpectedly, and they occur across different versions and operating systems.
microsoft/vscode/issues/255665, microsoft/vscode/issues/255666, microsoft/vscode/issues/255668, microsoft/vscode/issues/255671, microsoft/vscode/issues/255675, microsoft/vscode/issues/255676, microsoft/vscode/issues/255677, microsoft/vscode/issues/255678, microsoft/vscode/issues/255679, microsoft/vscode/issues/255680, microsoft/vscode/issues/255682, microsoft/vscode/issues/255683, microsoft/vscode/issues/255684, microsoft/vscode/issues/255685, microsoft/vscode/issues/255686, microsoft/vscode/issues/255687, microsoft/vscode/issues/255689, microsoft/vscode/issues/255690, microsoft/vscode/issues/255696, microsoft/vscode/issues/255697, microsoft/vscode/issues/255698, microsoft/vscode/issues/255699, microsoft/vscode/issues/255700, microsoft/vscode/issues/255701, microsoft/vscode/issues/255702, microsoft/vscode/issues/255704, microsoft/vscode/issues/255705, microsoft/vscode/issues/255706, microsoft/vscode/issues/255707, microsoft/vscode/issues/255708, microsoft/vscode/issues/255709, microsoft/vscode/issues/255715, microsoft/vscode/issues/255717, microsoft/vscode/issues/255718, microsoft/vscode/issues/255719, microsoft/vscode/issues/255722, microsoft/vscode/issues/255724, microsoft/vscode/issues/255725, microsoft/vscode/issues/255726, microsoft/vscode/issues/255727, microsoft/vscode/issues/255728, microsoft/vscode/issues/255729, microsoft/vscode/issues/255732, microsoft/vscode/issues/255737, microsoft/vscode/issues/255738, microsoft/vscode/issues/255741, microsoft/vscode/issues/255742, microsoft/vscode/issues/255744, microsoft/vscode/issues/255745, microsoft/vscode/issues/255749, microsoft/vscode/issues/255757, microsoft/vscode/issues/255765, microsoft/vscode/issues/255768, microsoft/vscode/issues/255771, microsoft/vscode/issues/255772, microsoft/vscode/issues/255774, microsoft/vscode/issues/255776, microsoft/vscode/issues/255777, microsoft/vscode/issues/255779, microsoft/vscode/issues/255780, microsoft/vscode/issues/255783, microsoft/vscode/issues/255784, microsoft/vscode/issues/255785, microsoft/vscode/issues/255786, microsoft/vscode/issues/255789, microsoft/vscode/issues/255792, microsoft/vscode/issues/255795, microsoft/vscode/issues/255796, microsoft/vscode/issues/255797, microsoft/vscode/issues/255798, microsoft/vscode/issues/255801, microsoft/vscode/issues/255802, microsoft/vscode/issues/255803, microsoft/vscode/issues/255807, microsoft/vscode/issues/255808, microsoft/vscode/issues/255809, microsoft/vscode/issues/255812, microsoft/vscode/issues/255816, microsoft/vscode/issues/255817, microsoft/vscode/issues/255818, microsoft/vscode/issues/255819, microsoft/vscode/issues/255820, microsoft/vscode/issues/255833, microsoft/vscode/issues/255834, microsoft/vscode/issues/255838, microsoft/vscode/issues/255842, microsoft/vscode/issues/255843, microsoft/vscode/issues/255849, microsoft/vscode/issues/255850, microsoft/vscode/issues/255851, microsoft/vscode/issues/255852, microsoft/vscode/issues/255855, microsoft/vscode/issues/255860, microsoft/vscode/issues/255861, microsoft/vscode/issues/255862, microsoft/vscode/issues/255864, microsoft/vscode/issues/255865, microsoft/vscode/issues/255868, microsoft/vscode/issues/255870, microsoft/vscode/issues/255872, microsoft/vscode/issues/255873, microsoft/vscode/issues/255875, microsoft/vscode/issues/255876, microsoft/vscode/issues/255878, microsoft/vscode/issues/255879, microsoft/vscode/issues/255882, microsoft/vscode/issues/255883, microsoft/vscode/issues/255884, microsoft/vscode/issues/255885, microsoft/vscode/issues/255887, microsoft/vscode/issues/255889, microsoft/vscode/issues/255890, microsoft/vscode/issues/255893, microsoft/vscode/issues/255894, microsoft/vscode/issues/255895, microsoft/vscode/issues/255897, microsoft/vscode/issues/255906, microsoft/vscode/issues/255907, microsoft/vscode/issues/255911, microsoft/vscode/issues/255913, microsoft/vscode/issues/255917, microsoft/vscode/issues/255918, microsoft/vscode/issues/255922, microsoft/vscode/issues/255925, microsoft/vscode/issues/255927, microsoft/vscode/issues/255928, microsoft/vscode/issues/255929, microsoft/vscode/issues/255932, microsoft/vscode/issues/255937, microsoft/vscode/issues/255938, microsoft/vscode/issues/255939, microsoft/vscode/issues/255940, microsoft/vscode/issues/255941, microsoft/vscode/issues/255944, microsoft/vscode/issues/255946, microsoft/vscode/issues/255948, microsoft/vscode/issues/255949, microsoft/vscode/issues/255958, microsoft/vscode/issues/255960, microsoft/vscode/issues/255962, microsoft/vscode/issues/255966, microsoft/vscode/issues/255971, microsoft/vscode/issues/255975, microsoft/vscode/issues/255976, microsoft/vscode/issues/255981, microsoft/vscode/issues/255983, microsoft/vscode/issues/255986, microsoft/vscode/issues/255990, microsoft/vscode/issues/255992, microsoft/vscode/issues/255993, microsoft/vscode/issues/255994, microsoft/vscode/issues/255995, microsoft/vscode/issues/255998, microsoft/vscode/issues/256000, microsoft/vscode/issues/256002, microsoft/vscode/issues/256005, microsoft/vscode/issues/256007, microsoft/vscode/issues/256010, microsoft/vscode/issues/256013, microsoft/vscode/issues/256014, microsoft/vscode/issues/256019, microsoft/vscode/issues/256021, microsoft/vscode/issues/256025, microsoft/vscode/issues/256027, microsoft/vscode/issues/256030, microsoft/vscode/issues/256033, microsoft/vscode/issues/256034, microsoft/vscode/issues/256036, microsoft/vscode/issues/256037, microsoft/vscode/issues/256038, microsoft/vscode/issues/256039, microsoft/vscode/issues/256042, microsoft/vscode/issues/256046, microsoft/vscode/issues/256050, microsoft/vscode/issues/256051, microsoft/vscode/issues/256052, microsoft/vscode/issues/256053, microsoft/vscode/issues/256054, microsoft/vscode/issues/256055, microsoft/vscode/issues/256056, microsoft/vscode/issues/256063, microsoft/vscode/issues/256066, microsoft/vscode/issues/256067, microsoft/vscode/issues/256069, microsoft/vscode/issues/256070, microsoft/vscode/issues/256071, microsoft/vscode/issues/256072, microsoft/vscode/issues/256074, microsoft/vscode/issues/256075, microsoft/vscode/issues/256078, microsoft/vscode/issues/256079, microsoft/vscode/issues/256080, microsoft/vscode/issues/256081, microsoft/vscode/issues/256086, microsoft/vscode/issues/256088, microsoft/vscode/issues/256090, microsoft/vscode/issues/256091, microsoft/vscode/issues/256094, microsoft/vscode/issues/256095, microsoft/vscode/issues/256099, microsoft/vscode/issues/256102, microsoft/vscode/issues/256109, microsoft/vscode/issues/256111, microsoft/vscode/issues/256112, microsoft/vscode/issues/256114, microsoft/vscode/issues/256116, microsoft/vscode/issues/256117, microsoft/vscode/issues/256118, microsoft/vscode/issues/256120, microsoft/vscode/issues/256121, microsoft/vscode/issues/256122, microsoft/vscode/issues/256125, microsoft/vscode/issues/256129, microsoft/vscode/issues/256133, microsoft/vscode/issues/256135, microsoft/vscode/issues/256138, microsoft/vscode/issues/256139, microsoft/vscode/issues/256140, microsoft/vscode/issues/256142, microsoft/vscode/issues/256145, microsoft/vscode/issues/256146, microsoft/vscode/issues/256148, microsoft/vscode/issues/256150, microsoft/vscode/issues/256151, microsoft/vscode/issues/256153, microsoft/vscode/issues/256158, microsoft/vscode/issues/256161, microsoft/vscode/issues/256165, microsoft/vscode/issues/256167, microsoft/vscode/issues/256168, microsoft/vscode/issues/256172, microsoft/vscode/issues/256176, microsoft/vscode/issues/256177, microsoft/vscode/issues/256179, microsoft/vscode/issues/256181, microsoft/vscode/issues/256182, microsoft/vscode/issues/256183, microsoft/vscode/issues/256186, microsoft/vscode/issues/256188, microsoft/vscode/issues/256189, microsoft/vscode/issues/256191, microsoft/vscode/issues/256192, microsoft/vscode/issues/256193, microsoft/vscode/issues/256199, microsoft/vscode/issues/256201, microsoft/vscode/issues/256203, microsoft/vscode/issues/256204, microsoft/vscode/issues/256206, microsoft/vscode/issues/256210, microsoft/vscode/issues/256211, microsoft/vscode/issues/256212, microsoft/vscode/issues/256213, microsoft/vscode/issues/256214, microsoft/vscode/issues/256215, microsoft/vscode/issues/256216, microsoft/vscode/issues/256220, microsoft/vscode/issues/256221, microsoft/vscode/issues/256224, microsoft/vscode/issues/256228, microsoft/vscode/issues/256230, microsoft/vscode/issues/256232, microsoft/vscode/issues/256233, microsoft/vscode/issues/256235, microsoft/vscode/issues/256240, microsoft/vscode/issues/256245, microsoft/vscode/issues/256246, microsoft/vscode/issues/256247, microsoft/vscode/issues/256251, microsoft/vscode/issues/256254, microsoft/vscode/issues/256255, microsoft/vscode/issues/256257, microsoft/vscode/issues/256261, microsoft/vscode/issues/256263, microsoft/vscode/issues/256264, microsoft/vscode/issues/256266, microsoft/vscode/issues/256268, microsoft/vscode/issues/256269, microsoft/vscode/issues/256271, microsoft/vscode/issues/256272, microsoft/vscode/issues/256275, microsoft/vscode/issues/256277, microsoft/vscode/issues/256279, microsoft/vscode/issues/256282, microsoft/vscode/issues/256286, microsoft/vscode/issues/256291, microsoft/vscode/issues/256292, microsoft/vscode/issues/256294, microsoft/vscode/issues/256295, microsoft/vscode/issues/256296, microsoft/vscode/issues/256297, microsoft/vscode/issues/256299, microsoft/vscode/issues/256302, microsoft/vscode/issues/256304, microsoft/vscode/issues/256305, microsoft/vscode/issues/256306, microsoft/vscode/issues/256312, microsoft/vscode/issues/256315, microsoft/vscode/issues/256316, microsoft/vscode/issues/256318, microsoft/vscode/issues/256324, microsoft/vscode/issues/256325, microsoft/vscode/issues/256328, microsoft/vscode/issues/256329, microsoft/vscode/issues/256330, microsoft/vscode/issues/256331, microsoft/vscode/issues/256332, microsoft/vscode/issues/256333, microsoft/vscode/issues/256335, microsoft/vscode/issues/256336, microsoft/vscode/issues/256337, microsoft/vscode/issues/256338, microsoft/vscode/issues/256341, microsoft/vscode/issues/256343, microsoft/vscode/issues/256344, microsoft/vscode/issues/256347, microsoft/vscode/issues/256354, microsoft/vscode/issues/256355, microsoft/vscode/issues/256357, microsoft/vscode/issues/256360, microsoft/vscode/issues/256361, microsoft/vscode/issues/256363, microsoft/vscode/issues/256364, microsoft/vscode/issues/256366, microsoft/vscode/issues/256373, microsoft/vscode/issues/256375, microsoft/vscode/issues/256376, microsoft/vscode/issues/256377, microsoft/vscode/issues/256379, microsoft/vscode/issues/256380, microsoft/vscode/issues/256383, microsoft/vscode/issues/256384, microsoft/vscode/issues/256393, microsoft/vscode/issues/256397, microsoft/vscode/issues/256401, microsoft/vscode/issues/256402, microsoft/vscode/issues/256403, microsoft/vscode/issues/256404, microsoft/vscode/issues/256408, microsoft/vscode/issues/256409, microsoft/vscode/issues/256414, microsoft/vscode/issues/256419, microsoft/vscode/issues/256420, microsoft/vscode/issues/256422, microsoft/vscode/issues/256423, microsoft/vscode/issues/256425, microsoft/vscode/issues/256426, microsoft/vscode/issues/256428, microsoft/vscode/issues/256429, microsoft/vscode/issues/256431, microsoft/vscode/issues/256433, microsoft/vscode/issues/256437, microsoft/vscode/issues/256440, microsoft/vscode/issues/256442, microsoft/vscode/issues/256443, microsoft/vscode/issues/256444, microsoft/vscode/issues/256448, microsoft/vscode/issues/256450, microsoft/vscode/issues/256451, microsoft/vscode/issues/256456, microsoft/vscode/issues/256457, microsoft/vscode/issues/256458, microsoft/vscode/issues/256459, microsoft/vscode/issues/256460, microsoft/vscode/issues/256462, microsoft/vscode/issues/256466, microsoft/vscode/issues/256469, microsoft/vscode/issues/256471, microsoft/vscode/issues/256473, microsoft/vscode/issues/256474, microsoft/vscode/issues/256475, microsoft/vscode/issues/256481, microsoft/vscode/issues/256482, microsoft/vscode/issues/256485, microsoft/vscode/issues/256486, microsoft/vscode/issues/256488, microsoft/vscode/issues/256494, microsoft/vscode/issues/256495, microsoft/vscode/issues/256500, microsoft/vscode/issues/256501, microsoft/vscode/issues/256502, microsoft/vscode/issues/256505, microsoft/vscode/issues/256509, microsoft/vscode/issues/256511, microsoft/vscode/issues/256515, microsoft/vscode/issues/256519, microsoft/vscode/issues/256520, microsoft/vscode/issues/256521, microsoft/vscode/issues/256522, microsoft/vscode/issues/256525, microsoft/vscode/issues/256526, microsoft/vscode/issues/256529, microsoft/vscode/issues/256530, microsoft/vscode/issues/256534, microsoft/vscode/issues/256535, microsoft/vscode/issues/256536, microsoft/vscode/issues/256537, microsoft/vscode/issues/256540, microsoft/vscode/issues/256543, microsoft/vscode/issues/256546, microsoft/vscode/issues/256549, microsoft/vscode/issues/256551, microsoft/vscode/issues/256552, microsoft/vscode/issues/256555, microsoft/vscode/issues/256556, microsoft/vscode/issues/256557, microsoft/vscode/issues/256560, microsoft/vscode/issues/256561, microsoft/vscode/issues/256570, microsoft/vscode/issues/256571, microsoft/vscode/issues/256574, microsoft/vscode/issues/256575, microsoft/vscode/issues/256577, microsoft/vscode/issues/256584, microsoft/vscode/issues/256587, microsoft/vscode/issues/256588, microsoft/vscode/issues/256592, microsoft/vscode/issues/256594, microsoft/vscode/issues/256595, microsoft/vscode/issues/256596, microsoft/vscode/issues/256597, microsoft/vscode/issues/256599, microsoft/vscode/issues/256600, microsoft/vscode/issues/256601, microsoft/vscode/issues/256602, microsoft/vscode/issues/256607, microsoft/vscode/issues/256610, microsoft/vscode/issues/256611, microsoft/vscode/issues/256619, microsoft/vscode/issues/256623, microsoft/vscode/issues/256624, microsoft/vscode/issues/256625, microsoft/vscode/issues/256626, microsoft/vscode/issues/256627, microsoft/vscode/issues/256628, microsoft/vscode/issues/256630, microsoft/vscode/issues/256632, microsoft/vscode/issues/256633, microsoft/vscode/issues/256635, microsoft/vscode/issues/256638, microsoft/vscode/issues/256640, microsoft/vscode/issues/256641, microsoft/vscode/issues/256642, microsoft/vscode/issues/256643, microsoft/vscode/issues/256650, microsoft/vscode/issues/256652, microsoft/vscode/issues/256653, microsoft/vscode/issues/256655, microsoft/vscode/issues/256656, microsoft/vscode/issues/256660, microsoft/vscode/issues/256662, microsoft/vscode/issues/256663, microsoft/vscode/issues/256665, microsoft/vscode/issues/256668, microsoft/vscode/issues/256672, microsoft/vscode/issues/256673, microsoft/vscode/issues/256676, microsoft/vscode/issues/256677, microsoft/vscode/issues/256679, microsoft/vscode/issues/256681, microsoft/vscode/issues/256683, microsoft/vscode/issues/256687, microsoft/vscode/issues/256688, microsoft/vscode/issues/256690, microsoft/vscode/issues/256692, microsoft/vscode/issues/256693, microsoft/vscode/issues/256697, microsoft/vscode/issues/256700, microsoft/vscode/issues/256702, microsoft/vscode/issues/256704, microsoft/vscode/issues/256709, microsoft/vscode/issues/256712, microsoft/vscode/issues/256713, microsoft/vscode/issues/256718, microsoft/vscode/issues/256721, microsoft/vscode/issues/256724, microsoft/vscode/issues/256728, microsoft/vscode/issues/256729, microsoft/vscode/issues/256730, microsoft/vscode/issues/256731, microsoft/vscode/issues/256732, microsoft/vscode/issues/256733, microsoft/vscode/issues/256734, microsoft/vscode/issues/256739, microsoft/vscode/issues/256740, microsoft/vscode/issues/256741, microsoft/vscode/issues/256745, microsoft/vscode/issues/256746, microsoft/vscode/issues/256748, microsoft/vscode/issues/256750, microsoft/vscode/issues/256751, microsoft/vscode/issues/256753, microsoft/vscode/issues/256755, microsoft/vscode/issues/256757, microsoft/vscode/issues/256758, microsoft/vscode/issues/256761, microsoft/vscode/issues/256771, microsoft/vscode/issues/256775, microsoft/vscode/issues/256777, microsoft/vscode/issues/256779, microsoft/vscode/issues/256780, microsoft/vscode/issues/256785, microsoft/vscode/issues/256786, microsoft/vscode/issues/256787, microsoft/vscode/issues/256789, microsoft/vscode/issues/256791, microsoft/vscode/issues/256792, microsoft/vscode/issues/256795, microsoft/vscode/issues/256796, microsoft/vscode/issues/256801, microsoft/vscode/issues/256803, microsoft/vscode/issues/256806, microsoft/vscode/issues/256807, microsoft/vscode/issues/256809, microsoft/vscode/issues/256810, microsoft/vscode/issues/256812, microsoft/vscode/issues/256813, microsoft/vscode/issues/256814, microsoft/vscode/issues/256815, microsoft/vscode/issues/256816, microsoft/vscode/issues/256817, microsoft/vscode/issues/256818, microsoft/vscode/issues/256822, microsoft/vscode/issues/256826, microsoft/vscode/issues/256828, microsoft/vscode/issues/256829, microsoft/vscode/issues/256830, microsoft/vscode/issues/256831, microsoft/vscode/issues/256833, microsoft/vscode/issues/256834, microsoft/vscode/issues/256835, microsoft/vscode/issues/256837, microsoft/vscode/issues/256838, microsoft/vscode/issues/256840, microsoft/vscode/issues/256842, microsoft/vscode/issues/256845, microsoft/vscode/issues/256846, microsoft/vscode/issues/256847, microsoft/vscode/issues/256850, microsoft/vscode/issues/256851, microsoft/vscode/issues/256852, microsoft/vscode/issues/256853, microsoft/vscode/issues/256854, microsoft/vscode/issues/256855, microsoft/vscode/issues/256857, microsoft/vscode/issues/256859, microsoft/vscode/issues/256860, microsoft/vscode/issues/256862, microsoft/vscode/issues/256865, microsoft/vscode/issues/256866, microsoft/vscode/issues/256867, microsoft/vscode/issues/256869, microsoft/vscode/issues/256870, microsoft/vscode/issues/256871, microsoft/vscode/issues/256872, microsoft/vscode/issues/256873, microsoft/vscode/issues/256874, microsoft/vscode/issues/256875, microsoft/vscode/issues/256876, microsoft/vscode/issues/256877, microsoft/vscode/issues/256879, microsoft/vscode/issues/256882, microsoft/vscode/issues/256884, microsoft/vscode/issues/256886, microsoft/vscode/issues/256888, microsoft/vscode/issues/256889, microsoft/vscode/issues/256890, microsoft/vscode/issues/256891

2.4 Closed Issues
This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable. 
Issues Closed This Week: 431
Summarized Issues:

Gemini Code Assist Malfunctions: The Gemini Code Assist extension for VS Code on Windows has issues with the "Accept All" button, leading to the creation of new "Untitled" files instead of modifying existing ones. Additionally, the Gemini 2.5 agent experiences significant delays and excessive file spawning, with files being duplicated over 100 times.
vscode/issues/255604, vscode/issues/255654

Activation Events Visibility: Visual Studio Code extensions editor fails to display implicit activation events like onView, onLanguage, and onCommand under the "Activation Events" section. This omission leads to confusion about extension activation, as users expect all possible events to be visible.
vscode/issues/255616

DisposableStore Error: An error occurs in Visual Studio Code when adding a disposable object to a DisposableStore that has already been disposed. This issue could potentially lead to a memory leak, although the error is not easily reproducible.
vscode/issues/255624

Unused Extensions Management: A feature proposal for Visual Studio Code aims to help developers manage unused extensions by tracking their last activation or usage frequency. This feature would display information in the Extensions view and offer options to disable or uninstall idle extensions, improving startup time and reducing memory usage.
vscode/issues/255625

GitHub Copilot Path Separator Issue: GitHub Copilot faces a problem on Linux remote servers accessed from a Windows-based VSCode UI, where backslashes are used as path separators. This incompatibility with Linux file path conventions prevents file creation or editing.
vscode/issues/255630

Performance Freezes: Visual Studio Code experiences performance issues, freezing after switching back from another program. Disabling GPU acceleration and dev-shm-usage resolves the problem.
vscode/issues/255634

Music Playback Feature Request: A feature request suggests integrating music playback, similar to Spotify, into Visual Studio Code to enhance the coding experience. The proposal includes implementing it as an extension, referencing existing extensions like vscode-spotify and Music Time.
vscode/issues/255636

Free Version Bug Report: A user questions the necessity of a free version of a software extension, given their use of ChatGPT 4.1 for free. The report includes details about the extension version, VS Code version, and system information.
vscode/issues/255638

Suggested Edits Discard Feature: A feature request for the VS Code extension version 0.29.0 seeks a simple method to discard or forget a list of 10 suggested edits. The current functionality does not allow users to remove them.
vscode/issues/255639

Copilot File Deletion Bug: Files deleted using Copilot in VS Code reappear after reopening the application. This issue may be due to a conflict with OneDrive file synchronization.
vscode/issues/255653

Language Model Unavailability: The Visual Studio Code extension version 0.29.0 reports a bug where the language model is unavailable on a Windows 10 system running VS Code version 1.102.0. This issue affects users' ability to utilize the extension effectively.
vscode/issues/255656, vscode/issues/255710, vscode/issues/256407

Live Server Extension Bug: The Live Server extension in Visual Studio Code is not functioning properly when writing HTML and JavaScript code. The issue is linked to specific system and extension information.
vscode/issues/255657

Grading System AttributeError: A user reports that the grading system fails to recognize code due to an AttributeError, resulting in all tests failing for tasks related to adding audio and source elements to website sections.
vscode/issues/255658

Public Code Block Error: Users receive an error message stating "Sorry, the response matched public code so it was blocked" when attempting to generate a table of members in an existing component using an updated extension in VS Code.
vscode/issues/255659, vscode/issues/255693, vscode/issues/255694, vscode/issues/256691

Chat and Inline Chat Issues: On Windows 11, users of the latest VSCode and Copilot extensions are unable to send chats or inline chats. The issue is resolved by downgrading VSCode and later discovering a missing copilot instructions file.
vscode/issues/255660

Copilot Pyramid Code Issue: A failure in GitHub Copilot occurs while attempting to fix a pyramid-related code issue in a public repository. The tool indicates it matches public code, and the user is unsure if the failure is due to a potential re-write of GitHub Copilot or another underlying issue.
vscode/issues/255661

Agent Mode Generating State Bug: The VS Code extension version 0.29.0 has a bug where the agent mode is stuck in a "generating" state, falsely indicating that 566 files have been changed. No actual changes have been made, and the same file is repeatedly listed.
vscode/issues/255662

Source Control Commit Fields Request: A request is made to add commit subject and comment message fields to the Source Control tab in Visual Studio Code to enhance its functionality.
vscode/issues/255663

Multi-line Commit Messages Support: A request is made to add support for multi-line commit messages in the Git sidebar of VS Code. This feature would enhance clarity and collaboration by allowing users to include detailed commit bodies alongside the subject line.
vscode/issues/255664

Pro Version Upgrade Recognition Issue: A user who upgraded to the pro version of an extension in Visual Studio Code finds that the software does not recognize the upgrade. This issue occurs despite using version 0.29.0 of the extension on VS Code version 1.102.0 on a Darwin arm64 system.
vscode/issues/255667

SyntaxError Resolution: A SyntaxError caused by an "Unexpected token" error in Visual Studio Code persists even after uninstalling and reinstalling the software. The issue is resolved by deleting all extensions in the user folder.
vscode/issues/255669

Gemini 2.5 Pro Budget Loss: A user experienced a loss of budget due to the Gemini 2.5 Pro editing a file 612 times without producing any results. The system logged successful operations, leading to frustration over paying for a service that did not deliver expected outcomes.
vscode/issues/255672, vscode/issues/255673, vscode/issues/255674

Copilot Malfunction After Plan Upgrade: A bug occurs where the Copilot feature in Visual Studio Code malfunctions after upgrading the plan. The issue persists despite using the specified extension and VS Code versions on a Darwin arm64 system.
vscode/issues/255681

Copilot Chat Formatting Issue: The GitHub Copilot extension for Visual Studio Code has a bug where code blocks are not formatted correctly during Copilot chat. Code is displayed in a single line without proper formatting, rendering the extension unusable.
vscode/issues/255688

Stuck at api.py File: A bug in the Visual Studio Code extension version 0.29.0 causes the application to get stuck at the api.py file. The user plans to resolve it by removing duplicated code at the end of the file.
vscode/issues/255691

413 Request Entity Too Large Error: A performance problem in Visual Studio Code results in a "413 Request Entity Too Large" error. The request payload exceeds the server's capacity to process it, occurring on a system running Windows 10 with VS Code version 1.102.0.
vscode/issues/255692, vscode/issues/256461, vscode/issues/256464, vscode/issues/256598

Unaccepted Copilot Edits Reversion: In Visual Studio Code, unaccepted Copilot edits are reverted upon restarting extensions, although the edits remain in the undo history. The issue was closed because the problem could not be reproduced in the latest version.
vscode/issues/255695

Dev Containers Error: Errors occur in Visual Studio Code when using Dev Containers with a valid devcontainer.json file, specifically after updating to version 1.102. The issue was resolved by updating the Dev Containers extension to version 0.422.1.
vscode/issues/255791

Telemetry Setting Misleading Description: The telemetry.telemetryLevel setting in Visual Studio Code has a misleading description. It fails to clarify that the setting is grayed out because it can only be configured for the Default profile, not custom profiles.
vscode/issues/255800

Live Share Extension Argument Error: A regression in the VS Code Insiders build causes the Live Share extension to fail with an "argument does not match" error. This issue is likely due to changes made in a recent pull request intended to fix Dev Containers.
vscode/issues/255805

Devcontainers Disconnecting with WSL: Devcontainers in Visual Studio Code repeatedly disconnect when using Windows Subsystem for Linux (WSL) after a recent update. The problem might be linked to a specific extension, as it works when extensions are disabled.
vscode/issues/255806

Debugger Launch Failure: The debugger in Visual Studio Code intermittently fails to launch properly because it sends incomplete or disordered commands to the terminal. This issue occurs particularly when using Git Bash, resulting in failed attempts to start the debugging process for a Python application with Uvicorn.
vscode/issues/255810

Quota Reached Message Error: A user with an active subscription receives a "quota reached" message while using version 0.29.0 of an extension in Visual Studio Code version 1.102.0 on a Windows 10 system.
vscode/issues/255814

Copilot Chat Extension Inquiry: A problem or inquiry related to the Copilot Chat Extension in Visual Studio Code prompts the user to provide specific version details and logs to aid in diagnosing the issue. However, it lacks detailed reproduction steps or a clear description of the problem.
vscode/issues/255835, vscode/issues/255836

Filtered Response Error: A bug in the Visual Studio Code extension version 0.29.0 results in a filtered response from the Responsible AI Service. Users are prompted to rephrase their request, as indicated by the error message and associated request ID.
vscode/issues/256126, vscode/issues/256127

Copilot Chat Model Unavailability: The chat model is unavailable for use in the VS Code extension version 0.29.0 on a Linux x64 system. This issue affects users' ability to utilize the extension effectively.
vscode/issues/256020

Copilot Chat Quota Reached Error: Users with a GitHub Copilot Pro subscription are incorrectly receiving notifications that they have reached their monthly chat messages quota. This issue persists despite having the pro version and being prompted to upgrade or wait for the allowance to renew.
vscode/issues/256751, vscode/issues/256924

Copilot Chat No Response Error: Users encounter a "Sorry, no response was returned" message while using the Copilot chat feature in Visual Studio Code. This issue affects users on various systems and configurations, leading to frustration and a lack of functionality.
vscode/issues/256386, vscode/issues/256388, vscode/issues/256390, vscode/issues/256413

Copilot Chat 400 Bad Request Error: A "400 Bad Request" error occurs in the Visual Studio Code extension version 0.29.1, preventing users from making successful requests. This issue affects users on various systems and configurations.
vscode/issues/256863, vscode/issues/256864

Copilot Chat 413 Request Entity Too Large Error: Users encounter a "413 Request Entity Too Large" error while using the Copilot chat feature in Visual Studio Code. This issue affects users on various systems and configurations, leading to frustration and a lack of functionality.
vscode/issues/256598, vscode/issues/256637

Copilot Chat Responsible AI Service Error: Users encounter a message stating "A resposta foi filtrada pelo Serviço de IA Responsável" (The response was filtered by the Responsible AI Service) when using the Copilot chat feature in Visual Studio Code. This issue affects users on various systems and configurations.
vscode/issues/256465, vscode/issues/256634

Copilot Chat Language Model Unavailability: The language model is unavailable in the Visual Studio Code extension version 0.29.1, affecting users' ability to utilize the extension effectively. This issue affects users on various systems and configurations.
vscode/issues/256407, vscode/issues/256657, vscode/issues/256658

Copilot Chat Premium Request Quota Error: Users encounter a message indicating that they have reached their premium request quota while using the Copilot chat feature in Visual Studio Code. This issue affects users on various systems and configurations.
vscode/issues/256751, vscode/issues/256924