Weekly Project News

Archives

Weekly GitHub Report for Vscode: April 25, 2026 - May 02, 2026 (19:19:52)

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 update primarily focuses on resolving various issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." For a comprehensive overview of all changes and enhancements, users are directed to the official Visual Studio Code updates page.

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.

As of our latest update, there are no active issues with ongoing comments this week.

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.

As of our latest update, there are no stale issues for the project this week.

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: 0

Summarized Issues:

As of our latest update, there are no open issues for the project this week.

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: 21

Summarized Issues:

  • UI and Accessibility Issues: Several problems affect the user interface and accessibility in VS Code, including icons that are too close and look similar causing accidental actions, and insufficient color contrast for keyboard focus indicators that hinder navigation for keyboard-only and low-vision users. These issues reduce usability and accessibility, impacting the overall user experience.
  • [issues/307319, issues/307581]
  • Performance and Stability Problems: Users experience significant performance degradation and stability issues such as white glitches caused by Riot Vanguard downloads, VS Code Insiders freezing due to GitHub Copilot Agent running CLI commands, and frequent unexpected editor reloads. These problems disrupt workflow and require multiple restarts or workarounds to continue coding.
  • [issues/307399, issues/307723, issues/309201]
  • Copilot and Extension Failures: Multiple bugs affect Copilot and related extensions, including disappearing code samples in chat history, non-functional Capilot extension returning 400 errors, server error 500 failures in certain extension versions, and errors with Copilot lacking detailed reproduction steps. These issues prevent reliable use of AI-assisted coding features.
  • [issues/307672, issues/308531, issues/309041, issues/309270]
  • Authentication and Integration Requests: Users request features to improve integration and authentication, such as reusing VS Code authentication in Agents to avoid repeated sign-ins and supporting absolute paths for skills locations to better handle GitHub Codespaces. These enhancements aim to streamline workflows and improve multi-repository support.
  • [issues/307610, issues/308028]
  • Agent and Terminal Compatibility Bugs: The execution subagent is incompatible with the new asynchronous terminal implementation, limiting its ability to check terminal output and causing erratic behavior due to its synchronous design. This incompatibility raises concerns about correct context handling when async tasks complete.
  • [issues/308048]
  • Data Serialization and Session Loss: A serialization error during chat session storage causes a RangeError due to invalid string length, resulting in session loss if the window is closed unexpectedly. This bug risks losing user data and ongoing work.
  • [issues/308484]
  • Build and Connection Errors: The ProjectBuildSnapshotService encounters a System.AggregateException from a lost JSON-RPC connection during design-time builds, causing unexpected closure of project system data flow even without active development. This disrupts the build process and project stability.
  • [issues/309004]
  • Quality and Performance Discrepancies in AI Plans: The $40 AI plan produces lower quality code and performs worse on simple prompts compared to the $10 plan and Pi Agent, especially within VS Code, leading to dissatisfaction with higher-tier subscriptions.
  • [issues/309046]
  • Feature Requests for Enhanced Functionality: Users request new features such as a game resource launcher integrated into VS Code to browse, download, and launch educational and entertainment games from a centralized panel, aiming to expand the platform's utility.
  • [issues/309061]
  • Conversation and Session State Bugs: Reasoning models like Claude Sonnet 4.6 get stuck in a “Compacting conversation” loop causing delays, and switching mode selectors mid-conversation updates the UI without changing session state, leading to unavailable tools and potential user confusion. These bugs degrade interaction quality and reliability.
  • [issues/309166, issues/309275]
  • User Frustration and Unprofessional AI Feedback: A user expresses frustration that the AI feature in VS Code is unprofessional, wastes time, and negatively impacts their work despite having a subscription, highlighting dissatisfaction with AI performance and support.
  • [issues/309318]
  • Incomplete or Non-Descriptive Issue Reports: Some issues, such as the "Dream" template submission, lack specific details or reproduction steps, limiting their usefulness for troubleshooting or resolution.
  • [issues/309124]
  • Platform and Environment Compatibility Issues: Certain extension versions fail to work properly on specific platforms, such as version 0.35.3 not functioning on VS Code 1.107.1 with a remote Linux environment on Windows 10, causing usability problems for affected users.
  • [issues/308892]

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.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.


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: 0

As of our latest update, there are no open pull requests for the project this week.

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: 0

As of our latest update, there are no closed pull requests for the project this week.

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.

As of our last update, there are no open or closed pull requests with discussions going on within 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
yogeshwaran-c 112 0 0 0
roblourens 104 0 4 0
joshspicer 105 0 0 0
lszomoru 90 0 0 0
DonJayamanne 75 0 0 0
Copilot 75 0 0 0
meganrogge 58 0 0 0
dmitrivMS 57 1 0 0
osortega 51 0 0 0
pwang347 46 0 0 0

Don't miss what's next. Subscribe to Weekly Project News:
Powered by Buttondown, the easiest way to start and grow your newsletter.