Weekly GitHub Report for Vscode: October 06, 2025 - October 13, 2025 (12:00:38)
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.
-
Bad terminal sticky scroll header when
ctrl+l: This issue describes a problem with the terminal's sticky scroll header in VS Code becoming visually corrupted or showing mixed output after using theCtrl+Lshortcut to clear the terminal. Users report that the terminal output gets cut off or overlapped with previous content, and the sticky scroll header behaves unexpectedly, especially after repeated use ofCtrl+LorCtrl+Kcommands in various shell environments.- The comments include requests for more diagnostic information and screenshots, user confirmations of the bug on different platforms, and detailed reproduction steps. Contributors discuss potential causes related to how the terminal handles control sequences triggered by
Ctrl+L, compare behavior between stable and Insiders builds, and consider whether forcing proper newline sequences could resolve the sticky scroll header corruption. - Number of comments this week: 8
- The comments include requests for more diagnostic information and screenshots, user confirmations of the bug on different platforms, and detailed reproduction steps. Contributors discuss potential causes related to how the terminal handles control sequences triggered by
-
Clicking OS notification always opens secondary side bar, even if I'm working with Chat in editor: This issue describes a problem where clicking an OS notification related to Chat in VS Code always opens the secondary side bar, even when the user is actively working with a Chat editor, instead of focusing the relevant chat editor as expected. The user provides detailed steps to reproduce the issue and highlights that the expected behavior is for the chat editor corresponding to the notification to open on the right, rather than the secondary side bar.
- The comments include attempts to reproduce the issue with varying results, identification of the problematic code areas, suggestions for using a specific function to correctly reveal the chat widget, and discussions about challenges in linking confirmation widgets back to their chat widgets to ensure proper focus behavior.
- Number of comments this week: 8
-
Remote MCP server hosted on an internally with a Self-sign certificate no can be started in 105: This issue reports that with the release of VS Code version 1.105.0, users are unable to start a remote MCP server hosted internally on a machine using a self-signed SSL certificate, resulting in a fetch failure error. The problem does not occur in version 1.104.0 or when SSL/TLS verification is disabled, indicating a regression likely caused by an upgrade in the Electron framework and its underlying Chromium security updates.
- Multiple users confirmed the issue affects connections to internal MCP servers with self-signed certificates starting in version 1.105.0, with workarounds including disabling SSL verification or downgrading to 1.104.0. The root cause is suspected to be an Electron upgrade that changed Chromium versions, causing VS Code to ignore the system certificate store despite the certificates being valid and working with tools like curl.
- Number of comments this week: 7
-
froze vs code and copilot stopped working after rebooting vs code: This issue describes a bug where the GitHub Copilot extension in VS Code stopped working and became unresponsive after running a specific NPX command and rebooting VS Code. The user reports that Copilot fails to respond even after restarting, with logs showing multiple validation warnings and summarization request failures related to the MCP tools and Copilot chat features.
- The comments include detailed logs showing initialization steps, multiple schema validation warnings for MCP tools, and repeated summarization failures causing Copilot chat to not respond properly. Users note that starting a new chat acts as a temporary workaround, but the underlying issue with tool validation and summarization errors persists, preventing normal Copilot functionality.
- Number of comments this week: 6
-
vscode doesn't remember collapsed state of
staged changes: This issue reports that in the latest VSCode insiders build, the "Staged changes" section in the source control view does not retain its collapsed state when switching views if a staged file is open in the editor. Specifically, collapsing the staged changes and navigating away then returning causes the section to expand again unexpectedly.- The discussion involved attempts to reproduce the problem, with a request for a screen recording and clarification of reproduction steps, including ensuring a staged file is open in the editor. Suggestions about related settings like
scm.autoRevealandexplorer.autoRevealwere made but found to have no effect on the issue. - Number of comments this week: 6
- The discussion involved attempts to reproduce the problem, with a request for a screen recording and clarification of reproduction steps, including ensuring a staged file is open in the editor. Suggestions about related settings like
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 this functionality to be added or enabled in VS Code so that code cell outputs containing markdown can be recognized and shown in the outline view, enhancing navigation and usability.
- 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 session is disconnected and replaced by the new connection, causing loss of the original window's context.
${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," leading to errors that prevent the terminal process from starting. 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.- 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 does not occur in web browsers like Firefox, indicating a rendering or font support issue specific to VS Code 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: 467
Summarized Issues:
- Performance and Responsiveness Issues: Numerous reports describe severe performance degradation, including freezing, unresponsiveness, and excessive delays in VS Code and its GitHub Copilot extension. These issues manifest during tasks such as auto-formatting, chat summarization, code suggestion generation, search operations, and terminal command execution, significantly impacting user productivity and causing frustration.
- Chat and Copilot Extension Failures: Many issues report the GitHub Copilot Chat extension failing to respond, freezing, or producing incorrect or no output across various platforms and versions. Problems include chat features not loading, indefinite waiting states, failure to provide suggestions, and repeated errors requiring prompt resubmission or extension restarts.
- Agent and Terminal Command Execution Bugs: Several issues describe bugs where AI agents or Copilot extensions fail to correctly execute or detect terminal commands, causing endless loops, failure to capture output, or incorrect command execution. These problems affect both local and remote environments, including SSH and Codespaces, and lead to stalled workflows and user confusion.
- File Editing and Code Modification Failures: Multiple reports indicate that the extension or Copilot fails to apply requested code changes, improperly modifies files, or deletes user work unexpectedly. Users experience missing file edits, corrupted merges, incorrect file overwrites, and inability to revert or update code as intended, causing data loss and workflow disruption.
- Authentication and Connection Problems: Users report issues with authentication flows, including OAuth failures, connection refused errors, and sign-in windows not opening. These problems affect various authentication methods and environments, including Codespaces, remote SSH, and browser-based login flows, preventing proper extension functionality.
- Model Selection and Usage Issues: Several issues highlight problems with AI model selection, including models not appearing as options, incorrect default model persistence, inability to select or switch models, and models producing poor or incorrect outputs. These issues affect user experience and the quality of AI assistance.
- issues/269981, issues/270170, issues/270246, issues/270584, issues/270684, issues/270712, [issues/270745](https://github.com/issues/270745], issues/270764
- UI and Layout Bugs: Users report visual glitches, improper layout behavior, and UI inconsistencies in VS Code and its extensions. Problems include flickering panels, overlapping chat components, missing padding, incorrect icon usage, and broken scroll or focus behavior, which degrade the user interface experience.
- Extension Installation and Signature Verification Failures: There are reports of extension signature verification failures and issues with installing or updating extensions, causing functionality problems and preventing proper extension use.
- Code Suggestion and Autocompletion Problems: Users experience issues with code suggestions being intrusive, premature, incorrect, or failing to trigger properly. Some report unwanted automatic completions, inability to disable suggestions, or suggestions that do not match the context, negatively impacting coding flow.
- Remote Development and Environment Issues: Problems arise with remote SSH, Codespaces, and container environments, including path resolution errors, environment variable leakage, and failure to connect or run commands properly. These issues hinder remote development workflows and integration.
- Data Loss and Critical Bugs: Some users report critical bugs causing data loss, such as unexpected deletion of work or files, and irreversible overwrites during updates or extension operations, leading to significant frustration and disruption.
- Feature Requests and Usability Enhancements: Several requests seek improvements such as better model management UI, enhanced authentication flows, support for additional authentication methods, improved chat session management, and new editor features like bookmarks, image previews, and memory usage tooltips.
- Network and Connectivity Errors: Users encounter network errors such as HTTP/2 protocol errors, network changed errors, and firewall-related issues that prevent the extension from functioning correctly, often requiring network troubleshooting or retries.
- issues/270289, issues/270327, issues/270463, issues/270588, issues/270740, [issues/270600](https://github.com/issues/270600]
- Code Analysis and Syntax Errors: Several issues report incorrect code analysis, syntax errors, or improper handling of language features by the extension or Copilot, including misinterpretation of code lines, incorrect syntax suggestions, and failure to handle special characters properly.
- issues/269954, issues/270320, issues/270845, issues/270886, issues/270900, [issues/270926](https://github.com/issues/270926]
- Miscellaneous Bugs and Issues: Additional problems include keyboard input failures, terminal profile mismatches, extension host CPU spikes, and issues with specific language or file types, all contributing to a degraded development experience.
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: 265
Summarized Issues:
- Extension Marketplace Access and Installation Failures: Multiple issues report problems with searching, accessing, and installing extensions from the VS Code Marketplace, including 404 errors, extensions incorrectly flagged as unavailable, and signature verification failures preventing updates or installs. These problems affect both CLI and UI methods, causing user frustration and blocking extension usage despite extensions existing on the marketplace.
- GitHub Copilot Chat Quota and Subscription Recognition Issues: Several users report receiving "Chat Quota Reached" errors or prompts to upgrade despite having active subscriptions or not using chat prompts, indicating server-side quota tracking or subscription recognition failures. This leads to inability to use Copilot Chat features and repeated erroneous quota messages.
- GitHub Copilot Model Switching and Rate Limiting Problems: Users experience unexpected switching between AI models (e.g., from Grok Code Fast 1 to GPT 4.1o or GPT-4o-mini), resulting in poor code generation quality. Additionally, severe and repeated rate limiting occurs even for paid users, causing interruptions and inability to complete prompts.
- Server Errors and Request Failures in VS Code Extensions: Numerous reports describe server error 500, 502, and 400 errors occurring during requests in VS Code extensions, often accompanied by messages like "Sorry, your request failed. Please try again." These errors affect various features including chat, agent mode, and model requests, causing failures in functionality.
- issues/270105, issues/270073, issues/270237, issues/270256, issues/270494, issues/270575, issues/270576, issues/270571, issues/270766, issues/270728, [issues/270920](https://github.com/issues/270920]
- Extension Signature Verification Failures: Several issues report that extension signature verification fails during activation or update, causing extensions to not install or update properly. This affects multiple extensions including Jupyter and C/C++ build tasks, leading to installation blocks and errors with an 'UnknownError' or similar messages.
- Performance and Responsiveness Issues in Copilot and Chat Features: Users report extremely long response times (10-30 minutes), freezing, unresponsiveness, and slow or broken inline completions in Copilot and chat features. These issues degrade usability and productivity, sometimes requiring workarounds like reloading or restarting VS Code.
- Agent Mode and Tool Call JSON Format Errors: Multiple reports describe failures in agent mode due to invalid JSON format in tool call arguments, resulting in 400 errors and preventing successful operation. These errors cause requests to fail repeatedly and block agent functionality.
- MCP Authentication and Configuration Issues: Issues include failures in MCP authentication due to token invalidation or self-signed certificates, problems with MCP server URI updates, and settings being reset unexpectedly when using MCP commands. These cause connection failures and configuration overwrites.
- Jupyter Notebook and Python Kernel Failures: After VS Code updates, users report Python kernels failing to launch or connect, issues with virtual environments not recognized, and Jupyter notebook edits not applying. These problems prevent running Python code and disrupt notebook workflows.
- Network and Connectivity Errors Affecting VS Code and Extensions: Users experience network errors such as ERR_CONNECTION_RESET, ERR_NETWORK_CHANGED, and firewall-related failures that prevent authentication, extension functionality, and service access, causing paid subscriptions to be unusable.
- Accessibility and UI Bugs in Copilot Chat and VS Code: Problems include screen reader not announcing buttons, chat input becoming unresponsive, mode picker freezing, and UI elements like icons or buttons being hidden or inactive, negatively impacting user experience and accessibility.
- Security Vulnerabilities and Unauthorized Behavior: A critical security vulnerability was reported in an extension that silently installs and escalates privileges without user consent. Additionally, users report unexpected code rewriting and hacking-like behavior in VS Code.
- Feature Requests for Chat and UI Improvements: Requests include support for multiple independent chat threads, a pause/intervene button in Copilot Chat, SVG code completion, window transparency, larger Copilot UI, and customizable commit message prompts to improve productivity and user control.
- Model-Specific Bugs and Failures in AI Extensions: Specific AI models like Claude Sonnet 4 and Gemini Pro 2.5 exhibit failures such as server errors, infinite file generation, failure to follow instructions, and schema validation errors causing 400 responses, disrupting AI-assisted coding workflows.
- VS Code Terminal and Shell Environment Issues: Problems include Copilot terminals not loading the same shell profile as normal terminals, environment variables not being available in tasks, and terminal output disappearing intermittently, causing workflow disruptions.
- Miscellaneous Bugs Affecting File and Workspace Management: Issues include files created in wrong directories, import paths not updating after file moves, inability to remotely index workspaces without cloning, and folder names conflicting with file paths causing explorer display problems.
- User Frustration and Complaints About AI Quality and Censorship: Multiple users express strong dissatisfaction with GitHub Copilot's AI quality, censorship policies, and overall experience, describing it as buggy, unintelligent, and a waste of resources, with some switching to competing services.
- Telemetry and Diagnostic Enhancements Requested: A request was made to add telemetry to better measure tool invocation times within VS Code core, aiming to improve performance tracking beyond current extension-level metadata.
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.75 (Rapid escalation, aggressive language, user frustration)
- This GitHub conversation begins with a bot providing a polite and neutral suggestion to upgrade software, followed by a user named MUJAHID SCIENCES ELECTRONICS MUJAHID SOFTWARE responding with frustration and aggressive language, criticizing the bot's response as unhelpful and overly verbose. The tone shifts from neutral to hostile, triggered by the user's dissatisfaction with the initial automated reply.
-
- Toxicity Score: 0.75 (Rapid escalation, dismissive language, frustration)
- This GitHub conversation involves two users exchanging increasingly frustrated and dismissive comments, with one user expressing strong dissatisfaction and the other responding with skepticism and finality. The tone is negative and confrontational, with tension triggered by perceived incompetence and unproductive engagement.
-
- Toxicity Score: 0.75 (Aggressive language, explicit profanity, potential for escalation)
- This GitHub conversation involves a user posting a highly aggressive and profane issue report, which triggers a response from another user expressing surprise at the nature of the initial comment. The tone is initially hostile due to the original post, but the reply attempts to acknowledge the unexpectedness of the situation without escalating tension. Given the explicit language and potential for further negative exchanges, the likelihood of toxicity in future comments is elevated.
-
annoying copilot microsoft censorship
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, personal insults, explicit profanity)
- This GitHub conversation consists of a single user expressing strong frustration and anger towards a feature, using highly offensive language and personal insults. The tone is aggressive and confrontational, with no responses or attempts at resolution visible. The initial post's intensity and explicit language suggest a high potential for further toxic interactions if the conversation continues.
-
You suck microsoft and your lousy copilot!
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, explicit profanity)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger towards a product, using explicit language and demanding a specific type of interaction. There are no responses or further comments to indicate any change in tone or sentiment. The tone is highly emotional and confrontational from the outset, with no signs of de-escalation or resolution.
-
annoying copilot microsoft censorship
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, explicit profanity, one-sided negativity)
- This GitHub conversation features a single user expressing strong frustration and anger towards a product's censorship policies, using explicit language and a confrontational tone. There are no other participants or responses, so the conversation remains one-sided with no de-escalation or moderation. The user's sentiment is highly negative and emotionally charged, indicating potential for conflict if others were to engage.
-
schema validation issue (title property missing)
- Toxicity Score: 0.75 (Rapid escalation, aggressive language)
- This GitHub conversation involves a single user expressing frustration with a terse and aggressive comment, indicating a negative sentiment and a confrontational tone triggered by a technical issue.
-
- Toxicity Score: 0.95 (Rapid escalation, aggressive language, repeated offensive content)
- This GitHub conversation consists solely of repeated comments by a single user expressing intense frustration and anger towards the platform and its AI features, using highly offensive and aggressive language. The tone is hostile and derogatory, with no engagement or responses from other users, indicating a one-sided venting rather than a dialogue. The repeated posting of identical toxic messages suggests a high potential for continued toxicity if the conversation persists.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms, one-sided hostility)
- This GitHub conversation consists of a single initial comment by one user expressing intense frustration and anger towards the platform and its AI features, using highly offensive language and derogatory terms. There are no responses or interactions from other users, so the tone remains one-sided and hostile without any de-escalation or moderation. The trigger of tension is the user's dissatisfaction with the AI's performance and the platform's impact on their time and resources.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single user expressing strong frustration and dissatisfaction with the product's performance, using harsh language and a dismissive tone without any responses or further discussion.
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: 36
Key Open Pull Requests
1. Use actual configuration for policy export: This pull request introduces a new workflow to validate the policy export process, refactors the existing policy export script into a VS Code service with unit tests triggered by a Workbench contribution, and updates the IPolicy interface to support localization keys, resulting in alphabetically sorted policies and improved enum parsing based on actual configuration data.
- URL: pull/270283
- Merged: No
- Associated Commits: eb2a7, c7588, 662df, c4cb9, 23012, 44920, 2e356, 4b5ca, 22197, 0f0ed, 50094, 1932d, b9b36, 79753, 45ee1, ffeda, 87d34, 6fcc4, 7c7dd, b9c0f, a80da, ce9e4, 16542, 31a1b, 49f1f, 814c1, 630c5, f7371, d98c3, e504d, ee4ea, f8adc, a5bc0, 0763c, 8ab16, 4c5fd, f0247, e81b1, 657f5, bfa58, 72b51, 7fa12, e1518, 5ba98, 3a555, 1996d, 97914, 6606e, 403df, 0f7cc, 3d470, ba150, fab87, b20eb, 0139e
2. wip terminal inline chat: This pull request introduces a work-in-progress feature for inline chat within the terminal of Visual Studio Code, addressing merge conflicts from a previous related pull request and including tasks such as properly disposing of UI parts and incorporating feedback from comments.
- URL: pull/270821
- Merged: No
3. Refactor Issue Reporter into EditorPane: This pull request aims to refactor the Issue Reporter feature into an EditorPane within the VSCode project, involving work-in-progress commits focused on loading HTML content, improving editor functions, fixing UI button duplication, and restructuring for better maintainability.
- URL: pull/270643
- Merged: No
Other Open Pull Requests
- Chat interface improvements: Multiple pull requests enhance the chat experience by disabling the send button and preventing new lines on empty input, adding a new
/investigatecommand for GitHub issue notes, fixing empty names in chat session history, and separating inline notebook chat settings for version 2. These changes improve usability, provide new functionality, and fix bugs related to chat session management.
[pull/270117, pull/270274, pull/270592, pull/270658]
- Notebook testing and stability: Several pull requests focus on notebook smoke tests by re-enabling previously skipped tests, adding repeated runs for stability, and creating independent settings for inline notebook chat. These efforts aim to investigate timeouts, memory leaks, and improve feature isolation in notebook components.
[pull/270298, pull/270658, pull/270796]
- Editor navigation and search fixes: Pull requests introduce a new cursorMove argument to avoid cluttering navigation history, add support for absolute character offset navigation, and fix search issues with special characters in filenames. These updates enhance navigation precision and search reliability within the editor.
[pull/270385, pull/270625, pull/270844]
- Find widget and color settings corrections: A pull request fixes swapped color settings for
editor.findMatchForegroundandeditor.findMatchHighlightForegroundto ensure correct display of search matches. Another removes deprecated hoverDelegate usage across components, improving lifecycle support and context toggling. These changes improve UI consistency and codebase modernization.
[pull/270395, pull/270749]
- Dependency and build updates: Updates include upgrading dompurify and related type packages, as well as updating TypeScript versions used for building VS Code, which required fixing compatibility issues and suppressing build errors. These ensure the project uses current dependencies and build tools.
[pull/270041, pull/270054]
- Proxy and network handling fixes: A pull request addresses a regression from an Electron update by treating missing proxy authentication indicators as first attempts, preventing repeated credential prompts. Another implements a close transport message for streamable HTTP in the MCP component to fix a related issue. These improve network reliability and user experience.
[pull/270025, pull/270433]
- Diagnostics and commit hook improvements: One pull request fixes a pre-commit diagnostics hook that incorrectly blocked commits due to stale data by adding a delay before checking diagnostics, preventing false positives when files are quickly fixed and staged. This enhances the accuracy of commit validations.
[pull/270039]
- UI customization and accessibility: A pull request adds two new settings for independently adjusting font sizes of primary and secondary sidebars, enabling dynamic scaling without UI reloads or theme changes. This improves accessibility and user customization options.
[pull/270851]
- Terminal and suggest addon fixes: A fix ensures the terminal suggest addon correctly multiplies line heights according to its configuration, differentiating it from the editor suggest line heights and resolving a specific issue. This improves terminal UI consistency.
[pull/270827]
- Debugger session handling: A pull request modifies debugger REPL evaluation logic to prioritize stopped or running child sessions over the parent session after switching debug console sessions, preventing unresponsiveness. This ensures smoother debugging workflows.
[pull/270461]
- Language configuration enhancements: A new
textDirectionfield is added to languageConfiguration to support right-to-left languages alongside left-to-right, addressing internationalization needs.
[pull/270580]
- Miscellaneous fixes and additions: Other changes include adding a new HTML file
ase_canvas.html, fixing quote parsing in subCommands.ts for command inputs, and preventing flickering when opening webviews by hiding empty message divs before layout. These address various minor bugs and UI improvements.
[pull/270467, pull/270202, pull/270777]
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: 203
Key Closed Pull Requests
1. New console: This pull request proposes the development of a new console feature in the VSCode project, including backend services, runtime session management, integration of Python and R support, UI components for sessions and plots, code cells, data explorer enhancements, and various fixes and improvements, but it was ultimately not merged.
- URL: pull/270037
- Merged: No
- Associated Commits: c0d83, 25a6c, 40c52, d3bb0, 5ae41, eadfd, f93a2, 75aba, 064a1, 41638, 9b6a7, 2c628, b86df, 42de0, e25c7, 7a9e8, 079ea, da7c1, f8dbc, fa11c, f0bf7, 10258, ceb65, 1513c, a00ae, a9d44, 1fb60, 01782, 5f7a2, 28f8e, 4d50b, 4bda4, 7ebac, ce87d, 98beb, 0ec68, a1b89, a835b, 5845d, 30753, 133bc, 1b24d, a9f3e, 8d279, edcfa, 2fae7, f18c0, 54ab0, 092cb, 8f4e2, 5e44c, 2da3a, 8041c, 91458, 029a0, 5655a, cd183, 33daf, 497d8, 4ba59, f8e74, 19778, 5d8fb, cf96a, 9d806, 9ba9c, 3e74e, 42b52, a52db, 021e6, d59f4, aca59, 0b316, bfef6, c5a75, 0810a, d661f, fc156, 6af89, bc639, c3286, c6255, d8826, 28c01, 40884, 6f6ae, 80a3e, 0aa2f, 46865, ece7e, 76386, 6924e, 6bffb, ac296, 6dbdd, 59a70, 53f39, c21a8, 4e548, 1f3cf, 2b992, 4d2ee, 481e9, 62e83, 6f169, e1760, ea6f3, 6e47d, 4027c, 68b29, 636e2, d8978, 331cf, 52592, 591d9, 6d019, cc740, 734aa, 9e0b6, 52d9f, 12526, 867f4, 62a70, bc8ed, 375d0, 6ee26
2. Add setting to turn off "Ask GitHub Copilot" option in command palette: This pull request adds a new setting to Visual Studio Code that allows users to disable the "Ask GitHub Copilot" option in the command palette, addressing issue #195023.
- URL: pull/270458
- Merged: Yes
- Associated Commits: 3b21d, db4a7, 18796, d2a68, 1c0a8, 02543, e6a68, 9c5d1, f2d8d, 58af0, 994d2, a7360, 96d67, 53e2a, 5f702, 16275
3. Make ICommandHandler default to ...args: unknown[]: This pull request updates the ICommandHandler interface to default its parameters to ...args: unknown[] to handle cases where command definitions lack specified parameter types, and modifies registerCommand to prevent errors for handlers with explicit types, addressing related type errors in the codebase.
- URL: pull/270134
- Merged: Yes
- Associated Commits: 856f1, fdb77, 117e9, 6e5e3, 80c4d, 8989d, 809fe, 00489, 3cd59, 4538d, f1c67, 26134, 15f50
Other Closed Pull Requests
- Terminal and Shell Enhancements: Multiple pull requests improve terminal functionality by adding support for terminal completion providers with descriptive metadata, fixing environment variable issues in agent-created zsh terminals, and correcting terminal tool input suggestions to avoid ambiguous prompts. These changes enhance user experience and reliability in terminal interactions within VS Code.
pull/270597, pull/270605, pull/270351
- Event Handling and Capability Improvements: Pull requests introduce capability type narrowing, generic access, and a command detection event while removing specific capability type events, alongside adding unit tests and improving event handling with memoization and lazy evaluation. These updates address issue #269213 and improve the robustness of event management in VS Code.
pull/270149
- Testing and Build Fixes: Several pull requests focus on fixing failed tests by removing disabled servers, improving test coverage for extensionMCPDiscovery, and correcting test errors to ensure successful builds. These efforts maintain build stability and test reliability.
pull/270704
- Managed Trusted Extensions UI Improvements: A pull request adds a button to the Managed Trusted Extensions picker that allows users to view detailed extension information, addressing issue #204876 and enhancing user control over trusted extensions.
pull/270450
- QuickPick Component Enhancements: A pull request adds prompt support to the QuickPick component, including refinements, suggestion fixes, and build break resolutions, addressing issue #78335 and improving the component's usability.
pull/270497
- MCP Authentication and Metadata Handling: Improvements to MCP authentication include refactoring metadata fetching to handle non-JSON responses robustly, implementing a helper function for JSON parsing with early returns, and ensuring all metadata URLs are checked before fallback. These changes enhance reliability and code clarity.
pull/270579
- Icon and Design Updates: The codicon library is refreshed by updating font files and adding new icons aligned with the Fluent design language, aiming to gather feedback for future fine-tuning of the icon set.
pull/270350
- Accessibility Enhancements: Accessibility on macOS is improved by adding support for an accessible view of problem markers in the editor’s marker navigation widget, enabling screen reader users to access detailed problem information via a new editor action triggered by Alt+F2.
pull/270598
- TypeScript Type Safety Improvements: Multiple pull requests reduce the usage of the
anytype and update type definitions in tree model classes to allow nullable types and enhance type safety, contributing to better maintainability and code quality.
pull/270100, pull/270139, pull/270193
- Codebase Modernization: A pull request removes references to old versions and updates the codebase to adopt the latest versions, ensuring compatibility and modernization.
pull/270153
- Launch Configuration Validation: Comprehensive validation is added for the
serverReadyAction.patternregex field in launch.json, including JSON schema validation, Settings UI validation with immediate feedback, and runtime error handling to prevent debug session failures.
pull/270244
- Command and Search Usability: The commands picker is improved by removing character accents from search inputs to enable accent-insensitive filtering, enhancing search accuracy and usability.
pull/270248
- Notebook Find Widget Fixes: Fixes enable F3 and Shift+F3 keys to properly navigate search results within notebooks, restoring functionality and improving multi-command support for the find feature.
pull/270303
- Editor Build Configuration Consolidation: Editor compile settings are consolidated by sourcing all target and environment configurations from
tsconfig.monaco.json, eliminating overrides instandalone.jsand ensuring consistency.
pull/270116
- MCP Prompt Input Bug Fix: A bug fix prevents reuse of suggestion values across different argument fields in the MCP prompt input by adding a flag to clear active selections, ensuring each field starts clean.
pull/270229
- Inline Editing for Todo List Titles: Inline editing is added for todo list titles with a hover-activated pencil icon, keyboard accessibility, ARIA attributes, auto-save on blur or Enter, cancel on Escape, and corresponding CSS and tests for a user-friendly experience.
pull/270255
- Issue #270285 Candidate Fix: A candidate fix for issue #270285 includes multiple commits aimed at improving and refining the solution before merging.
pull/270351
- Notebook Text Model Logging: A logging service is introduced to the notebook text model to trace and record edit activity, assisting in troubleshooting issue #268797.
pull/270786
- PEP8 Style Preliminary Optimizations: Preliminary PEP8 style optimizations are made, primarily updating and adding to the README.md file, though this pull request was not merged.
pull/269936
- Rerun Task Fix for npm in Monorepos: The "Rerun Task" feature is fixed for npm tasks in monorepos by extending task lookup logic to include contributed tasks with additional identifying properties, ensuring correct task restart.
pull/270080
- OAuth and Extension Host API Updates: Updates to OAuth-related code and extension host API files address feedback from a previous submission to improve functionality and maintain code quality.
pull/270106
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 | 289 | 60 | 0 | 282 |
| meganrogge | 149 | 15 | 30 | 154 |
| bpasero | 137 | 15 | 43 | 74 |
| mjbvz | 92 | 34 | 26 | 54 |
| roblourens | 29 | 13 | 35 | 121 |
| TylerLeonhardt | 35 | 10 | 24 | 129 |
| lszomoru | 136 | 10 | 6 | 24 |
| sandy081 | 47 | 11 | 10 | 73 |
| connor4312 | 58 | 9 | 10 | 57 |
| Tyriar | 48 | 15 | 26 | 30 |
Don't miss what's next. Subscribe to Weekly Project News: