Weekly GitHub Report for Vscode: August 04, 2025 - August 11, 2025 (22:43:28)
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.
-
Explorer View no longer syncs to active source file in editor: This issue reports a bug where the Explorer view in VS Code no longer synchronizes with the active source file in the editor, and the "Reveal Active File In Explorer" command fails to work. This regression appeared after updating to version 1.103.0 and affects users working in remote environments such as WSL2, with various attempts to mitigate the problem including disabling extensions, reloading the window, and switching sidebars.
- Commenters suggested using the Extension Bisect tool to identify problematic extensions, but this did not resolve the issue for all users. Several workarounds were shared, such as moving the Explorer to the opposite sidebar and back or downgrading to version 1.102.3. The problem was linked to a specific recent commit, and switching to the insiders build provided temporary relief, though the issue recurred. The discussion also included requests to pin the issue to reduce duplicates and calls for related feature finalizations.
- Number of comments this week: 17
-
"Open with Code" old context menu option missing from Explorer on version 1.103.0: This issue reports that after installing Visual Studio Code version 1.103.0 on Windows, the "Open with Code" option is missing from the Windows Explorer context menu despite selecting the option during installation. Users confirm the problem occurs after updating, with some noting that reinstalling earlier versions restores the context menu item, and a specific commit is identified as the cause of the regression.
- Multiple users confirm the disappearance of the "Open with Code" context menu option after updating to version 1.103.0, despite installation settings being correctly selected. Several suggest workarounds such as reinstalling older versions or modifying installation steps, while a contributor points to a recent commit that removed the old context menu entry, explaining the regression.
- Number of comments this week: 15
-
vscode opens the terminal to automatically execute the environment activation command, and opens the cmd window: This issue describes a problem in VSCode where opening a new terminal automatically runs environment activation commands that cause a visible command prompt window to flash, introduce startup delays, and sometimes freeze the terminal. The user expects the terminal to open directly in the specified ML environment instantly without showing these activation commands or pop-up windows, and seeks configuration advice to achieve this behavior.
- Multiple users confirm experiencing similar issues with the terminal not activating the correct environment or causing visible pop-ups and delays; attempts to fix it by toggling settings like "python.useEnvironmentsExtension" or changing terminal profiles have not resolved the problem, and the discussion references related issues and logs without a definitive solution.
- Number of comments this week: 11
-
copilot not working inside jupyter notbook: This issue reports that GitHub Copilot is not functioning inside Jupyter notebooks within VS Code, specifically when triggering the inline suggestion command (Ctrl+I), resulting in a timeout error stating that Copilot took too long to get ready. The user notes that the extension version is 0.30.0, VS Code version is 1.103.0, and the problem occurs on Windows 10, with logs showing repeated errors related to an invalid network address preventing Copilot from connecting to its server.
- The comments reveal that multiple users experience the same problem after a recent VS Code update, with inline Copilot working in Python scripts but failing in notebooks. Diagnostic steps were suggested, including enabling trace logging and checking various output channels, which confirmed repeated "net::ERR_ADDRESS_INVALID" errors indicating connection failures; however, some users noted no additional errors in logs, suggesting the issue might be specific to notebook integration rather than general authentication or server availability.
- Number of comments this week: 11
-
Branch display not updated when changing branch using git command in terminal: This issue reports a bug where the branch name displayed in the VS Code status bar does not update when changing branches using the
git checkoutcommand in the integrated terminal. Users experience an error when clicking the branch name after switching branches, which temporarily resolves after reloading the window and closing all files, but can reoccur, especially after restarting the extension host.- The discussion confirms the issue is reproducible consistently by multiple users on different platforms and VS Code Insider versions. Users report an error triggered by clicking the branch name, which disappears after reloading the window but may return after extension host restarts. The maintainers request reproduction steps or recordings to diagnose the problem further, and the issue is temporarily closed pending further reports.
- Number of comments this week: 10
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 shows titles from code cell outputs alongside markdown cells. The requester highlights that this functionality would allow dynamic content generated by code to be reflected in the outline view, improving usability and aligning the behavior with JupyterLab's existing features.
- 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 an existing one, the current remote connection is forcibly replaced, causing the user to lose their original session and disrupting workflow.
${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 toprocess, causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}produces malformed paths like/c:/Users/myuser/myfolder/my.exe, using${env:USERPROFILE}instead results in correctly formatted paths and successful task execution.- 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, if the main VS Code window is minimized. The characters only appear after restoring the main window, indicating that the remote connection may enter a sleep state when the main window is minimized, causing a delay in terminal updates despite no actual freeze occurring.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is copied 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 or font support issue within 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: 595
Summarized Issues:
- Code suggestion and completion issues: Multiple reports describe problems with code suggestion features in the VS Code extension, including premature or unwanted code snippet suggestions, persistent or incorrect autocomplete prompts, and failures in code generation or editing. These issues affect user experience by causing distractions, incorrect code insertions, or complete failure of code completion functionality across various platforms and extension versions.
- Extension version 0.29.1 stability and performance problems: Numerous issues report that the VS Code extension version 0.29.1 exhibits severe stability and performance problems, including infinite loading states, failure to apply code changes, high CPU usage, freezing, and random hallucinations such as creating dummy files or repeating strings. These problems cause significant disruption to workflows on multiple operating systems and VS Code versions.
- Copilot and Copilot Chat extension authentication and sign-in failures: Several issues describe problems where users cannot sign in, are incorrectly reported as not signed in, or receive misleading error messages about authentication status in the GitHub Copilot and Copilot Chat extensions. These issues prevent proper extension functionality and cause confusion despite users having valid accounts and installed extensions.
- Agent mode and chat session bugs: Multiple reports highlight issues with the agent mode and chat sessions in the VS Code extension, including infinite loops, failure to apply edits, loss of context, inability to switch modes, and chat windows freezing or not responding. These problems degrade the interactive AI-assisted coding experience and cause workflow interruptions.
- Terminal and shell integration issues: Several issues report problems with terminal command completion, shell integration, and terminal behavior in VS Code, including premature command termination, inability to kill active terminals, environment variable conflicts, and missing or incorrect terminal environment activation. These issues affect terminal usability and integration with AI features.
- issues/259562, issues/259677, issues/259670, issues/260334, issues/260387, issues/260601, issues/260819, issues/260821, [issues/260888](https://github.com/issues/260888]
- Performance and freezing problems in VS Code: Multiple users report severe performance degradation, freezing, and unresponsiveness in VS Code, including slow loading, lag when switching tabs, high CPU usage, and crashes, often linked to extension usage or specific VS Code versions. These issues significantly impact productivity and stability.
- Git and source control related bugs: Several issues describe problems with Git integration in VS Code, including slow commit operations, failure to stage or commit changes properly, issues with undoing file renames, problems with Git submodules, and authentication errors during Git operations. These bugs hinder version control workflows.
- Markdown and preview rendering issues: Users report problems with Markdown preview, including poor text contrast in dark themes, failure of the "Open Preview" option, and rendering bugs such as LaTeX formulas not displaying correctly or text appearing bolder intermittently. These issues affect content readability and editing experience.
- Environment and configuration inconsistencies: Several issues highlight problems with environment variable resolution in devcontainers, inconsistent casing in UI text, failure to merge user and workspace settings, and issues with workspace folder variable resolution. These inconsistencies cause confusion and unexpected behavior in configuration and environment management.
- File handling and editing bugs: Multiple reports describe bugs where files are unexpectedly recreated after deletion, syntax coloring disappears, files revert after saving, or edits do not persist. These issues cause data loss, confusion, and hinder code editing workflows.
- Model and API integration problems: Several issues report that certain AI models (e.g., Gemini, GPT-5) are unresponsive, stuck in loops, or provide incorrect or incomplete responses. There are also requests for improved model handling, error code support, and API performance optimizations. These problems affect AI-assisted coding reliability.
- User interface and usability enhancements requests: Multiple feature requests seek improvements such as drag-and-drop terminal tabs, multi-tab chat sessions, better undo/redo integration, improved tool selection UI, and enhanced chat session management. These aim to improve user experience and workflow efficiency.
- Authentication and network errors: Several issues report network errors such as
net::ERR_NETWORK_CHANGEDornet::ERR_ACCESS_DENIEDaffecting extension connectivity, often requiring firewall or network troubleshooting. These errors disrupt extension functionality and user workflows.
- Accessibility and screen reader problems: Some issues highlight accessibility shortcomings, including screen readers announcing extra content, lack of keyboard navigation support in task lists, and inconsistent color usage in syntax highlighting, which hinder users relying on assistive technologies.
- Miscellaneous bugs and feature requests: Additional issues cover a wide range of topics such as build errors due to custom Visual Studio paths, missing context in chat, problems with file drag-and-drop, and requests for improved prompt refinement and AI usage statistics.
- issues/259576, issues/259710, issues/259711, issues/260128, issues/260349, [issues/260652](https://github.com/issues/260652], issues/260769, issues/260759
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: 740
Summarized Issues:
- GitHub Copilot and Chat Extension Failures: Numerous issues report that GitHub Copilot and its Chat extension frequently fail to function properly across various platforms and VS Code versions. Problems include authentication loops, model unavailability, request failures with 400 or 500 errors, inability to generate or apply code edits, quota mismanagement, and crashes during use, severely impacting user productivity and causing frustration.
- issues/255855, issues/256025, issues/256179, issues/256282, issues/256729, issues/256786, issues/256949, issues/256953, issues/256971, issues/257212, issues/257228, issues/257233, issues/257245, issues/257257, issues/257265, issues/257329, issues/257696, issues/258104, issues/258113, issues/258217, issues/258227, issues/258339, issues/258366, issues/258436, issues/258449, issues/258471, issues/258510, issues/258513, issues/258526, issues/258543, issues/258618, issues/258627, issues/258755, issues/258758, issues/259377, issues/259378, issues/259391, issues/259404, issues/259405, issues/259427, issues/259545, issues/259622, issues/259628, issues/259632, issues/259678, issues/259679, issues/259681, issues/259733, issues/259740, issues/259755, issues/260008, issues/260017, issues/260023, issues/260036, issues/260241, issues/260243, issues/260244, issues/260245, issues/260273, issues/260274, issues/260285, issues/260324, issues/260347, issues/260355, issues/260406, issues/260444, issues/260558, issues/260561, issues/260562, issues/260630, issues/260667, issues/260670, issues/260774, issues/260780, issues/260782, issues/260783, issues/260785, issues/260789, issues/260790, issues/260795, issues/260796, issues/260812, issues/260815, issues/260817, issues/260822, issues/260879
- "Open with VS Code" Context Menu Missing on Windows: Many users report that after recent VS Code updates, the "Open with Code" or "Open with VS Code" option disappears from the Windows File Explorer right-click context menu for files and folders. This issue persists despite reinstalling VS Code with all context menu options enabled, causing significant disruption to workflows that rely on quick folder or file opening from Explorer.
- issues/256373, issues/259491, issues/260419, issues/260432, issues/260468, issues/260480, issues/260483, issues/260487, issues/260495, issues/260509, issues/260545, issues/260564, issues/260571, issues/260576, issues/260580, issues/260589, issues/260595, issues/260596, issues/260603, issues/260604, issues/260607, issues/260612, issues/260627, issues/260635, issues/260642, issues/260645, issues/260827, issues/260844
- Performance and Freezing Issues in VS Code: Several reports describe severe performance degradation, freezing, and unresponsiveness in VS Code, often linked to specific extensions like GitHub Copilot or large file handling. Users experience slow loading, editor freezes, delayed output in terminals, and crashes, which disrupt workflows and require frequent restarts or reinstallation.
- Terminal and Shell Integration Problems: Multiple issues report problems with terminal behavior in VS Code, including command truncation, failure to recognize commands, broken shortcuts, and issues with terminal auto-approval of commands. Some terminals fail to clear contents or handle environment variables correctly, and there are requests for improved terminal UI features like floating terminals and better command history search.
- Authentication and Sign-In Issues: Users report problems signing into GitHub Copilot and other services within VS Code, including persistent sign-in loops, timeouts, and errors related to OAuth and token expiration. These issues prevent access to Copilot features and cause repeated authentication failures despite correct credentials and network conditions.
- Code Generation and Editing Failures: Several issues describe failures in code generation or editing by AI agents and Copilot, including incomplete or incorrect code insertions, infinite loops, duplicated lines, and failure to apply edits despite indicating success. These bugs cause loss of work, corrupted files, and user frustration.
- Quota and Subscription Management Problems: Users frequently encounter issues with Copilot subscription recognition, quota resets, and trial activation. Problems include premature quota exhaustion messages, failure to upgrade to Pro features, and incorrect subscription status, leading to inability to use paid features despite valid subscriptions.
- File and Workspace Management Bugs: Issues include files being deleted or corrupted unexpectedly, inability to create or rename files/folders, workspace folders disappearing after reload, and problems with Git worktrees and file operations. These bugs cause data loss and disrupt development workflows.
- Search and Navigation Issues: Problems include search functionality getting stuck or not respecting encoding settings, auto reveal in Explorer not working, and navigation features like "Go to Definition" or "Reveal Active File" failing or behaving inconsistently.
- UI and UX Concerns: Users report jarring delays, confusing or missing UI elements, misplaced icons, and requests for improved visual distinction in chat contexts, terminal UI improvements, and better keyboard shortcut support.
- Extension Installation and Update Failures: Some users report inability to install or update extensions, signature verification failures, and extensions becoming unresponsive or non-functional after updates, affecting overall VS Code usability.
- Security and Privacy Concerns: Reports include unexpected deletion of files by AI agents, unauthorized code sharing flagged as public code, and critical bugs causing data loss or system hacks, raising concerns about safety and trust in the tools.
- Feature Requests and Improvements: Users request enhancements such as better multi-account GitHub support, improved terminal features, incremental code review during AI generation, and more flexible keyboard shortcut configurations.
- Release Planning and Iteration Coordination: Issues outline detailed iteration plans, endgame checklists, and release coordination steps for the July 2025 VS Code release, emphasizing schedules, testing, verification, and branching to ensure smooth deployment.
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.
-
Copilot constantly lies about it's knowledge and tries to gaslight the user about functionality
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation involves a user expressing strong dissatisfaction and distrust towards the software, using accusatory and emotionally charged language. The tone is confrontational and frustrated, with no constructive dialogue or responses visible. The initial comment triggers tension by implying unethical behavior, which may provoke defensive or equally hostile replies in the future.
-
Support creating a new chat session/editor for Coding Agent
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a single comment from an anonymous user expressing frustration and distrust towards the software, using accusatory and emotionally charged language. The tone is negative and confrontational, with no direct engagement from other participants, which may indicate a potential for escalation if further comments continue in a similar vein.
-
Bug Report: Faulty Looping Behavior in GitHub Copilot
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, user frustration)
- This GitHub conversation involves multiple users expressing frustration and dissatisfaction with the software's behavior, with one user explicitly calling it a scam and another acknowledging ongoing efforts to fix the issue. The tone shifts from accusatory and negative to somewhat neutral and polite, as seen in a brief thank you comment. Tension is primarily triggered by perceived software failures and user dissatisfaction, leading to some hostile remarks.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided frustration)
- This GitHub conversation involves a single user expressing intense frustration and anger towards the handling of their code, using aggressive and profane language. The tone is highly emotional and accusatory, with no responses or attempts at resolution visible in the thread. The lack of engagement from others and the user's hostile language suggest a volatile atmosphere with potential for escalation if others join the discussion.
-
MAKING INVISIBLE CHANGES TO THINGS THAT DO NOT EXIST
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, sarcasm, repeated unfulfilled promises)
- This GitHub conversation involves a user expressing strong frustration and disappointment with the responses and actions of the maintainers or contributors, highlighting a pattern of unfulfilled promises and vague assurances without concrete code changes. The tone is critical and sarcastic, with the user emphasizing inefficiency and lack of transparency in the development process. The conversation escalates due to repeated claims of feature implementation that are not substantiated by actual code, leading to a tense and accusatory atmosphere.
-
LOSING MY TIME WITH YOUR COPILT!!!
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided venting)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with an AI tool, using aggressive and profane language to convey their negative experience. The tone is highly emotional and confrontational, with no responses or dialogue from other participants, indicating a one-sided venting rather than a collaborative discussion. The tension is triggered by perceived failures of the AI to follow instructions and provide correct code, leading to the user's declaration of wasted time and threats of negative feedback.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a single user expressing strong frustration and distrust towards a bot's performance, using accusatory and emotionally charged language without any responses or dialogue from others. The tone is highly negative and confrontational, with no signs of resolution or moderation.
-
- Toxicity Score: 0.55 (Moderate possibility, frustration, sarcasm, perceived dismissal, escalating tension)
- This GitHub conversation involves a user expressing frustration and disappointment with recent software updates, highlighting issues and regressions. The tone is initially factual but shifts to sarcastic and exasperated, especially when the user feels their concerns are dismissed or mishandled by automated responses or support processes. Tension is triggered by perceived lack of effective support and repeated problems despite attempts to troubleshoot and rollback. The interaction suggests a growing distrust and dissatisfaction with the handling of the issue.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, personal attacks)
- This GitHub conversation involves a user expressing intense frustration and using highly offensive language directed at others, with a dismissive and aggressive tone. Another participant responds with a similarly provocative and disrespectful comment, escalating the tension. The interaction is marked by personal attacks and a lack of constructive dialogue, indicating a hostile environment.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive remarks)
- This GitHub conversation involves a user expressing extreme frustration and anger towards the software and its payment model, using aggressive and offensive language. Another participant responds dismissively and with hostility, escalating the tension. The tone throughout is highly confrontational and emotionally charged, with no attempts at constructive dialogue. The trigger of tension is the initial user's dissatisfaction and perceived unfairness, which provokes a defensive and rude reply.
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: 45
Don't miss what's next. Subscribe to Weekly Project News: