Weekly GitHub Report for Vscode: November 10, 2025 - November 17, 2025 (12:00:51)
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.
-
Extension host terminating on macOS with v1.106: This issue reports that on macOS with VS Code version 1.106, the extension host crashes immediately upon startup with the error "Extension host terminated unexpectedly 3 times within the last 5 minutes." The problem appears related to a native crash triggered when Node.js attempts to obtain system CA certificates, and users have found a temporary workaround by disabling this behavior via the
"http.systemCertificatesNode": falsesetting.- Multiple users confirmed the crash occurs on macOS (and possibly Windows) after updating to version 1.106, with extensive troubleshooting including reinstalling VS Code and clearing extensions failing to resolve it. Crash dumps revealed the issue stems from Node.js certificate handling, and setting
"http.systemCertificatesNode": falsesuccessfully prevents the crash, though the root cause is linked to a recent code change involving system certificate parsing; the setting has since been disabled in A/B testing to mitigate the problem. - Number of comments this week: 18
- Multiple users confirmed the crash occurs on macOS (and possibly Windows) after updating to version 1.106, with extensive troubleshooting including reinstalling VS Code and clearing extensions failing to resolve it. Crash dumps revealed the issue stems from Node.js certificate handling, and setting
-
Extension Signature Verification Failed: GitHub Copilot Chat: This issue reports a bug where the GitHub Copilot Chat extension fails signature verification during installation, particularly affecting setups using WSL with Guix. Users also experience related problems such as extension host crashes, disabled GitHub login, and incompatibility errors with certain API proposals after updating VS Code to version 1.106.0.
- The comments reveal that while the original issue concerns signature verification failures on Windows with VS Code 1.105.1, several users report a similar but distinct problem after upgrading to VS Code 1.106.0 on macOS, involving API incompatibilities causing extension host crashes and login failures; users suggest these are separate issues and recommend filing distinct bug reports.
- Number of comments this week: 9
-
Incorrect warning "The model wants to edit files outside of your workspace": This issue reports an incorrect warning message in the Copilot Chat extension for VS Code, where the user is prompted that the model wants to edit files outside of their workspace, even though the files are clearly within the workspace folder. The user provides environment details and reproduction steps, and the discussion in the comments investigates whether the workspace is symlinked and verifies the real paths of the workspace and files to confirm the paths match.
- Multiple users confirm experiencing the same warning on different operating systems. The discussion rules out symlinked folders as the cause by checking real paths, which are consistent with the workspace location. The issue remains unresolved but is clearly identified as a false positive warning about file locations.
- Number of comments this week: 7
-
Issue with Terminal Commands Not Being Executed in Copilot Chat: This issue describes a problem where terminal commands fail to execute when using GitHub Copilot Chat accessed through a VS Code tunnel, despite the ability to edit and inspect files. The user reports that the GitHub Pull Request extension never activates, repeatedly showing warnings that its API is unavailable, which appears to block terminal command execution and pull-request workflows in this remote setup.
- The discussion involved requests for additional environment details, screenshots, and logs to diagnose the problem. The user provided detailed system information and evidence showing the extension failing to activate and terminal commands not running, while attempts to reload, restart, and verify CLI functionality via direct SSH did not resolve the issue.
- Number of comments this week: 7
-
Allow changing default GitHub Copilot model for all users of an organization: This issue requests the ability to set a default GitHub Copilot model for all users within an organization, aiming to improve onboarding by ensuring everyone uses a premium model by default rather than the less effective 'auto' mode. The user highlights that many developers struggle with Copilot because they unknowingly use non-premium models, and switching to models like Claude Sonnet 4.5 significantly enhances their experience and productivity.
- The discussion acknowledges the feature request but places it in the backlog pending further feedback. Commenters express frustration with the 'auto' mode reverting unexpectedly and prefer consistent use of premium models, while maintainers seek clarification on the reported bug and usage scenarios, with some investigation ongoing to reproduce the issue.
- Number of comments this week: 6
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 rendered in the output of code cells. The requester highlights that this functionality would allow outlines to include dynamically generated content from code cells, improving usability by reflecting changes made through code rather than only static markdown cells.
- 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," causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}works correctly when the task type is "shell" with PowerShell as the default shell, it produces malformed paths in other contexts, and that using${env:USERPROFILE}serves as a functional workaround.- 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, preventing immediate 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 pasted into Visual Studio Code, it is incorrectly rendered as a question mark instead of displaying the correct symbol. The problem occurs on Fedora 39 with VS Code version 1.87.2, and the character displays properly in other applications like Firefox, indicating a rendering bug specific to VS Code.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 584
Summarized Issues:
- Extension Unresponsiveness and No Response Issues: Multiple reports indicate that various versions of the VS Code extension (notably 0.32.4, 0.32.5, 0.33.0, and 0.33.1) frequently become unresponsive or fail to return any response during use on Windows 10, macOS, and Linux systems. Users experience symptoms such as the extension being stuck on "Working," showing error messages like "Sorry, no response was returned," or the chat window freezing and not updating, severely disrupting workflows and causing frustration.
- issues/276374, issues/276375, issues/276377, issues/276385, issues/276390, issues/276396, issues/276401, issues/276410, issues/276418, issues/276618, issues/276621, issues/276624, issues/276678, issues/276687, issues/276688, issues/276849, issues/276922, issues/276928, issues/276932, issues/276953, issues/277346, issues/277372, issues/277410, issues/277429, issues/277539
- GitHub Copilot and Chat Feature Failures: Numerous issues report that GitHub Copilot and Copilot Chat extensions fail to function correctly across various platforms and VS Code versions. Problems include failure to sign in, chat windows not appearing or freezing, incorrect or incomplete code suggestions, persistent 400 errors, and inability to use premium features despite payment. These failures often cause significant disruption to user productivity and trust in the tool.
- issues/276394, issues/276431, issues/276494, issues/276525, issues/276593, issues/276596, issues/276624, issues/276638, issues/276639, issues/276690, issues/276693, issues/276700, issues/276707, issues/276730, issues/276733, issues/276745, issues/276749, issues/276900, issues/276910, issues/276918, issues/277053, issues/277074, issues/277183, issues/277201, issues/277214, issues/277257, issues/277280, issues/277335, issues/277370, issues/277381, issues/277384, issues/277405, issues/277421, issues/277426, issues/277427, issues/277528, issues/277637, issues/277643, issues/277644, issues/277645, issues/277652
- Performance and Resource Usage Problems: Several issues highlight severe performance degradation in VS Code and its extensions, including high CPU and memory usage, freezing, slow responses, and unresponsiveness during normal operations or specific tasks like code completion, chat interactions, or running tests. These problems occur on multiple platforms and hardware configurations, often rendering the application unusable or causing significant delays.
- Network and Authorization Errors: Users report frequent network-related errors such as ERR_HTTP2_PROTOCOL_ERROR, ERR_CERT_COMMON_NAME_INVALID, ERR_CONNECTION_RESET, 400 and 403 HTTP errors, and authorization failures affecting extension functionality, sign-in processes, and API requests. These issues often relate to firewall settings, proxy configurations, or certificate problems, causing disruptions in normal operation.
- Code Modification and Edit Application Failures: Multiple issues describe situations where the agent or extension indicates that code changes or file edits have been made, but no actual modifications occur in the files. This includes problems with edit pills showing combined diffs incorrectly, files being deleted unexpectedly, or changes not being applied despite confirmation messages, leading to confusion and loss of trust in the tool's reliability.
- UI and Visual Bugs: Several reports highlight UI inconsistencies and visual bugs such as misaligned paddings and margins, flickering chat views, invisible indentation guides, clipped confirmation dialogs, and broken or missing UI elements like model selectors or chat windows. These issues degrade the user experience and can cause confusion or hinder usability.
- Sign-In and Authentication Problems: Users frequently encounter issues signing into GitHub Copilot or related services within VS Code, including missing browser windows for authentication, repeated sign-in prompts, and persistent login errors despite correct credentials and network connectivity. These problems prevent access to key features and cause user frustration.
- Model Selection and Configuration Issues: Several issues report missing or broken model selection dropdowns, inability to set default models, unexpected model switching behavior, and requests for more flexible model configuration options. These problems limit user control over AI model usage and can lead to suboptimal or confusing experiences.
- Memory Leaks and Promise Accumulation: Reports indicate memory leaks in VS Code related to unresolved promises accumulating during notebook scrolling, terminal creation and deletion, and text duplication and deletion, leading to increased resource consumption and potential performance degradation over time.
- Agent and Tool Integration Bugs: Issues include agents entering infinite loops, refusing to use enabled tools, incorrectly flagging valid YAML as errors, and problems with tool confirmation editors and delegation workflows. These bugs disrupt the expected AI-assisted workflows and cause user confusion or wasted resources.
- Feature Requests for Improved Usability and Functionality: Users request enhancements such as standardized UI bug report templates, support for new AI models, improved chat export options, better model and tool configuration interfaces, inline refactoring support, and more intuitive UI elements like run-to-cursor icons and multi-line status bars to improve overall user experience and productivity.
- Crash and Stability Issues: Several reports describe crashes of VS Code or its extension host triggered by specific actions such as opening files, using certain extensions, or during startup, often requiring workarounds or disabling features to regain stability.
- Localization and Accessibility Concerns: Some issues highlight problems with localization such as untranslated strings, incorrect text direction for RTL languages, and accessibility issues like screen readers not announcing dialogs or keyboard shortcuts not working as expected, impacting usability for diverse user groups.
- Miscellaneous Bugs and User Experience Problems: Additional issues include problems with keyboard shortcuts, terminal behavior, file drag-and-drop, and unexpected UI behaviors such as persistent undo UI or incorrect git blame decorations, all contributing to a less smooth user 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: 333
Summarized Issues:
- Agent and Model Identification Issues: Several reports indicate that the Claude Sonnet 4.5 agent and related AI models incorrectly identify themselves as older versions (e.g., Claude 3.5 Sonnet), causing user confusion and bug reports. Additionally, the agent sometimes hangs or becomes stuck waiting indefinitely during command execution or git operations, leading to stalled workflows and requiring manual intervention.
- Terminal Command Execution and Interaction Bugs: Multiple issues report that GitHub Copilot and AI agents fail to correctly handle terminal commands, including omitting the first letter of commands, failing to detect terminal state, merging command histories across terminals, and terminal output being blank or cut off. These bugs cause commands to be entered incorrectly, indefinite waiting, and loss of terminal session context.
- Performance and Responsiveness Problems: Users frequently experience slow or unresponsive behavior in VS Code extensions, including long delays in summarizing conversation history, repeated "Sorry, no response was returned" errors, and severe performance degradation after updates or plan upgrades. These issues affect multiple platforms and extension versions, causing frustration and loss of productivity.
- Quota, Rate Limiting, and Subscription Access Issues: Several reports highlight problems with quota resets not occurring as expected, users being incorrectly rate limited despite having active Pro subscriptions, and extensions showing messages about reaching monthly chat message limits erroneously. These issues cause confusion and restrict access to paid features.
- Request Failures Due to Invalid JSON or Attachment Issues: Numerous bugs report requests failing with 400 errors caused by invalid JSON format in tool call arguments or inaccessible attachments, leading to failed operations and error messages like "vision_attachment_not_accessible." These failures occur across various extension versions and platforms, disrupting normal usage.
- Chat History and Session Persistence Problems: Users report that chat histories do not save or persist correctly, with TODO tasks leaking between sessions and resumed chats losing context, causing loss of conversation continuity and user frustration.
- Extension Host and Crash Issues: Several reports describe the VS Code extension host or the entire application crashing or becoming unresponsive, sometimes linked to specific extension versions or system configurations, causing loss of work and requiring restarts.
- User Interface and Usability Bugs: Problems include the Up Arrow key in Agent mode deleting unsubmitted messages without recovery, suggestion overlays blocking views, missing or hidden UI buttons (e.g., commit button, terminal tabs), and cluttered context menus, all negatively impacting user experience.
- issues/276373, issues/276711, issues/277409, issues/277174, issues/276841, [issues/277317](https://github.com/issues/277317]
- Security Vulnerabilities and Data Exposure: A critical remote code execution vulnerability was found where prompt injection in agent mode could bypass file editing guards to modify sensitive files, which was fixed by validating file paths. Additionally, accidental exposure of sensitive data in public repositories was reported.
- Model and Feature Functionality Failures: GPT-5 and other advanced models sometimes fail to respond or cut off mid-response, and features like "plan mode" disappear after updates. The Copilot extension also sometimes generates destructive or nonsensical code, reducing trust and usability.
- issues/276386, issues/276432, issues/276456, issues/276481, issues/276780, issues/277178, [issues/277616](https://github.com/issues/277616], issues/277491, issues/277627
- Rate Limiting and Token Expiry Errors: Users encounter frequent rate limiting and token expiration errors (403), causing failed requests and interruptions in service despite active subscriptions, leading to repeated error messages and blocked usage.
- issues/277039, issues/277159, issues/276936, issues/277891, [issues/277916](https://github.com/issues/276916]
- File and Code Corruption Issues: Bugs include corrupted files due to overlapping replacements, incomplete or truncated code snippets, and destructive behavior by the Copilot extension, causing loss of code integrity and user trust.
- issues/276705, issues/277113, issues/277154, issues/277146, [issues/277639](https://github.com/issues/277639]
- Authentication and Account Management Problems: Users report repeated logouts from Microsoft Account Authentication, issues with GitHub sign-in for Copilot, and incorrect subscription status displays, complicating access and usage.
- issues/276522, issues/276527, issues/276692, [issues/277098](https://github.com/issues/277098]
- Miscellaneous Bugs and Feature Requests: Other issues include requests for keyboard shortcuts, UI improvements like nested peek windows, manual file reordering, and better error message handling, as well as bugs in syntax highlighting, terminal suggestions, and extension installation.
- issues/276460, issues/276466, issues/276520, issues/276512, issues/276579, [issues/276647](https://github.com/issues/276647], issues/277443, issues/277470
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 potential, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by one user expressing extreme frustration and anger about a performance issue, using aggressive and profane language. There are no responses or further comments, so the tone remains highly negative but unchallenged. The lack of interaction leaves the situation unresolved, with potential for escalation if others respond.
-
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, explicit frustration)
- This GitHub conversation involves a single user expressing strong dissatisfaction with a tool, using explicit language to convey frustration. The tone is negative and blunt, with no responses or further discussion visible to moderate or escalate the sentiment. The lack of engagement suggests a stagnant conversation with potential for increased negativity if others respond defensively or dismissively.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, lack of moderation)
- This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment with aggressive and repetitive language, without any responses or further interaction. The tone is highly confrontational and dismissive, but no dialogue or escalation occurs due to the absence of replies.
-
- Toxicity Score: 0.65 (Rapid escalation, dismissive response, potential trolling)
- This GitHub conversation involves a user expressing personal difficulty and frustration in understanding a concept due to platform limitations, using a lighthearted and self-deprecating tone. Another participant responds with a brief, dismissive comment that could be interpreted as spam or trolling, potentially escalating tension. The interaction shows a contrast between a vulnerable expression and a curt, possibly antagonistic reply, which may trigger further negative exchanges.
-
- Toxicity Score: 0.55 (Moderate possibility, escalating frustration, dismissive responses)
- This GitHub conversation involves a user expressing dissatisfaction with the service and another user responding with frustration, indicating a breakdown in communication and mutual understanding. The tone is increasingly confrontational, with both parties showing signs of impatience and dissatisfaction, triggered by perceived neglect and unmet expectations.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive slurs)
- This GitHub conversation involves a user posting a highly offensive and aggressive issue report, followed by a bot responding with a standard, neutral message suggesting an update. The initial comment sets a hostile and toxic tone, but the bot's reply is calm and procedural, without escalation. There is no evidence of further human interaction or de-escalation attempts.
-
You guys are really stupid. Why did you hide the quick icon for the Git commit panel?”
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, insulting tone)
- This GitHub conversation begins with a single user posting a highly critical and insulting comment directed at the development team, expressing strong dissatisfaction in a confrontational tone. There are no subsequent comments or responses, so the conversation remains one-sided with a negative sentiment. The initial post's aggressive language and direct insults create a tense atmosphere, but without further interaction, the conversation does not escalate.
-
- Toxicity Score: 0.65 (Rapid escalation, accusatory tone, user frustration)
- This GitHub conversation involves a user expressing significant frustration and confusion regarding an upgrade process and billing issues, with a tone that is urgent and somewhat accusatory. The initial comment sets a tense atmosphere by highlighting dissatisfaction and perceived malfunction, which may provoke defensive or clarifying responses from maintainers or other users. The sentiment is predominantly negative, and the language used suggests a high level of user distress, potentially escalating tensions if responses are not empathetic or clear.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, repeated accusations, one-sided negativity)
- This GitHub conversation consists solely of repeated comments from the same user expressing intense frustration and dissatisfaction with a software feature, using accusatory and emotionally charged language. The tone is highly negative and confrontational, with no engagement or responses from other participants, indicating a one-sided venting rather than a dialogue. The repetition of identical comments suggests escalating agitation and a lack of constructive 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: 66
Key Open Pull Requests
1. Align tool names and add support for legacy reference identification: This pull request aims to unify tool names within the project by introducing a system that supports deprecating old names while maintaining backwards compatibility, thereby enabling extension authors to adopt similar capabilities.
- URL: pull/277047
- Merged: No
- Associated Commits: 21666, 4e9bc, eaeec, 24d4a, eaa81, 9f9aa, ec337, 16eef, b2e36, 4accf, 296e5, 5be16, 6f673, d675b, e48cb, cdddb
2. Insider builds should have an auto increasing version number: This pull request proposes implementing an automatic version number incrementing system for Insider builds in the Visual Studio Code project to ensure each build has a unique, sequential version identifier.
- URL: pull/277497
- Merged: No
- Associated Commits: 4e815, 97db8, 23c5e, a32a5, 527ce, 0e1b4, f7c06, 082f7, 57b27, edf65, 7cb22, 317bd, 0f159
3. Run our build scripts directly as typescript: This pull request updates the project's build scripts to run directly as TypeScript by converting files to ES modules, replacing Node.js-specific patterns like __dirname with import.meta, enabling syntax-only mode for TypeScript files, updating script references to use .ts extensions, and removing all checked-in compiled JavaScript files to streamline future script conversions and improve build management.
- URL: pull/277567
- Merged: No
- Associated Commits: 54999, aa3c1, 639e5, 9e03b, dcc9e, 4d885, b724b, 31f73, d6728, eef7e, fdba5, b13a3
Other Open Pull Requests
- Node.js and npm version enforcement: This pull request adds an "engines" field to the root package.json to specify minimum required versions of Node.js (>=18.0.0) and npm (>=9.0.0), ensuring users and contributors are warned if their environment does not meet these requirements. This change addresses issue #252372 to improve environment consistency.
- Diff mode stdin argument handling: This pull request fixes the handling of the
-argument representing stdin in diff mode by replacing it in-place with the stdin temporary file path, preserving its original position. It also improves support for multiple-occurrences, backward compatibility, and chat mode behavior.
- Update notification progress enhancements: This pull request enhances VS Code update notifications by displaying real-time download progress with percentage and estimated time remaining. It implements state management, platform-specific tracking for macOS and Windows, dynamic UI updates, edge case handling, and comprehensive unit tests.
- Tree component twistie customization and bug fix: These pull requests introduce an option to specify an additional CSS class for the twistie element to enhance appearance customization and fix a bug where clicking expand/collapse icons caused multiple tree items to retain focus styling. The fix changes focus update logic to ensure only a single item shows focus after expand/collapse actions.
- Security and performance improvements in parsing and chat sessions: This pull request refactors the parseLsFiles function to eliminate regular expressions and prevent ReDoS vulnerabilities using safer string methods. It also introduces a feature to prevent persistence of inline editor chat sessions.
- Terminal tabs memory leak fix: This pull request addresses a memory leak in the terminal tabs list by changing TabsRenderer from Disposable to non-Disposable and adopting templateDisposables and elementDisposables for element disposal, eliminating the leak as confirmed by testing.
- Simple browser console error logging enhancement: This pull request reintroduces and enhances logging for console errors within the simple browser feature, incorporating extensive Chrome DevTools work to enable console logs to be displayed in the chat interface.
- Terminal clipboard copyOnSelection fix: This pull request prevents the terminal's copyOnSelection feature from overwriting the clipboard when the find widget highlights search results by adding a guard in TerminalClipboardContribution to block copying if the selection originates from the find widget rather than user action.
- TypeScript language features tsconfig "extends" path resolution fix: This pull request updates TypeScript language features to correctly resolve tsconfig.json "extends" paths that use package exports subpath remapping, fixing module resolution failures and aligning with TypeScript’s logic.
- Microsoft-authentication extension cleanup: This pull request removes deprecated migration code and async factory methods from the microsoft-authentication extension, simplifying public client application construction and storage handling by eliminating legacy upgrade logic and updating calling code.
- Hot reload launch configuration and CI updates: This pull request introduces a hot reload launch configuration along with environment setting updates and continuous integration fixes.
- Editor word wrap visual indicators and minified file wrapping control: These pull requests add an optional editor feature displaying a subtle visual indicator (↩) at soft word wrap points controlled by
editor.renderWordWrapIndicator, and introduceeditor.wordWrapMinifiedto control automatic word wrapping for files with very long lines, fixing unwanted forced wrapping.
- Accessibility fix for filter input in panels: This pull request fixes an accessibility issue where filter inputs become unclickable due to overlapping badges blocking pointer events by disabling pointer events on the badge container while preserving toolbar button interactivity.
- Type definition update for getWorker functions: This pull request updates type definitions for getWorker and getWorkerUrl functions to include undefined as a possible return type, ensuring type correctness after rebasing and conflict resolution.
- Hover widget layout and style improvements: This pull request improves the hover widget layout and spacing by refactoring styles, removing unused CSS rules, and adjusting codicon sizes for better UI alignment.
- Experimental Copilot terminal command history exclusion: This pull request implements a new experimental setting to prevent Copilot-generated terminal commands from being recorded in shell history by prefixing them with a leading space, supporting Bash, Zsh, and Fish shells, and modifies command execution strategies accordingly.
- Welcome/Getting Started SVG files standardization: This pull request standardizes and refactors 18 Welcome/Getting Started SVG files by adding over 475 missing fallback colors, normalizing hex color casing, fixing malformed syntax, and ensuring consistent fallback values aligned with the Dark Modern theme to prevent rendering issues.
- Enterprise deployment policies for admin contact info: This pull request introduces new enterprise deployment policies allowing admins to configure hidden contact information settings displayed in system policy lock messages to provide actionable admin support details when settings are blocked.
- Tools Picker expand/collapse state preservation: This pull request fixes the Tools Picker to preserve expand/collapse state of tool buckets between invocations by introducing a stable identity provider for tree elements, enabling consistent state across data updates.
- VSBuffer BOM preservation regression test: This pull request adds a regression test to verify that the VSBuffer class correctly preserves the Byte Order Mark (BOM) character in filenames when converting buffers to strings, validating the fix for issue #251527.
- Extensions marketplace @allowed filter: This pull request introduces a new
@allowedfilter to the extensions marketplace, enabling users to query and display only extensions permitted by organizational policy by integratingIAllowedExtensionsServiceand implementing corresponding filtering logic.
- Output filter toggle button styling fix: This pull request adds minimal CSS to introduce spacing and a border around the output filter toggle button for visual consistency with the find widget across all FilterViewPane instances.
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: 284
Key Closed Pull Requests
1. Use ts-node to run our build scripts: This pull request proposes running the project's build scripts directly as TypeScript using ts-node to simplify their conversion to TypeScript, eliminate checked-in compiled JavaScript files, and enable direct execution of these scripts with node, while making necessary adjustments such as adding a helper to run scripts with the ts-node loader, converting modules to ES modules, and removing compiled files, though it remains a work in progress with some platform-specific issues unresolved.
- URL: pull/276864
- Merged: No
- Associated Commits: cd706, 7a371, 24f49, 9124e, b951f, f40a0, a58e8, 20769, 117cf, ff87c, 3bdc4, b3af3, 09d00, 3ab4c, 8b602, d5fbe, 57eea, cd9be, 839cd, 7919c, a86be, 1122c, 37e08, c92c1, 83c4d, f7f2e, aa1e8, 1325a, 61c3c
2. extract ChatTerminalToolOutputSection, fix a bug: This pull request extracts the ChatTerminalToolOutputSection component and fixes a bug where focus could unexpectedly move to an incorrect terminal or output element due to list re-rendering by tracking each part's position in the list, ensuring that keyboard focus always targets the most recent response in the chat terminal.
- URL: pull/277234
- Merged: Yes
- Associated Commits: 04e52, 163d4, 805ca, 071ed, fe548, a758f, 28005, 1e7bd, cde3b, 63278, b977f, 23dd1, 8da1c, b45b2, ff79b, 7d0ad, 43f46, 5664a
3. Add eligibleForAutoApproval: This pull request introduces the eligibleForAutoApproval setting to control which tools in VS Code are eligible for automatic approval, ensuring that tools marked as ineligible always require user confirmation and never offer auto-approval options, while maintaining default behavior for others and accounting for global auto-approve settings.
- URL: pull/277043
- Merged: Yes
- Associated Commits: db4d0, 3377e, 1baa1, 5b780, 3e8a9, 94fd6, 142aa, ea281, d337f, 943ac, eee76, 6c2a7
Other Closed Pull Requests
- Versioning and Build Pipeline Enhancements: This topic covers the implementation of an auto-incrementing patch versioning system for Insider builds in the Azure DevOps pipeline, introducing a pipeline-level counter scoped to the major.minor version and a ReadVersion job to validate version consistency with
package.json. The patch number is incremented before building platform-specific distributables, ensuring unique Insider build versions while requiring manual updates of the major.minor parameter on version changes.
- Enterprise Policy Configuration for Chat Tools: These pull requests add support for enterprise policy configuration of the
chat.tools.eligibleForAutoApprovalsetting, allowing administrators to control auto-approval of chat tools via JSON-based policies. The changes update policy generation infrastructure and tests, ensuring policy overrides user settings to enforce confirmation for ineligible tools.
- Terminal Command Persistence and Output Improvements: This group includes persistence of terminal commands and outputs after terminal termination and enhancements to terminal focus actions to navigate to relevant commands after reloads. Additionally, improvements in detecting questions and password requests in terminal output by analyzing more lines address longer outputs from tools like
yo code.
- Terminal Suggest Widget and Suggestion Grouping Enhancements: These pull requests fix layout issues in the terminal suggest widget by aligning its behavior with the content suggest widget and propose allowing the SimpleSuggestWidget detail pane to be set to the right side to prevent blocking terminal input. They also enhance terminal suggestions by including persistent options and improving logical grouping of suggestions.
- Code Quality and Type Safety Improvements: This topic covers the removal of the 'any' type from terminal-related code to improve type safety and the cleanup of eslint exemptions to enhance code quality and maintain linting consistency.
- Build Process and Tooling Updates: These pull requests update the build process to use the latest TypeScript version, remove deprecated settings, fix related smoke test issues, and add a TypeScript Go watcher with watch mode and localization support to enhance language features.
- Memory and Resource Leak Fixes: This group addresses memory leak errors caused by asynchronous updates on disposed ChatThinkingContentParts and fixes proxy disposable issues to ensure proper resource management without breaking functionality. It also fixes a resource leak in the MainThreadTerminalService by extending Disposable and properly registering disposables.
- UI and Styling Improvements: These pull requests improve the editing pills feature by enhancing animation, CSS styling, layering, and clarity, and refactor the comment widget by replacing dynamic inline CSS with static CSS files using CSS variables to simplify theming and improve performance.
- Chat Sessions and Delegate Menu Enhancements: This pull request introduces a
canDelegateflag to theIChatSessionsExtensionPointinterface and schema, allowing extensions to opt out of appearing in the delegate menu and filtering out external agents like OpenAI Codex to prevent them from showing alongside coding agents.
- Git Worktree Command Enhancements: This pull request enhances the
git.createWorktreeWithDefaultscommand by adding amigrateUncommittedChangesparameter that migrates all uncommitted changes to a new worktree using stash-and-apply, while handling repository registration and merge conflicts.
- OAuth Metadata Discovery Robustness: This pull request improves OAuth metadata discovery by adding robust error handling to the
fetchAuthorizationServerMetadatafunction, catching network errors, retrying all OAuth discovery endpoints before failing, and including comprehensive tests for various failure scenarios.
- Quick Pick and Editor Error Fixes: These pull requests fix issue #275068 by ignoring double-click events on Quick Pick titles when the target is a button to prevent unintended interactions, and fix the "Illegal value for lineNumber" error by adjusting parameters and adding test coverage for out-of-bounds line and column values.
- Prompt Service Caching Improvements: This pull request adds caching to the
listPromptFilesfunction in the PromptsService to ensure consistency with existing caching for slash commands and custom agents.
- Agents View Cleanup: This pull request removes the history custom node from the agents view and related code cleanups, including grouping and using archives instead.
- Manage Accounts Navigation Improvement: This pull request enables the Back button functionality on the Manage Accounts picker in the authentication workflow, improving navigation within account management.
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 | 475 | 105 | 0 | 600 |
| Tyriar | 240 | 24 | 126 | 289 |
| meganrogge | 310 | 26 | 68 | 218 |
| bpasero | 222 | 38 | 121 | 152 |
| mjbvz | 188 | 28 | 37 | 69 |
| lszomoru | 200 | 18 | 20 | 71 |
| dmitrivMS | 165 | 12 | 14 | 38 |
| aeschli | 105 | 7 | 17 | 96 |
| connor4312 | 79 | 11 | 25 | 102 |
| roblourens | 54 | 8 | 38 | 108 |
Don't miss what's next. Subscribe to Weekly Project News: