Weekly GitHub Report for Vscode: September 01, 2025 - September 08, 2025 (12:05:18)
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:
The current version of this repository is 1.98.2
1.2 Version Information:
The version released on March 12, 2025, primarily focuses on resolving various issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." For a comprehensive overview of all updates and improvements, users are directed to the official release notes on the Visual Studio Code 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.
-
duplicate prompts show up: This issue reports that duplicate prompts appear when using a specific shell prompt configuration, particularly involving the Starship prompt in the terminal, causing the split button to be unresponsive and only allowing the "Allow" button to be clicked. The reporter confirms the problem reproduces consistently and shares detailed environment information and screenshots, while others attempt to reproduce the issue but initially cannot until the specific shell prompt setup is clarified.
- The discussion centers on reproducing the issue, with initial attempts failing until the reporter reveals the use of the Starship prompt in zsh as a key factor. Multiple users share environment details and screenshots, and it is concluded that the problem is linked to the shell prompt configuration rather than the software version itself.
- Number of comments this week: 13
-
Chat breaks when closing window with chat session: This issue describes a bug where closing a newly opened chat window causes the main chat panel to go blank and triggers an error related to a disposed InstantiationService. The problem arises because the application currently allows the same chat session to be opened in multiple places, which leads to the disposal of the chat view’s active model and subsequent UI corruption.
- The comments discuss that opening the same chat session in multiple windows or views should be prevented to avoid breaking the chat panel. A fix was implemented by removing the "open in new window" action to prevent duplicate chat instances, and verification confirmed the action is no longer available; however, the underlying issue of opening the same chat twice remains a concern, with related issues and steps referenced for further investigation.
- Number of comments this week: 10
-
The root cause of all the issues with folding set as indentation: This issue addresses persistent problems with the folding feature in VS Code when the folding strategy is set to indentation, causing folding ranges to become out of sync and behave unexpectedly across various file types. The user highlights that common workarounds like resetting folding ranges or toggling folding strategies no longer reliably fix the problem, and requests a proper fix or a way to reset the folding cache state without closing all tabs or restarting the editor.
- Commenters confirm the folding desynchronization affects multiple languages and that typical fixes such as cut-paste or removing manual folding ranges often fail. The discussion clarifies that indentation-based folding is purely structural and lacks syntax awareness, unlike language-specific folding providers, and that some bugs stem from flaky folding range providers or pasting over collapsed regions. Users share detailed repro steps and express frustration over the lack of a straightforward reset mechanism, while maintainers explain the current folding logic and suggest filing issues against specific language extensions if needed.
- Number of comments this week: 10
-
Switches to wrong selected Model: This issue reports a bug where selecting the GPT-5 model in the VS Code extension results in responses coming from GPT-4.1 instead, despite the user’s explicit choice. The problem occurs consistently with GPT-5 but not with GPT-5-mini, and disabling telemetry settings temporarily resolves the issue, suggesting it may be related to an ongoing experiment affecting model selection.
- The discussion involved requests for evidence and confirmation of the bug, with the user providing screenshots and recordings showing GPT-4.1 responses despite selecting GPT-5. Disabling telemetry was found to fix the issue, indicating the problem might stem from an experimental deployment or configuration conflict. The maintainers acknowledged the bug, linked it to an experiment, and decided to pause the experiment while investigating the root cause.
- Number of comments this week: 10
-
Opening
vscodefolder asks for more permissions right away: This issue reports that when opening thevscodefolder in the VS Code Insiders build with Copilot enabled, the user is immediately prompted to grant additional GitHub permissions, whereas this prompt does not appear in the stable version. The discussion investigates whether this behavior is expected due to authentication scopes and session upgrades related to Copilot, with detailed log comparisons showing that Insiders requests a permissive session upgrade while stable does not, possibly due to differences in repository access or underlying GitHub services.- The comments clarify that the permission prompt is expected behavior triggered by Copilot's authentication upgrade process when opening private repositories or when minimal scopes are insufficient. Users share detailed logs from both stable and insiders versions, revealing that insiders requests a permissive session upgrade while stable does not, and the difference may stem from changes in GitHub repo services or remote configurations; no definitive bug is identified, and the behavior is considered by design.
- Number of comments this week: 9
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 asking for the ability to display markdown generated by code cells in the notebook outline, similar to how JupyterLab handles dynamic titles produced by code outputs. The requester wants an option for the notebook outline to recognize and show these code cell-generated markdown titles, enhancing the outline's functionality to include dynamically created content.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue reports a bug in Visual Studio Code where using a vscode:// link with the query parameters ?new-window or ?reuse-window does not behave as expected when opening remote SSH connections. Instead of opening a new window or reusing the existing one, the current remote connection is disconnected and replaced by the new connection, causing loss of the original session.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set to "process," causing the terminal process to fail to start due to an invalid executable path. The reporter notes that while${userHome}works correctly when the task type is "shell" with PowerShell as the default shell, it produces malformed paths on Windows when used with "process," and that using${env:USERPROFILE}is a viable workaround that results in properly formatted paths.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where the terminal in a floating window does not echo typed characters in real time when connected to a remote environment, such as WSL or SSH, and the main VS Code window is minimized. The characters only appear after the main window is restored, indicating a communication delay likely caused by the remote connection entering a sleep state when the main window is minimized, which does not get resolved by simply opening the floating terminal window.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is pasted into Visual Studio Code, it is incorrectly rendered as a question mark instead of displaying the correct symbol. The problem occurs on Fedora 39 with VS Code version 1.87.2, and the character displays properly in other applications like Firefox, indicating a rendering bug specific to VS Code.
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: 626
Summarized Issues:
- Performance and Stability Issues: Multiple reports describe Visual Studio Code and its extensions crashing, freezing, or becoming unresponsive under various conditions, including large workspaces, specific CPU architectures, and during use of GitHub Copilot or chat features. These issues cause significant disruption to user workflows, requiring restarts or workarounds to regain functionality.
- GitHub Copilot and Chat Extension Malfunctions: Numerous issues report GitHub Copilot and Copilot Chat extensions failing to respond, crashing, losing context, or not applying code changes as expected. Users experience problems such as infinite loading, missing model selections, incorrect file edits, and repeated error messages, severely impacting AI-assisted coding productivity.
- issues/264245, issues/264250, issues/264287, issues/264307, issues/264332, issues/264335, issues/264350, issues/264353, issues/264363, issues/264379, issues/264421, issues/264423, issues/264447, issues/264463, issues/264534, issues/264585, issues/264712, issues/264779, issues/264814, issues/264848, issues/264850, issues/264907, issues/265078, issues/265149, issues/265196, issues/265254, issues/265286, issues/265328, issues/265333, issues/265358, issues/265429, issues/265494
- Extension and Feature Bugs in Code Editing and Agent Modes: Several issues describe bugs where extensions or agents fail to apply code changes, hang indefinitely, or produce incorrect or incomplete edits. Problems include agent mode not writing files, chat agents stuck in working states, and extensions failing to complete tasks or commands, leading to user frustration and workflow interruptions.
- Terminal and Integrated Shell Issues: Users report persistent problems with the integrated terminal, including inability to open WSL terminals, terminal hangs, cursor disappearance, and command suggestion failures. These issues affect terminal usability and integration with AI tools, causing workflow disruptions.
- Chat and Conversation UI/UX Problems: Multiple issues highlight problems with chat session management, including inability to create or delete chats properly, chat history not updating, UI glitches like flickering or overlapping text, and accessibility issues such as missing screen reader announcements. These degrade the user experience in chat-based workflows.
- Settings, Configuration, and Feature Requests: Users request new features such as disabling specific commit characters, grouping search results by glob patterns, preserving custom instructions during summarization, and adding keyboard shortcuts for accessibility. Other issues report bugs in settings application, model management, and extension activation.
- Code Generation and Editing Anomalies: Several issues describe problems where code suggestions or generated code are misplaced, incomplete, or cause corruption. This includes issues with indentation, duplicated code, failure to remove duplicates, and unexpected file deletions by AI extensions, leading to loss of work and reduced trust in AI assistance.
- Workspace, File, and Project Management Issues: Users report problems opening folders, adding or deleting workspace folders, and issues with file explorer behavior such as unexpected jumps or missing files. These issues hinder project navigation and management within VS Code.
- Accessibility and Screen Reader Support Deficiencies: Several issues highlight missing or inadequate support for screen readers, including lack of announcements for progress, warnings, and suggestion counts, as well as keyboard navigation problems, reducing usability for users relying on assistive technologies.
- Update, Installation, and Extension Activation Problems: Users experience issues with extension signature verification failures, disabled repositories after updates, and extensions failing to activate or requiring manual reloads, complicating maintenance and usage of VS Code and its extensions.
- issues/264431, issues/264484, issues/264826, issues/264935, issues/265076, issues/265132, [issues/265248](https://github.com/issues/265248], issues/265250, issues/265472
- Miscellaneous UI and UX Issues: Various reports include inconsistent iconography, misaligned UI elements, flickering effects, confusing button states, and requests for improved visual feedback and layout consistency to enhance the overall user interface experience.
- Feature Requests for Enhanced AI and Development Tools: Users request new capabilities such as AI integration with debugging, support for additional file formats in Copilot, improved API testing tools, multi-tab chat support, and better management of AI customization and context to improve developer productivity and experience.
- issues/264283, issues/264708, issues/265184, issues/265400, issues/265449, issues/265451, issues/265452, issues/265453, issues/265456, issues/265485, issues/265496, [issues/265501](https://github.com/issues/265501]
- Authentication and Account Management Issues: Problems include sign-in popups opening on incorrect ports, repeated authorization errors, and confusion over account selection, which hinder seamless access to GitHub and Copilot features within VS Code.
- Code Completion and IntelliSense Failures: Users report IntelliSense and code completion features failing to load or respond, including stuck loading states and suggestions that interfere with normal editing, reducing coding efficiency.
- Chat History and Session Management Bugs: Issues include chat history truncation, failure to update or delete sessions properly, and inconsistent session synchronization across devices, leading to confusion and loss of context.
- issues/264521, issues/264532, issues/264760, issues/265079, [issues/265161](https://github.com/issues/265161]
- Token and API Key Handling Problems: Users face issues with token expiration, invalid API keys causing UI failures, and repeated prompts for upgrades despite active subscriptions, impacting uninterrupted AI service usage.
- issues/265316, issues/265253, issues/264913, [issues/265134](https://github.com/issues/265134]
- File and Folder Handling Bugs: Problems include inability to delete folders, unexpected file creations, and issues with file renaming and explorer behavior, complicating file management within VS Code.
- issues/265273, issues/265339, issues/265468, [issues/265493](https://github.com/issues/265493]
- Miscellaneous Bugs and Errors: Various isolated bugs include JSON parsing errors, markdown preview not refreshing, and unexpected UI freezes or crashes during specific operations, affecting overall stability and usability.
- issues/265091, issues/265277, [issues/265515](https://github.com/issues/265515], issues/265165, issues/265246, issues/265434
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: 712
Summarized Issues:
- GitHub Copilot and Chat Extension Malfunctions: Numerous issues report that GitHub Copilot and its Chat extension frequently fail to function correctly, including problems with initialization delays, unresponsiveness, failure to write or update code, repeated login prompts, and incorrect or missing UI elements. These malfunctions occur across various platforms and VS Code versions, often requiring restarts or reinstallations, and sometimes cause data loss or corrupted states.
- issues/260731, issues/260912, issues/261071, issues/261083, issues/261152, issues/261724, issues/261987, issues/261990, issues/262849, issues/262865, issues/262883, issues/262942, issues/263025, issues/263037, issues/263041, issues/263045, issues/263057, issues/263062, issues/263063, issues/263072, issues/263082, issues/263096, issues/263118, issues/263239, issues/263247, issues/263250, issues/263326, issues/263428, issues/263551, issues/263577, issues/263601, issues/263680, issues/263682, issues/263690, issues/263759, issues/263765, issues/263768, issues/263794, issues/263808, issues/263831, issues/263944, issues/264003, issues/264007, issues/264009, issues/264010, issues/264022, issues/264026, issues/264294, issues/264335, issues/264349, issues/264358, issues/264440, issues/264473, issues/264549, issues/264635, issues/264679, issues/264840, issues/264852, issues/264855, issues/265018, issues/265073, issues/265139, issues/265152, issues/265163, issues/265411
- Agent Mode and File Editing Failures: Multiple reports indicate that the agent mode in the VS Code extension fails to perform file edits, often claiming to have updated code without actually applying changes, or causing files to be empty or restored unexpectedly. These issues cause significant disruption to workflows, with some users experiencing repeated credit usage without results and others forced to manually intervene or restart to regain functionality.
- Terminal and Task Execution Issues: Several issues describe problems with terminal behavior and task execution, including freezing terminals, failure to recognize user input, premature disposal of editor models, and commands not being auto-approved correctly. These problems affect usability and automation, causing delays, lost input, and inconsistent command execution across different shells and platforms.
- Model Selection and API Key Problems: Users report that model selection dropdowns disappear or revert unexpectedly, preventing use of paid or newer models, and that API keys are sometimes not recognized or lost, causing authentication failures and inability to use certain AI features. These issues affect both Copilot and Claude models, impacting user access to advanced AI capabilities.
- Performance and Responsiveness Problems: Many users experience severe performance degradation, including slow startup, freezing, unresponsive UI elements, and long delays in IntelliSense or chat responses. These issues occur on various platforms and configurations, sometimes linked to large files, complex projects, or specific extension versions.
- Chat UI and Session Management Issues: Problems include chat sessions not opening or updating correctly, input boxes stealing focus, duplicate or missing chat history entries, and UI elements like buttons or tooltips not functioning as expected. These issues degrade the chat experience and complicate session navigation and management.
- JSON Schema Validation Errors in Tool Inputs: Numerous issues report 400 errors caused by invalid JSON schemas in tool input definitions that do not conform to the JSON Schema draft 2020-12 specification, leading to request failures and inability to use certain tools or models. This is a widespread problem affecting multiple extensions and models.
- issues/264963, issues/264964, issues/264965, issues/264966, issues/264968, issues/264970, issues/264972, issues/264973, issues/264975, issues/264976, issues/264978, issues/264979, issues/264980, issues/264981, issues/264982, issues/264984, issues/264985, issues/264986, issues/264987, issues/264988, issues/264990, issues/264992, issues/264994, issues/264995, issues/264996, issues/264998, issues/264999
- Network and Authentication Failures: Users encounter network errors such as net::ERR_NETWORK_CHANGED and net::ERR_CONNECTION_CLOSED, often related to firewall or VPN restrictions, causing failures in requests and authentication problems with GitHub Copilot and other AI services. These issues prevent normal operation and require network troubleshooting.
- Accessibility and Keyboard Navigation Problems: Issues include incomplete keyboard navigation and screen reader support in the TodoList tool, incorrect narrator announcements, and focus stealing in chat sessions, which hinder accessibility and usability for users relying on assistive technologies.
- Feature Requests and Usability Enhancements: Users request features such as automatic inclusion of MCP resources, drag-and-drop for chat sessions, hiding thinking tokens, group policy options to disable Code Review features, multi-edit tools for Claude, improved font settings in chat, and better management of chat history and sessions. These requests aim to improve workflow efficiency and user experience.
- Code Suggestion and Editing Bugs: Several issues describe problems where code suggestions are duplicated, inserted incorrectly inside methods, or overwritten unexpectedly, and where autocomplete is difficult to disable, causing frustration and workflow disruption.
- File and Workspace Management Issues: Users report bugs where files are unexpectedly deleted, restored, or created outside the workspace, folders fail to open or show contents, and workspace variables like
${workspaceFolder}are not resolved correctly, causing confusion and data loss.
- Miscellaneous Bugs and UI Glitches: Various other bugs include cursor placement errors, flickering UI elements, incorrect syntax highlighting, broken keyboard shortcuts, and inconsistent tooltip behavior, all contributing to a degraded user experience.
- Extension Signature Verification Failures: Some extensions, including Copilot and others, fail signature verification on certain platforms, preventing proper installation or use.
- Large File and Merge Editor Issues: Handling of large files and merge conflicts is problematic, with crashes, incorrect labeling of changes, and failure to open merge editors for renamed and edited files.
- Authentication and Sign-In Problems: Users face issues signing in with Microsoft accounts due to invalid client configurations, Keychain errors on macOS, and hanging sign-in dialogs, affecting extensions like C# Dev Kit and others.
- Miscellaneous Feature Requests: Requests include adding a delete command for focused chats, support for local model servers, improved MCP resource handling, and safeguarding PII in compliance with IRS guidelines.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a single user expressing intense frustration and dissatisfaction with a product, using highly charged and confrontational language. The tone is aggressive and accusatory, with no responses or attempts at resolution visible in the thread. The lack of engagement from others leaves the tension unaddressed, suggesting potential for escalation if further comments are made.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of dialogue)
- This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and frustration in a confrontational tone without any responses or further interaction.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, hostile tone)
- This GitHub conversation involves a single user expressing intense frustration and anger through aggressive and profane language directed at the product and its functionality. The tone is highly confrontational and hostile, with no responses or attempts at resolution visible in the conversation. The tension is triggered by perceived repeated failures and dissatisfaction with the product's performance.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, insults, lack of dialogue)
- This GitHub conversation features a single user expressing intense frustration and anger through aggressive and insulting language directed at the development team, with no responses or further comments present.
-
- Toxicity Score: 0.85 (Aggressive language, hostile tone, lack of moderation)
- This GitHub conversation consists solely of an initial post with a highly aggressive and offensive title, with no subsequent comments or interactions. The tone is hostile from the outset, and the lack of dialogue leaves the situation unresolved but potentially volatile.
III. Pull Requests
3.1 Open Pull Requests
This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Opened This Week: 44
Key Open Pull Requests
1. Add Multi-Diff Editor view for Search Results using existing components: This pull request implements a new "View as Multi-Diff" feature for search results in VS Code that opens each file in a separate diff editor with syntax highlighting and diff capabilities using existing multi-diff editor components, thereby enhancing the search experience while preserving the original search editor functionality and following established architectural patterns.
- URL: pull/264766
- Merged: No
2. Fix chat session disposal error by implementing move behavior instead of duplicate opening: This pull request addresses and fixes a disposal error in the chat feature by replacing the previous behavior of opening duplicate chat session instances across multiple windows with a "move" behavior that ensures only one instance of a chat session exists at a time, preserving view state and properly closing original instances to prevent shared service references and related errors when auxiliary windows are closed.
- URL: pull/265038
- Merged: No
3. fix: memory leak in InlayHints: This pull request addresses a memory leak in the InlayHints feature by introducing a new CancellationStore class that manages disposables more effectively, replacing the previous approach where sessionDisposables grew indefinitely during repeated scrolling events.
- URL: pull/265185
- Merged: No
Other Open Pull Requests
3.2 Closed Pull Requests
This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.
Pull Requests Closed This Week: 218
Key Closed Pull Requests
1. Empty state chat history: This pull request proposes adding a chat history feature to the empty state in settings under chat.emptyState.history.enabled, including UI improvements such as hiding the chat history link when the list is empty and adjusting disclaimer spacing, to address issue #251187 in the VSCode repository, although it has not been merged.
- URL: pull/262430
- Merged: No
2. add tool references to prompt file variables and ICustomChatModes: This pull request adds tool references to prompt file variables and the ICustomChatModes interface in Visual Studio Code to address issue #262159.
- URL: pull/264414
- Merged: 2025-09-05T10:58:51Z
3. Allow deleting and renaming history from chat session view: This pull request enhances the Chat Sessions sidebar view by adding both delete and rename functionalities for chat history items, enabling users to manage session entries directly with inline renaming, confirmation dialogs for deletion, immediate UI updates, and consistent behavior aligned with the existing chat history quick pick.
- URL: pull/264797
- Merged: 2025-09-03T04:31:28Z
Other Closed Pull Requests
3.3 Pull Request Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.
IV. Contributors
4.1 Contributors
Active Contributors:
We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.
If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.
| Contributor | Commits | Pull Requests | Issues | Comments |
|---|---|---|---|---|
| Copilot | 399 | 70 | 0 | 19 |
| Tyriar | 182 | 13 | 96 | 165 |
| meganrogge | 244 | 8 | 45 | 143 |
| roblourens | 44 | 6 | 70 | 213 |
| bpasero | 141 | 23 | 60 | 103 |
| TylerLeonhardt | 98 | 5 | 15 | 107 |
| mjbvz | 77 | 14 | 59 | 70 |
| justschen | 74 | 12 | 6 | 85 |
| connor4312 | 29 | 7 | 31 | 101 |
| lramos15 | 34 | 1 | 5 | 123 |