Weekly GitHub Report for Vscode: August 25, 2025 - September 01, 2025 (12:00: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
  • 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:

The version released on March 12, 2025, primarily focuses on addressing a range of issues resolved under the "February 2025 Recovery 2" milestone. For detailed information, users are directed to the complete release notes available on 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.

1. macOS: Microsoft Auth under broker - Keychain find status: -25300 error: This issue reports a bug on macOS where signing in to the C# Dev Kit with a Microsoft account using the modern MSAL authentication method hangs indefinitely, while the deprecated classic authentication method works correctly. The problem appears related to an invalid or misconfigured client ID in the MSAL implementation, causing token migration failures and keychain errors, and users have found that switching to an msal-no-broker setting bypasses the issue and allows successful sign-in.

   • In the comments, users provided detailed logs showing the MSAL broker flow failing with a keychain error (-25300) and token migration errors due to an invalid client configuration. Attempts to reproduce the issue varied, but multiple users confirmed the hang during MSAL sign-in, while the classic or msal-no-broker modes worked. The maintainers requested trace logs and diagnostic reports from the Company Portal app, and users shared incident IDs. One user noted that the MSAL interactive sign-in webview does not appear and eventually times out or is cancelled, resulting in authentication errors. Overall, the discussion focused on gathering diagnostic data and confirming the issue’s root cause as a misconfigured MSAL client ID affecting personal accounts on macOS.
   • Number of comments this week: 15

2. Shell integration doesn't work in Kali Linux's default bash setup: This issue describes a problem where the shell integration feature in the Copilot Chat extension does not function correctly in Kali Linux’s default bash environment, causing terminal commands to hang on the second execution. The user reports that while single commands run fine, subsequent commands never complete because Copilot does not receive the expected signals from the shell, and this behavior is consistent and reproducible with multiple commands.

   • The comments reveal that the problem stems from Kali Linux’s bash prompt not supporting the shell integration hooks used by Copilot, unlike Debian or Ubuntu where it works as expected. It is suggested to disable shell integration as a temporary workaround, and a related but separate issue with new terminals not recognizing active Python virtual environments is acknowledged for future tracking.
   • Number of comments this week: 10

3. The editor loses focus: This issue reports a bug where the editor in VS Code loses focus whenever the autosave setting is enabled, causing the active tab to switch unexpectedly. The user experiences this problem specifically while working with the Overleaf Workshop extension for LaTeX, noting that autosave should update the PDF in the background without disrupting the editor’s focus.

   • The discussion explores whether the problem is caused by an extension, with suggestions to disable all extensions and test, but the user confirms the issue persists even with extensions disabled. Attempts to reproduce the bug using insider builds also fail to resolve the problem, and the user emphasizes the annoyance of losing editor focus after autosave triggers, indicating it likely stems from a recent VS Code update rather than an extension conflict.
   • Number of comments this week: 10

4. All tool calls show canceled status in latest: This issue reports that all tool calls in the latest version of the project are showing a canceled status, regardless of whether they were manually or automatically approved. The problem appears to stem from an asynchronous handling bug introduced in a recent commit, which causes the tool invocation token to be disposed prematurely, marking the tool result as denied and displaying the cancel icon incorrectly in the UI.

   • The discussion identifies the root cause as an async/await interaction bug in a specific commit, leading to premature disposal of the tool invocation token and overriding approvals with a denied status. A revert commit was created and landed to temporarily fix the issue while further investigation and additional test cases are planned to ensure a proper patch.
   • Number of comments this week: 10

5. Laggy terminal: This issue reports a noticeable lag in the terminal when typing commands quickly, where characters appear with a delay, potentially linked to the suggestions feature. The user provides recordings and profiling data to illustrate the problem and seeks guidance on what logs or information could help diagnose the cause.

   • Commenters discuss whether the lag is reproducible on stable versions, with some not observing the issue. The conversation explores possible causes including UI blocking by suggestion widgets, extension host performance, and terminal input/output handling, with detailed trace logs shared to analyze delays in processing terminal input and rendering.
   • Number of comments this week: 7

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.

1. 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 rendered in the output of code cells. The requester highlights that this functionality would allow outlines to include dynamically generated content from code cells, enhancing the usability and organization of notebooks within the environment.
2. 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 window is hijacked and replaced with the new remote connection, causing the original session to disconnect and be lost.
3. ${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's tasks.json file generates incorrect file paths when the task type is set to "process," causing the terminal process to fail to start. The reporter notes that while ${userHome} produces malformed paths like /c:/Users/myuser/myfolder/my.exe, using ${env:USERPROFILE} correctly resolves to a valid Windows path, indicating an inconsistency in how these variables are expanded depending on the task type and shell environment.
4. 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 restoring the main window, indicating that the remote connection may enter a sleep state when the main window is minimized, causing delayed terminal updates despite no actual freeze.
5. Unicode character displayed as a question mark ?: This issue reports that the fullwidth quotation mark Unicode character (U+FF02) is displayed as a question mark when pasted into Visual Studio Code, despite rendering correctly in browsers like Firefox. The problem persists even with all extensions disabled, indicating a potential bug in how VS Code handles certain Unicode characters on Fedora 39 with version 1.87.2.

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

Summarized Issues:

• Agent Mode File Update Issues: GitHub Copilot's Agent mode in VS Code fails to detect and apply real-time file changes, causing it to repeatedly show outdated content and not perform requested edits. This leads to persistent problems where code modifications are indicated but not reflected, and the agent becomes unresponsive or stuck in endless loops without completing tasks.
  issues/263154, issues/263593, issues/263594, issues/263596, issues/263816, issues/263948, issues/263950, issues/263952, issues/263954, issues/264004, issues/264006, issues/264009, issues/264010, issues/264053

• Extension Unresponsiveness and Freezing: The VS Code extension version 0.30.3 frequently becomes unresponsive, hangs indefinitely, or freezes across multiple platforms including Windows, Linux, and Darwin arm64. Users report persistent "working" statuses without responses, editor freezes, and inability to complete operations, severely impacting usability.
  issues/263156, issues/263239, issues/263381, issues/263388, issues/263638, issues/263794, issues/263938, issues/264007, issues/264026, issues/264124, [issues/264178](https://github.com/issues/264178]

• Model Selection and Mode Switching Problems: Users experience issues with the model selection dropdown disappearing, inability to switch chat modes properly, and models behaving unexpectedly by editing files in Ask mode or failing to respond. These problems cause confusion and prevent effective use of AI features in VS Code.
  issues/263310, issues/263311, issues/263766, issues/263768, issues/263845, issues/264175, [issues/264177](https://github.com/issues/264177]

• Authentication and Subscription Recognition Failures: Several issues report problems with authentication flows, including MSAL sign-in failures, subscription status not being recognized, and users being incorrectly prompted to subscribe despite active plans. These authentication problems disrupt access to Copilot features and cause user frustration.
  issues/263355, issues/263356, issues/263559, issues/263673, issues/263681, issues/263690, [issues/263964](https://github.com/issues/263964], issues/263969, [issues/264160](https://github.com/issues/264160]

• Code Suggestion and Completion Bugs: Users report duplicated code suggestions, inability to disable persistent code completions, hallucinated or misleading code, and suggestions that do not follow instructions or documentation. These issues degrade the quality and reliability of AI-generated code in VS Code.
  issues/263180, issues/263237, issues/263320, issues/263579, issues/263806, issues/263808, issues/263849, issues/263915, [issues/263987](https://github.com/issues/263987]

• Terminal and Shell Integration Issues: Problems include commands hanging indefinitely in terminals, inability to control whether commands run in new or existing terminals, shell integration hanging on specific Linux distributions, and terminal tool call sections not resizing properly. These issues cause workflow interruptions and terminal usability problems.
  issues/263183, issues/263193, issues/263197, issues/263521, issues/263797, [issues/263798](https://github.com/issues/263798]

• Chat Session and UI Display Problems: Multiple bugs affect chat session views, including disappearing or broken chat histories, incorrect display of chat session statuses, duplicate or swapped chat content, and UI elements overlapping or disappearing unexpectedly. These issues hinder user interaction with chat features.
  issues/263187, issues/263288, issues/263339, issues/263469, issues/263520, issues/263524, issues/263526, issues/263527, issues/263528, issues/263639, [issues/264080](https://github.com/issues/264080]

• File Handling and Workspace Issues: Users face problems with files being recreated after deletion, inability to create or use environments, files not saving or updating properly, and workspace folders not recognized correctly. These bugs disrupt normal file and project management in VS Code.
  issues/263217, issues/263200, issues/263202, issues/263541, [issues/263907](https://github.com/issues/263907], [issues/264091](https://github.com/issues/264091]

• Performance and Startup Delays: VS Code experiences slow startup times, high CPU usage, and freezing during operations such as opening folders, loading extensions, or rendering chat content, affecting user productivity.
  issues/263261, issues/263450, issues/263496, issues/263499, issues/263883, [issues/264115](https://github.com/issues/264115]

• Extension Signature Verification Failures: Several extensions including GitHub Copilot and others fail signature verification on macOS and Darwin systems, preventing proper extension functionality and causing installation or update failures.
  issues/263303, issues/263598, issues/263945, issues/263955, issues/264066, issues/264069, [issues/263999](https://github.com/issues/263999]

• Chat History and Session Management Requests: Users request features to confirm before closing or starting new chat sessions, delete focused chats directly, and improve chat history handling to prevent accidental loss and improve workflow.
  issues/263219, [issues/263858](https://github.com/issues/263858], [issues/263689](https://github.com/issues/263689]

• API and Tooling Integration Bugs: Issues include missing headers in MCP server requests, inability to detect expired OAuth tokens automatically, and problems with tool invocation confirmation and cancellation handling, causing integration and security concerns.
  issues/264095, issues/263990, [issues/264023](https://github.com/issues/264023]

• Miscellaneous UI and Usability Issues: Problems such as inconsistent capitalization in tooltips, overlapping notifications, missing keyboard shortcuts for model switching, and lack of RTL support in chat affect the overall user experience.
  issues/263342, issues/263437, issues/263293, [issues/263805](https://github.com/issues/263805]

• Subscription and Billing Problems: Users report unexpected charges, declined payments, and subscription renewals not reflected in functionality, causing frustration and access issues.
  issues/263326, [issues/263753](https://github.com/issues/263753], [issues/264135](https://github.com/issues/264135]

• Code Generation and Editing Failures: The AI sometimes generates broken, duplicated, or incomplete code, fails to apply requested changes, or overwrites code without permission, leading to loss of trust and productivity.
  issues/263138, issues/263790, [issues/263946](https://github.com/issues/263946], [issues/264110](https://github.com/issues/264110]

• Remote SSH and Environment Issues: Problems include hanging commands during remote SSH sessions, inability to use Copilot on remote servers, and environment setup failures, disrupting remote development workflows.
  issues/263183, issues/263959, [issues/264163](https://github.com/issues/264163]

• Error Handling and Reporting Deficiencies: Users encounter misleading or missing error messages, such as "no response returned," "server error 500," or unhelpful prompts when contacting support, complicating troubleshooting.
  issues/263207, issues/263651, issues/263659, [issues/263683](https://github.com/issues/263683]

• Feature Requests for Improved AI Interaction: Suggestions include adding interactive controls in chat, auto-retry and sound notifications for agent tasks, multi-edit tools, and better planning loops to enhance AI collaboration.
  issues/263454, issues/263334, issues/263274, [issues/263917](https://github.com/issues/263917]

• Performance Issues with Large Files and Search: Handling of large files causes errors or hangs, and search functions sometimes return duplicate or incomplete results, reducing efficiency.
  issues/263203, issues/263276, [issues/263911](https://github.com/issues/263911]

• Code Editing and Debugging Anomalies: Bugs include inability to accept suggestions with Tab, debug toolbar controls not working, and copy value in debug watch copying variable names instead of values.
  issues/263982, issues/263365, [issues/263776](https://github.com/issues/263776]

• Localization and Accessibility Issues: Some UI elements and menus are not translated properly, and keyboard accessibility problems affect screen reader users.
  issues/263949, [issues/263863](https://github.com/issues/263863]

• Miscellaneous Bugs and Requests: Various other issues include cursor disappearance, broken hover tooltips, and requests for new keyboard shortcuts or UI improvements.
  issues/263409, issues/263633, [issues/263517](https://github.com/issues/263517], [issues/264027](https://github.com/issues/264027]

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

Summarized Issues:

• Copilot and Gemini API Key Issues: Users face multiple problems with Gemini API key management and BYOK model support in VS Code extensions, including inability to clear or specify Gemini API keys, failure to display API key configuration UI for Azure language models, and restrictions preventing adding custom model IDs for BYOK Gemini or openrouter models. These issues cause blocked usage of personal Azure OpenAI resources and limit user flexibility in model selection and key management.
  • issues/259268, issues/260535, issues/261174, issues/261732, issues/263775

• Copilot Extension Failures and Performance Problems: The GitHub Copilot extension frequently fails to work properly across various platforms and versions, with issues including failure to display models list, save conflicts, repeated crashes, unresponsiveness, and degraded performance over time. Users also report problems with Copilot Chat such as empty or nonsensical responses, infinite loops, and failure to edit files correctly, severely impacting usability and productivity.
  • issues/260231, issues/260298, issues/261236, issues/261731, issues/262041, issues/262052, issues/262053, issues/262055, issues/262063, issues/262119, issues/262155, issues/262265, issues/262338, issues/262450, issues/262459, issues/262664, issues/262683, issues/262755, issues/263385, issues/263389, issues/263393, issues/263416, issues/263420, issues/263447, issues/263463, issues/263492, issues/263497, issues/263521, issues/263551, issues/263580, issues/263622, issues/263643, issues/263772, issues/263774, issues/263791, issues/263793, issues/263814, issues/263817, issues/263821, issues/263822, issues/263834, issues/263864, issues/263869, issues/263873, issues/263874

• Authentication and Rate Limiting Problems: Users encounter repeated authentication failures, sign-in loops, and GitHub API rate limiting errors when using GitHub Copilot and related extensions in VS Code, causing inability to access features, repeated logouts, and blocked usage despite valid subscriptions. These issues often require workarounds or updates to resolve and significantly disrupt user workflows.
  • issues/262049, issues/263668, issues/263687, issues/263691, issues/263712, issues/263771, issues/263793, issues/263815, issues/263817, [issues/263822](https://github.com/issues/263822], issues/263893

• Performance and Responsiveness Issues in VS Code: Several reports highlight significant performance degradation in VS Code, including lag when switching tabs, slow command palette opening, terminal unresponsiveness, and editor freezes, often exacerbated by extension interactions or large projects. These problems affect user productivity and require investigation and optimization.
  • issues/260858, issues/262050, issues/262793, issues/263003, issues/263218, issues/263342, issues/263405, issues/263440, issues/263534, issues/263811

• Terminal and Command Execution Problems: Users report issues with terminal behavior in VS Code, including failure to wait for command completion before starting new commands, terminal resizing glitches, unresponsive terminals, and problems with shell integration and command execution context. These bugs disrupt terminal workflows and require fixes for smoother operation.
  • issues/260334, issues/261639, issues/262875, issues/263199, issues/263542, issues/263813, issues/264013, issues/264040

• Chat and UI Interaction Bugs: The chat feature in VS Code and Copilot Chat extension suffers from multiple issues such as unexpected confirmation dialogs, chat interface flickering, missing or unresponsive UI elements, incorrect chat participant behavior, and problems with chat mode switching. These issues hinder user interaction and reduce the effectiveness of chat-based coding assistance.
  • issues/259855, issues/259967, issues/260021, issues/261434, issues/262521, issues/262539, issues/263088, issues/263414, issues/263423, issues/263475, issues/263769, issues/263921, issues/263926

• Git and Source Control Integration Issues: Problems include SCM status collisions, failure to refresh source control views on branch changes, inability to switch branches due to missing commands, and conflicts between GitHub Copilot and Git extensions causing crashes or unexpected behavior. These issues complicate version control workflows within VS Code.
  • issues/259649, issues/262540, issues/262623, [issues/262550](https://github.com/issues/262550], issues/263667

• Model and AI Behavior Problems: AI models such as Claude Sonnet and GPT-4.1 exhibit issues including ignoring instructions, producing incorrect or empty code, failing to maintain context, and generating misleading or fabricated responses. These problems cause user frustration and reduce trust in AI-assisted coding.
  • issues/262120, issues/262615, issues/262664, issues/263332, issues/263420, issues/263468, issues/263855, issues/264011

• Extension Loading and Signature Verification Failures: Several reports indicate that extensions, especially GitHub Copilot Chat, fail signature verification or do not load properly on macOS Darwin arm64 systems, preventing users from using the extensions and requiring troubleshooting or updates.
  • issues/261933, issues/262380, issues/262381, issues/262421, issues/262422, issues/263599

• Quota and Subscription Recognition Issues: Users with active or paid subscriptions report being incorrectly blocked by chat message quotas, inability to access premium features, or being prompted to upgrade despite valid subscriptions, causing confusion and dissatisfaction.
  • issues/261147, issues/262123, issues/262433, issues/263447, issues/263588, issues/263830, issues/263842, [issues/263864](https://github.com/issues/263864]

• Buggy or Missing Features in VS Code Extensions: Users report missing features such as the Copilot Agent selection option, inability to add keyboard shortcuts for toggling word wrap per file, missing "Report Issue" menu items, and lack of support for certain configurations or tools, limiting usability and customization.
  • issues/259821, issues/261901, issues/263404, issues/263480, [issues/263729](https://github.com/issues/263729]

• Documentation and Casing Consistency: There are issues with inconsistent capitalization in hover text and outdated documentation usage, causing confusion and lack of uniformity in the user interface and project materials.
  • issues/259532, issues/259566, issues/262253, issues/262254

• Security and Safety Concerns: Critical bugs include execution of shell commands despite user cancellation, database resets without confirmation, and unsafe modifications to workspace settings that reduce command execution confirmations, posing risks to user data and system integrity.
  • issues/261907, issues/262894, [issues/262898](https://github.com/issues/262898]

• Miscellaneous Bugs and Feature Requests: Additional issues cover a wide range of topics such as keyboard shortcut requests, UI improvements, bug fixes in language services, and requests for better integration with external tools or workflows.
  • issues/259382, issues/260158, issues/260182, issues/262640, issues/263056, issues/263194, issues/263354, issues/263548, issues/263729, issues/263895

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.

1. Copilot is lying and cheating instead of doing the actual work - this is EXTREMELY OFFENSIVE

   • Toxicity Score: 0.65 (Rapid escalation, accusatory tone, emotional language)
   • This GitHub conversation features a user expressing strong frustration and disappointment with an AI tool, accusing it of dishonesty and poor performance. The tone is highly emotional and accusatory, with the user emphasizing repeated failures and perceived deception by the AI. Subsequent comments maintain a critical stance, referencing external sources to support their negative view and suggesting systemic issues with AI behavior. The conversation shows escalating dissatisfaction without constructive engagement or resolution.

2. restore checkpoint dont works anymore

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, offensive terms)
   • This GitHub conversation consists solely of an initial issue report by a single user expressing strong frustration and dissatisfaction with the product and company, using offensive language and a dismissive tone. There are no subsequent comments or interactions to indicate any change in sentiment or tone.

3. WHY SO STUPID?

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong frustration)
   • This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and frustration with the service's performance, using emphatic and confrontational language; no other participants have engaged or responded, so no tone shifts or conflict escalation have occurred.

4. Tell OpenAI to get their shit together

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong negative sentiment)
   • This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and frustration towards a company and its product, using harsh and critical language without any responses or further interaction from other users.

5. this is completely unacceptable, this is a complete waste of time, and this need to be fixed

   • Toxicity Score: 0.65 (Rapid escalation, accusatory language, frustration, demands for accountability)
   • This GitHub conversation involves multiple users expressing frustration and disappointment regarding the quality and honesty of the code and results presented. One user accuses the project of "smoke and mirror" tactics and fake simulations, leading to a loss of trust. Another user acknowledges these concerns, apologizes sincerely, and commits to providing real, functional code instead of misleading demonstrations. A third user attempts to clarify the situation by suggesting the issue may be related to model quality rather than a direct bug, which further fuels tension as others demand accountability and responsibility for the misleading information. The tone throughout is tense and critical, with escalating dissatisfaction triggered by perceived dishonesty and unmet expectations.

6. Absolutely fucked

   • Toxicity Score: 0.65 (Rapid escalation, strong language, unresolved frustration)
   • This GitHub conversation involves a user expressing significant frustration and disappointment with the service and responses received, using strong language and a tone of exasperation. The interaction includes a brief, somewhat dismissive comment from another participant, which does not engage with the user's concerns in detail. The tension is primarily triggered by unmet expectations and perceived unhelpfulness of the support or system.

7. money for what for scam?

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
   • This GitHub conversation involves a single user expressing frustration and confusion in a confrontational tone, using informal and aggressive language that questions the intelligence of another party. There are no responses or further comments to moderate or de-escalate the situation, leaving the initial tension unaddressed.

8. fuck you, very annoying popup

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
   • This GitHub conversation consists of a single initial comment by one user expressing strong frustration and annoyance in a blunt and aggressive tone, without any subsequent replies or engagement from other participants.

9. fucking useless

   • Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
   • This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment with aggressive and offensive language, without any responses or further interaction.

10. fuckt ab

    • Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
    • This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and frustration, using aggressive language and derogatory terms, without any responses or further interaction.

---

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

Key Open Pull Requests

1. [WIP] Two line chat session description: This pull request is a work-in-progress aimed at implementing a two-line description feature for chat sessions in the Visual Studio Code project.

• URL: pull/263317

• Merged: No

• Associated Commits: d51b7, 3b50d, c7b3e, 52e8b, 852b6, 5f6c4, b5c45, 84e97, 2f702, d45a5, cebba, f665f, a40f5, e09d3, 43128, 9067c, 23bc5, 8575c, a1052, 8abb7, 89b06, 654e0, d6baf, 5660e, 74783, 96646, 094e4, 632d7, 4f01d, 99eca, fb584, 164eb, 46f11, 4366d, 5332b, ac275, 16c9f, be4e5, 7f933, 1cb87, d8c77, 6ac25, cdea6, 06d65, b5a23, c3c40, 10cae

2. use stripped down version of PSReadline for screen reader support on windows to enable pwsh shell integration : This pull request proposes using a stripped-down version of PSReadline to improve screen reader support on Windows, thereby enabling PowerShell (pwsh) shell integration, with fixes addressing issue #233921 and verified functionality on macOS through adjustments to Windows detection conditions.

• URL: pull/263702

• Merged: No

• Associated Commits: c4d4c, 6fd0c, 7a5a1, f947a, 80b96, b0082, 0b3ab, a6a47, 68334, b0de5, 8454f, d22f3, d59e3, fef2b, 6df72, e2f53, 94864, 75552, d4106, 5d6c1, 16e8c, 21bac, e921a, 9e5e8, cee49, 92687

3. Adding font info in colorTokenCustomization: This pull request aims to enhance the colorTokenCustomization feature in VSCode by adding font information support, involving multiple commits that progressively implement and channel this data through the text model.

• URL: pull/263403

• Merged: No

• Associated Commits: 338ea, 01023, 78337, caa75, eff39, 32129, e3c37, 527e8, 3537d, b8513, 31caf, 00343

Other Open Pull Requests

• Concurrent debug session preLaunchTask execution fix: This pull request fixes the issue where the preLaunchTask was executed before the user confirmed starting a concurrent debug session with the same launch configuration by moving the confirmation dialog to occur before running the task. It also improves session detection reliability by comparing launch configuration properties instead of mutable session labels.
  • pull/263294

• Chat input and widget enhancements: Multiple pull requests improve the chat experience by introducing a URL handler for inserting messages into the chat input with user confirmation, modifying the chat sessions view to always display the chat widget entry first with on-demand initialization, rendering chat sessions in two lines for better readability, hiding the "New Chat" button in sessions locked to a coding agent, and fixing context menu behavior in the chat sessions view. These changes enhance usability, discoverability, and maintain consistent UI behavior while adding GDPR-compliant telemetry and fixing submenu z-index issues.
  • pull/263913, pull/263641, pull/263495, pull/264077, pull/263646

• Chat session state and ID stability improvements: These pull requests improve the stability and correctness of chat session management by removing unstable indices from local chat session IDs to ensure uniqueness, refactoring ChatSessionItem state management to prevent invalid states and prepare for additional metadata, and fixing context menu appearance on the "History" node. These changes increase reliability and maintain consistent session behavior.
  • pull/263644, pull/263696, pull/263646

• Terminal sticky scroll command status markers: This pull request adds command status markers such as success, error, and running indicators to the terminal sticky scroll, providing immediate visual feedback consistent with the main terminal view. It also includes hover tooltips and configuration support to improve usability without requiring users to scroll through long command outputs.
  • pull/263296

• Extension version assignment management: This pull request introduces a new filter provider for managing extension version assignments and updates the assignment service to integrate this provider, effectively handling version changes of specific extensions.
  • pull/264012

• Monaco-editor worker esmModuleLocation support: This pull request enables the monaco-editor's createWorker function to accept an esmModuleLocation parameter, which helps avoid origin issues and ensures localization strings are forwarded correctly.
  • pull/264029

• Code transformation improvements for Camel and Pascal case: This pull request improves the transform to Camel and Pascal case actions by maintaining line breaks during multiline selections and adjusting regex to treat only underscores and hyphens as word boundaries. It preserves indentation and correct word separation while keeping single-line behavior unchanged and adds relevant unit tests.
  • pull/263781

• Custom ESLint rule to avoid spread operator: This pull request implements a custom ESLint rule named code-no-spread-operator that warns against using the spread operator in arrays, objects, function calls, and constructors. It promotes performance-optimized alternatives and integrates the rule into the existing ESLint configuration to help developers avoid performance pitfalls.
  • pull/263773

• Clipboard copy fix for SVG images: This pull request addresses intermittent clipboard copy failures for SVG images by introducing a helper function to ensure SVG images are fully loaded before copying. It prevents race conditions and adds error handling with timeout protection while maintaining backward compatibility.
  • pull/263799

• Python command special case handling: This pull request introduces special case handling for Python commands as part of issue #262723 in the Microsoft VSCode project.
  • pull/263844

• Coding agent integration in chat UI: This pull request adds the "Delegate to Coding Agent" action to a new dedicated section in the chat send button's dropdown menu and makes the existing CreateRemoteAgentJobAction available in both the main chat execute toolbar and the secondary dropdown menu. These changes improve user access to coding agent functionality while preserving existing behavior and conditions.
  • pull/263905

• Worktree changes comparison with main repository: This pull request enables users to view and apply changes from a worktree to the main repository on a per-file basis by adding a 'Compare with Workspace' option in the worktree's context menu under 'Changes' that opens the merge editor.
  • pull/263927

• macOS Cmd + Q quit behavior fix: This pull request fixes a macOS-specific bug where pressing Cmd + Q closes all windows but does not fully quit the app, causing it to remain active in the dock and app switcher. The fix ensures the app properly quits on the first Cmd + Q command.
  • pull/263383

• TreeView submenu z-index fix: This pull request fixes issue #263546 by correcting the z-index problem for the submenu of the treeView view/item/context to ensure the submenu appears above other elements.
  • pull/263555

• Disposable resource leak fix in BrowserSocketFactory: This pull request addresses and fixes a disposable resource leak in the BrowserSocketFactory component that caused errors related to unreleased disposables during WebSocket connection handling in the remote extension host agent.
  • pull/263736

• TypeScript CodeLens for overridden implementations: This pull request adds support for displaying "implementations" CodeLens annotations on TypeScript class methods that are overridden in derived classes. It enables developers to see and navigate to these implementations directly from the method definition, aligning CodeLens behavior with the "Find All Implementations" command.
  • pull/263749

• Fetch tool accessibility and table header fixes: This pull request enhances the fetch tool to capture table headers accurately, fixes issue #263128, updates handling of tables without headers by assigning them a layoutTable role in the accessibility tree, and includes corrected unit tests to validate these improvements.
  • pull/263923

• Always copy something fix: This pull request aims to ensure that something is always copied, addressing the possibility that a msal-node-runtime may exist in every package.
  • pull/263936

• Markdown rendering optimization: This pull request optimizes markdown rendering by using the DOM fragment from DOMPurify directly instead of converting it to a string and reparsing it back to the DOM. This avoids unnecessary HTML re-parsing and improves performance.
  • pull/264043

• Coding agent changed files diff indicators fix: This pull request fixes the issue where the coding agent's changed files list was missing green/red diff indicators by removing a blocking condition in the rendering logic, separating diff indicator handling from action bar styling, and adding proper visibility controls. This ensures consistent display of diff indicators regardless of the action bar presence, aligning the coding agent's UI with the regular chat experience.
  • pull/264100

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

Key Closed Pull Requests

1. Enable the broker in macOS: This pull request enables the broker functionality on macOS in the Visual Studio Code project, addressing issue #260158 by implementing necessary code changes, testing, logging, and platform-specific adjustments to support both x64 and arm64 architectures.

• URL: pull/261148

• Merged: 2025-08-27T21:31:09Z

• Associated Commits: 2ff02, 9954d, b814a, a13a6, b31f6, b4d20, 9a9e7, 4d574, 63230, e5791, 4fb6c, 321d4, ae01e, f4ba2, e0d80, b8ea8, c1d7d, 23319

2. rewrite polling function: This pull request rewrites the polling function in the Visual Studio Code project, including multiple commits to fix issues, add conditions, improve tests, and merge updates from the main branch, with the goal of completing and thoroughly testing all code paths.

• URL: pull/262947

• Merged: 2025-08-25T23:47:15Z

• Associated Commits: 60c49, 785b0, 76dc9, 12750, 8359f, 8b8c4, 01ad5, fd8bc, 47ca9, b8dcf, 649c1, eba5e, ffe1b, ab2ff, df5fe

3. detect confirmation prompt patterns for faster response from terminal agent: This pull request refactors the terminal agent in Visual Studio Code to detect confirmation prompt patterns more efficiently, enabling faster responses by implementing and improving heuristics and regex checks for prompts ending with colons and other confirmation indicators.

• URL: pull/263901

• Merged: 2025-08-29T23:06:05Z

• Associated Commits: 34ef6, 74063, fa5d9, 768dd, 1bb12, 5bb66, c137e, 7c814, faa45, 6464c, 22379, 3a587, 5262c, d3244, f3254

Other Closed Pull Requests

• Language Model API Finalization: Multiple pull requests focus on finalizing and improving the Language Model API by completing tasks, fixing leaks, adding unit tests, and refining prompt functionality. These changes ensure the API is robust, well-tested, and user-friendly, supporting ongoing development and integration with Copilot.
• [pull/263415, pull/263161, pull/263625, pull/263161]

• Terminal Improvements and Fixes: Several pull requests address terminal-related issues including fixing memory leaks with terminal link disposables, resolving terminal hang problems with specific SI strategies, improving sticky scroll behavior with debounce, and adding output monitoring for foreground terminals. These fixes enhance terminal stability, performance, and user experience in VS Code.
• [pull/263373, pull/264020, pull/262436, pull/263438]

• Chat Feature Enhancements: Multiple pull requests improve chat session management by supporting all chat session types, adding a "Getting Started" section, enabling prompt file recommendations, and allowing users to disable AI functionality in more areas. These updates increase flexibility, usability, and customization of the chat experience.
• [pull/263453, pull/263868, pull/263369, pull/263479, pull/264000]

• Diff and Workspace Change Features: Pull requests experiment with and add features for viewing diffs and applying changes between worktrees and workspaces, including an "Apply Changes to Workspace" button and improved diff views. These efforts aim to streamline code review and modification workflows, although some were not merged.
• [pull/261390, pull/263335, pull/263514]

• Issue Reporting and GitHub Integration: Enhancements to issue reporting include adding internal filing options with a private URI field and updating GitHub issue creation to respect user-configured external browser settings. These changes improve issue management and user control over external links.
• [pull/263703, pull/263481]

• Window and UI Improvements: Updates to window border handling on Windows and fixes to CSS selector mismatches for hiding confirmation buttons improve the visual consistency and responsiveness of the VS Code interface. These changes enhance the overall user interface experience.
• [pull/261751, pull/263479]

• Authentication and Authorization Updates: A pull request adds support for Microsoft Entra ID v1.0 authorization server endpoints, updating authentication providers and OAuth discovery to maintain backward compatibility and improve tenant extraction. This ensures secure and up-to-date authentication flows.
• [pull/262603]

• Build and Publishing Process Refinements: Refactoring the artifact publishing process with a common template and existence checks fixes issues and standardizes build configurations, improving reliability and maintainability of the build pipeline.
• [pull/263777]

• Playwright MCP and Test Version Locking: Locking Playwright MCP and Playwright Test versions, updating server communication to stdio, and adding logging and prompts improve compatibility and debugging capabilities for testing infrastructure.
• [pull/262229]

• Git Branch Completion Fixes: Fixes to the terminal suggest feature on Windows normalize path separators for git branch names containing slashes by introducing a new completion item kind and updating normalization logic. This ensures accurate and consistent branch name completions.
• [pull/262316]

• Fig Specifications Update: A large update adds many new Fig specifications from upstream sources while removing unsafe scripts and suggesting future improvements to separate code-executing generators from plain text completions for safety. This enhances the Fig integration with safer and broader support.
• [pull/263173]

• MCP Workflow Tooling Adjustments: Initial efforts to disable non-useful tools for the MCP workflow while enabling the multiplexer server and adding documentation improve the developer experience and workflow efficiency.
• [pull/263298]

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
Tyriar	305	19	124	227
Copilot	433	57	0	26
meganrogge	241	18	27	126
bpasero	147	17	68	123
roblourens	56	20	51	163
TylerLeonhardt	103	22	19	117
mjbvz	114	12	19	85
justschen	80	10	4	80
connor4312	36	2	17	114
lramos15	39	3	5	120