Weekly GitHub Report for Vscode: February 01, 2026 - February 08, 2026 (15:58:08)
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 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.
-
[FEATURE-REQUEST] unclear how to cancel a copilot terminal: This issue discusses the difficulty in identifying how to cancel a running command in the new Copilot terminal UI, where multiple icons are present but none clearly indicate a cancel or stop function. The user eventually found the main chat Stop button and noted that the abundance of buttons with unclear visual cues leads to confusion and inefficiency when trying to perform simple actions like canceling a command.
- The comments clarify that canceling can be done using Ctrl+C in the terminal or the existing stop button, and while adding a dedicated cancel button is unlikely, there is agreement that the current icons, especially the play button for backgrounding, are confusing and could benefit from improved design and clearer hover tooltips, with some discussion on platform-specific hover delays and the potential for a better icon to represent backgrounding.
- Number of comments this week: 11
-
Consider
Shift Tabto toggle between Plan/Agent modes in chat input: This issue proposes using theShift+Tabkeybinding to toggle between Plan and Agent modes in the chat input, citing it as an industry standard and a potentially smooth interaction. However, there are significant concerns about accessibility, particularly for screen reader users, and debate over whether this shortcut is intuitive or appropriate given existing keybindings and navigation needs.- The comments reveal a mix of support and strong opposition, highlighting accessibility conflicts with
Shift+Tabas a critical navigation key for screen readers, suggestions for alternative keybindings, and discussion about existing shortcuts likecmd+.; some users emphasize the need for easy mode switching while others caution against overloading shortcuts or creating non-intuitive interactions. - Number of comments this week: 11
- The comments reveal a mix of support and strong opposition, highlighting accessibility conflicts with
-
[INFO-NEEDED] [WINDOWS] Missing context menu on windows: This issue reports that after upgrading to version 1.109.x of VS Code on Windows 11, the context menu entry "Open with Code" is missing from the right-click menu on files and folders, although it still appears when right-clicking on the desktop or in whitespace within Explorer. Users have confirmed the problem persists across different Windows 11 builds and installation types, and reinstalling the application does not resolve the issue.
- Multiple users confirmed the missing context menu entry after the update, shared system and installation details, and noted that the option remains available only in certain contexts; requests for a fix were made, but no resolution was provided in the comments.
- Number of comments this week: 11
-
Copilot won't read skills files outside of current workspace in WSL2: This issue describes a problem where the Copilot Chat extension in VSCode running on WSL2 cannot read skill files located outside the current workspace, even when those locations are specified in the configuration. The user expects that defining external skill folders in the settings should allow access, but Copilot still fails to read these files unless the folders are explicitly added to the workspace, which is not the desired behavior.
- The comments include requests for logs, sharing of partial logs showing permission errors, suggestions to update VSCode and enable specific settings, observations about different model behaviors, and discussions about folder naming inconsistencies; ultimately, users confirm the issue persists with recent versions and that skills outside the workspace are discoverable but not usable, indicating a regression in functionality.
- Number of comments this week: 9
-
[CHAT-BILLING] Billing can be bypassed using a combination of subagents with an agent definition, resulting in unlimited free premium requests.: This issue describes a billing bypass vulnerability in Copilot where users can exploit the interaction between subagents and agent definitions to make unlimited free premium model requests, effectively avoiding charges for expensive models like Opus 4.5. The problem arises because subagent and tool calls do not consume request credits, and billing is only calculated based on the initial model used, allowing a free model to spawn premium subagents without incurring additional costs.
- The comments discuss the issue's distinction from a related bug, express skepticism about its closure, confirm the bug's reproducibility, and propose a server-side enforcement fix to bill based on the actual model used by subagents, including suggestions for integration and loop tests to prevent regression.
- Number of comments this week: 9
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
As of our latest update, there are no stale issues for the project this week.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 718
Summarized Issues:
- Performance and Responsiveness Issues: Numerous reports describe severe performance problems including freezing, unresponsiveness, excessive CPU or memory usage, and slow UI updates in VS Code and its Copilot extensions. These issues affect various features such as chat readiness, terminal responsiveness, file explorer updates, and large repository handling, often requiring disabling extensions or restarting the application to recover.
- Chat and Copilot Extension Failures: Many issues report that the GitHub Copilot Chat extension fails to start, becomes unresponsive, or produces errors such as timeouts, 400/413/500 HTTP errors, or invalid JSON responses. Users experience problems with chat history disappearing, requests failing repeatedly, and inability to send or receive messages, often across multiple platforms and VS Code versions.
- issues/292205, issues/292206, issues/292207, issues/292230, issues/292384, issues/292417, issues/292490, issues/292491, issues/292533, issues/292543, issues/292551, issues/292576, issues/292631, issues/292764, issues/292795, issues/292842, issues/292856, issues/293068, issues/293071, issues/293122, issues/293201, issues/293336, issues/293345, issues/293349, issues/293350, issues/293372, issues/293416, issues/293418, issues/293440, issues/293444, issues/293547, issues/293594, issues/293595, issues/293604, issues/293640, issues/293642, issues/293696
- Agent and Subagent Command Execution Problems: Several issues describe bugs where agents or subagents fail to execute commands properly, enter infinite loops, or produce incorrect or duplicated outputs. Problems include repeated prompts for confirmation, inability to cancel parallel agents, command conflicts due to shared sessions, and failure to handle terminal sessions correctly, leading to broken workflows and security concerns.
- File and Workspace Data Loss or Corruption: Multiple reports describe critical bugs where files or data are deleted unexpectedly, chat histories are lost, or code changes are applied incorrectly without user consent. Users report loss of private keys, project files, chat session data, and corrupted code blocks, causing significant disruption and potential financial loss.
- Terminal and Command Line Integration Issues: Users report problems with terminal behavior including commands not executing or being recorded properly, terminal flickering, infinite loops, inability to recall commands, and terminal sessions closing unexpectedly. These issues affect both integrated terminals and those used by Copilot agents, impacting usability and workflow continuity.
- issues/292159, issues/292166, issues/292168, issues/292190, issues/292222, issues/292561, issues/292823, issues/293127, issues/293219, issues/293232, issues/293574, [issues/293579](https://github.com/issues/293579], issues/293580, issues/293585, issues/293712
- UI and UX Problems: Many issues highlight user interface bugs such as misaligned buttons, unreadable text or colors, broken layouts, inconsistent theme behavior, and confusing or redundant UI elements. These problems affect accessibility, usability, and visual consistency across VS Code and its extensions.
- issues/292215, issues/292229, issues/292273, issues/292275, issues/292309, issues/292404, issues/292419, issues/292420, issues/292423, issues/292462, issues/292484, issues/292581, issues/292630, issues/292784, issues/292988, issues/293011, issues/293036, issues/293050, issues/293051, issues/293052, issues/293118, issues/293177, issues/293179, issues/293223, issues/293240, issues/293244, issues/293247, issues/293250, issues/293253, issues/293255, issues/293260, issues/293316, issues/293347, issues/293435, issues/293479, issues/293480, issues/293573, issues/293578, issues/293611, issues/293629, issues/293638
- Authentication, Licensing, and Billing Issues: Users report problems with sign-in, license recognition, unexpected quota exhaustion, billing loopholes, and premium feature access, causing frustration and loss of service despite valid subscriptions or licenses.
- Model and API Errors: Several issues describe errors related to model usage including invalid model identifiers, 400/404/408/413/500 errors, unexpected token errors, and failures in model API calls, affecting the ability to generate code, complete tasks, or receive responses.
- Feature Requests and Usability Enhancements: Users request new features such as improved prompt chaining, branch and stash management in chat, multi-grammar syntax highlighting, better model selection visibility, enhanced accessibility, integrated OCR, speech-to-text APIs, and improved CLI integration to enhance workflow and user experience.
- issues/292156, issues/292217, issues/292247, issues/292304, issues/292382, issues/292407, issues/292410, issues/292549, issues/292587, issues/292600, issues/292687, issues/292926, issues/293007, issues/293059, issues/293060, issues/293062, issues/293109, issues/293159, issues/293217, issues/293317, issues/293318, issues/293322, issues/293328, issues/293329, issues/293408, issues/293466, issues/293469, issues/293523, issues/293554, issues/293576, issues/293578, issues/293588, issues/293631, issues/293635, issues/293716, issues/293726, issues/293727, issues/293730, issues/293742, issues/293753
- Extension and Marketplace Issues: Problems include extension signature verification failures, auto-reinstallation of Copilot on remote hosts, missing or outdated extension icons, and issues with extension installation or updates causing crashes or UI problems.
- Accessibility Concerns: Several issues highlight problems with screen reader support, keyboard navigation, ARIA attributes, and inconsistent or confusing accessibility UI elements, impacting users relying on assistive technologies.
- Theme and Visual Styling Bugs: Users report issues with new themes causing unreadable text, missing icons, broken menu expansions, and inconsistent color usage, affecting the overall visual experience in VS Code.
- Code Editing and Language Features Bugs: Problems include broken rename symbol functionality, incorrect code completions, failure to apply code changes, and issues with syntax highlighting or tokenization affecting editing workflows.
- Git and SCM Integration Issues: Users report problems with Git integration such as missing references, incorrect merge conflict UI, inability to clone from enterprise, and issues with commit message handling across multiple VS Code instances.
- issues/292796, issues/292984, issues/293123, issues/293428, issues/293464, issues/293741, issues/293742, [issues/293571](https://github.com/issues/293571]
- Security and Privacy Concerns: Some issues highlight vulnerabilities such as billing bypasses, unauthorized code changes, and improper handling of sensitive files or keys, raising serious security risks.
- Miscellaneous Bugs and Requests: Various other issues include problems with file manager integration, keyboard shortcut inconsistencies, clipboard handling, and requests for improved documentation or onboarding.
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: 715
Summarized Issues:
- Copilot Chat Initialization and Readiness Delays: Multiple issues report that the GitHub Copilot Chat extension in VS Code takes an excessively long time to initialize or become ready, often showing error messages advising users to ensure they are signed in to GitHub and that the extension is installed and enabled. These delays disrupt user workflows and are accompanied by authentication failures, token fetching errors, and network problems, causing repeated failures and preventing normal chat functionality.
- issues/287185, issues/287674, issues/288587, issues/288833, issues/288947, issues/289066, issues/289110, issues/289414, issues/289588, issues/289991, issues/290263, issues/290452, issues/291204, issues/291258, issues/291577, issues/291585, issues/291729, issues/290630, issues/290711, issues/290818, issues/291839, issues/292074, issues/292178, issues/292977, issues/292978, issues/293018, issues/293353
- Authentication and Sign-In Failures: Several issues describe problems where users are unable to sign in to GitHub or maintain authentication with the Copilot Chat extension, resulting in repeated logouts, authentication errors, and inability to access chat features. These issues cause frustration and inconsistent access, often requiring repeated sign-in attempts or reinstallation of extensions.
- Chat Feature Failures and Unresponsiveness: Multiple reports indicate that the chat feature in the GitHub Copilot extension or VS Code becomes unresponsive, fails to respond, or repeatedly shows error messages such as "Sorry, no response was returned" or "Sorry, your request failed." These failures often cause the chat to stall, loop without progress, or require restarting the extension or VS Code to recover.
- Server Errors and Request Failures (502, 400, 413, 408, 504): Numerous issues report server-side errors such as HTTP 502 Bad Gateway, 400 Bad Request, 413 Request Entity Too Large, 408 Request Timeout, and 504 Gateway Timeout during Copilot or chat requests. These errors cause requests to fail, sometimes deducting user credits despite no output, and severely impact usability and reliability.
- issues/292499, issues/292501, issues/292502, issues/292503, issues/292507, issues/292508, issues/292510, issues/292511, issues/292512, issues/292513, issues/292514, issues/292516, issues/292517, issues/292518, issues/292519, issues/292522, issues/292525, issues/292529, issues/292530, issues/293145, issues/293146, issues/293475, issues/293484
- Performance Issues and High CPU Usage: Several users report that VS Code or the Copilot extension causes high CPU usage, freezes, or slowdowns, sometimes making the application unusable or causing system lag. These performance problems are linked to extension activity, large session file parsing, or chat processing.
- Extension Crashes and Runtime Errors (e.g., 'Cannot read properties of undefined (reading "bind")'): Multiple issues describe crashes or runtime errors in the GitHub Copilot Chat extension, often related to undefined properties causing failures in extension host processes and preventing normal operation. These errors frequently require rolling back to earlier extension versions or waiting for patches.
- Rate Limiting and Quota Issues: Users report unexpected or premature rate limiting, including messages indicating limits reached despite having remaining quota, and repeated rate limit errors causing interruptions and frustration. Some issues describe rate limiting occurring even with valid subscriptions and sufficient credits.
- Ollama Integration Failures: Several issues describe problems using Ollama local models with the Copilot Chat extension, including 404 page not found errors and inability to ask questions or initiate chats, despite Ollama being installed and configured.
- Terminal and Sandbox Command Execution Issues: Users report problems with running commands in the VS Code terminal or sandbox environment, including commands not executing, terminal output being clipped, inability to cancel commands properly, and sandbox features failing in WSL or remote environments.
- File and Workspace Management Bugs: Issues include files being deleted unexpectedly, text inserted into wrong files or locations, inability to edit files, background sessions showing incorrect or missing file lists, and workspace folder pickers selecting incorrect folders.
- Model and Tool Invocation Errors: Several bugs involve invalid JSON format in tool call arguments causing 400 errors, models failing to respond or prematurely terminating tasks, and issues with model selection or invocation leading to incorrect or missing responses.
- UI and Accessibility Issues: Various problems include inconsistent font sizes, missing or incorrect visual elements, poor contrast in themes, inaccessible or confusing screen reader behavior, and UI elements not responding as expected.
- Code Completion and Suggestion Problems: Users report that Copilot suggestions can be intrusive, irrelevant, or overly aggressive, sometimes causing confusion or wasting tokens and time. Some users request disabling or limiting suggestions.
- Session and History Management Bugs: Issues include loss of chat sessions, duplicate or inconsistent session data, failure to index or display saved sessions, and problems with session scoping and filtering.
- Network and Proxy Connectivity Issues: Some users experience network errors, timeouts, or fetch failures due to proxy configurations, firewall rules, or internet restrictions, impacting the ability to use Copilot Chat or related features.
- Copilot Chat Session and Agent Mode Bugs: Reports include agents not returning responses, editing tools disabled in agent mode, and agents incorrectly deleting files or producing inaccurate outputs, causing workflow disruptions.
- Miscellaneous Bugs and Feature Requests: Various other issues include requests for UI improvements, accessibility enhancements, feature additions like dark mode or prompt linting, and reports of spam or incomplete bug reports.
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.65 (Rapid escalation, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment and frustration towards a software agent, using harsh and dismissive language. There are no replies or further interactions, so the tone remains unchallenged and the conversation does not evolve. The lack of engagement and the aggressive nature of the initial comment suggest potential for tension if others respond.
-
I signed up for the bot and it said I've exhausted my quota??
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, threats)
- This GitHub conversation features a user expressing strong frustration and dissatisfaction with a service, using aggressive and accusatory language directed at the service provider. The tone is confrontational and demands immediate action, including a refund and cancellation, with threats of reporting fraud. There is a clear trigger of tension stemming from perceived service failure and unmet expectations.
-
- Toxicity Score: 0.75 (Rapid escalation, dismissive language, accusatory tone)
- This GitHub conversation begins with a user raising a concern about a technical issue, followed by another user responding with a neutral request for more information, indicating a helpful tone. However, the subsequent comment shifts abruptly to a dismissive and accusatory tone, suggesting the issue is spam and should be closed, which introduces tension and potential conflict. The interaction moves from constructive inquiry to a confrontational stance without resolution.
-
ai destroyed my site three times i need a human
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, unresolved frustration)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with the AI feature and support system, using harsh language and demanding human intervention. The tone is highly negative and confrontational, with no responses or engagement from other users, which may contribute to unresolved tension. The lack of dialogue and the user's aggressive approach suggest potential for escalation if further comments occur.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, unresolved frustration)
- This GitHub conversation features a single user expressing strong frustration and disappointment with the product and support agents, using harsh and accusatory language. The tone is highly negative and confrontational, with no responses or attempts at resolution visible in the thread. The tension is triggered by the user's dissatisfaction with the time and money spent without achieving a solution.
-
Tokens got eaten by previous erros & bugs of vscode
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a user expressing frustration and urgency regarding a perceived problem with the software, using informal and somewhat aggressive language. The tone is accusatory and impatient, indicating dissatisfaction with the handling of the issue. There is a trigger of tension stemming from the user's belief that the problem causes financial loss and lack of adequate response from the maintainers. No other participants or responses are present to moderate or escalate the tone further.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, strong emotional expression)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger about an issue, using explicit language and a highly emotional tone. There are no responses or further interactions, so no shifts in sentiment or tone occur. The lack of replies means no escalation or resolution is observed.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive content)
- This GitHub conversation consists of a single user posting a highly negative and offensive comment without any responses or further discussion, indicating a one-sided expression of frustration with a hostile tone.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, hostile tone, spam label)
- This GitHub conversation consists of a single initial post by a user expressing strong negative emotions through aggressive language and insults, with no subsequent comments or engagement from other users. The tone is hostile and inflammatory, and the issue was labeled as spam, indicating a lack of constructive dialogue or resolution.
-
- Toxicity Score: 0.95 (Rapid escalation, aggressive language, explicit insults)
- This GitHub conversation involves a single user expressing strong frustration and anger in a highly aggressive and offensive tone, using explicit language and insults. The sentiment is overwhelmingly negative, with no responses or attempts at resolution visible. The tension is triggered by dissatisfaction with the software's behavior and perceived lack of appropriate functionality.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, rule enforcement response)
- This GitHub conversation involves a user expressing extreme frustration and using offensive language directed at the platform and its maintainers, which triggers an automated bot response closing the issue for violating community guidelines. The tone is highly aggressive and hostile from the user, while the bot maintains a neutral and procedural tone. The tension arises from the user's dissatisfaction and the bot's enforcement of rules without engaging in dialogue.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided hostility)
- This GitHub conversation involves a single user expressing intense frustration and anger towards the development team, using aggressive and profane language to criticize recent changes. The tone is highly confrontational and hostile, with no responses or attempts at dialogue from other participants, leading to a one-sided venting of dissatisfaction. The lack of engagement and the presence of strong negative emotions suggest a potential for escalation if further comments occur.
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: 108
Key Open Pull Requests
1. Chat - implement session picker in the chat panel title: This pull request implements a session picker feature in the chat panel title of Visual Studio Code, refining the user interface to allow easier selection and management of chat sessions, and includes various related improvements and fixes as a second attempt following a previous pull request.
- URL: pull/293426
- Associated Commits: 36086, dc748, 43089, 8a6a8, 50b7d, 1e4b6, dd4e0, fc0f7, 1854e, dc483, 3d85e, 8efd0, ec22f, a8ba8, a48e2, f3768, 89a51, 45f7e, 51b26, 2d155, 6b96e, 143a0, e0bca, 0f785, 5660d, 27d95, 1412c, c0d2f
2. Update configure hooks flow and supported paths: This pull request updates the configuration hooks flow and the supported paths within the Visual Studio Code project, including multiple commits that refine handling, clean up code, fix tests, and merge changes from the main branch.
- URL: pull/293643
- Associated Commits: 38376, a6220, 9c633, e9e1d, 09aca, 4ac60, c6932, a7fcd, 68fa2, 06cb7, 43d24, 3eda1, 5225f
3. Fix double update issue on Windows: This pull request addresses and fixes the issue of double updates occurring on Windows in the Visual Studio Code project, as referenced by issue #268531.
- URL: pull/292746
- Associated Commits: 293d2, 85649, 8dc8b, c3f0f, 45ce8, 6baab, f9875, 4eb58, d17df, ff0fc, 596c2, 9912c
Other Open Pull Requests
- Chat session targeting enhancements: This pull request adds a
targetparameter to thevscode://GitHub.Copilot-Chat/chatdeep link and theworkbench.action.chat.opencommand, allowing programmatic selection of chat session types such as local, background, cloud, Claude, or Codex. It maps these targets to specific session providers and creates new sessions when the current session is empty and local.
[pull/292925]
- UI theming and visual improvements: Multiple pull requests enhance theming and visual effects, including adding blur and transparency effects to modals in the 2026 themes, comprehensive theming for the activityBarTop and activityBarBottom with icon refinements and restored theming participants, and fixing overlapping text in the Agent Sessions Welcome screen for narrow viewports. These changes improve customization, visual consistency, and readability across the UI.
[pull/293281, pull/293557, pull/292276]
- Debug session lifecycle and agent session UI fixes: Improvements to debug session listener management replace array tracking with a DisposableMap to prevent memory leaks and simplify disposal logic. Additionally, the agent status indicator's color issue during debugging is fixed by replacing a CSS variable with hardcoded semi-transparent backgrounds, preserving normal agent status colors while allowing command center color changes.
[pull/293442, pull/292632]
- Git and repository management enhancements: Enhancements include improving the "Clone from GitHub" feature by prioritizing user and organization repositories with parallel fetching and deduplication, adding a "Fetch" button to remote branch items in the Git checkout picker for individual branch fetching, and fixing false positive merge conflict detection by verifying active Git merge states before showing conflict UI. These changes improve repository handling and user experience in Git workflows.
[pull/293539, pull/293041, pull/293381]
- Agent session status and native OS integration: One pull request extracts "input needed" notification logic from an experimental widget into production-ready components that display badges in the command center when agent sessions require input. Another adds native OS integration for real-time agent session status using Electron APIs, showing session counts and states via macOS Dock badges or Windows/Linux system tray icons, with IPC communication and telemetry support.
[pull/292954, pull/292315]
- Performance and resource management improvements: The npm extension is improved by replacing text document openings of package.json files with direct file reads and introducing an LRU cache to reduce LSP server notifications. A typo fix and resource leak fix ensure proper file handle closure in
getOSReleaseInfoto prevent descriptor leaks on Linux.
[pull/292380, pull/293105]
- Crash fixes and error handling in Rust CLI and tunnel flows: This pull request addresses multiple crash and edge-case bugs by preventing keychain credential corruption, stopping msgpack RPC loops on EOF, converting panic paths into manageable errors or warnings, and fixing update extraction crashes for small or empty archives. All changes are minimal and covered by new unit tests.
[pull/292602]
- Terminal sandbox network configuration update: A new boolean property
allowTrustedDomainsis added to the terminal sandbox network configuration, enabling merging and use of the existing trusted domains list. Related services are refactored to support this integration with dynamic updates when trusted domains change.
[pull/293330]
- Claude agent support introduction: This pull request introduces support for Claude agents, including relevant code updates and tests to integrate this new functionality into the project.
[pull/293354]
- Extension and editor behavior fixes: Fixes include preventing the active editor from closing automatically when installing an extension by adding
preserveFocus: trueto the extension details editor, and removing a 5-second timeout workaround in the authentication service’s activation method to simplify logic and clean up unused code.
[pull/292377, pull/292588]
- Agent sessions panel layout actions: New layout actions for the agent sessions panel title are added, including hide sidebar, maximize, and restore panel size functionalities. These actions are organized in a dedicated file and appear contextually only when relevant.
[pull/292611]
- File management commands: Two new Command Palette commands allow users to duplicate and rename the currently active file with user-friendly input, support moving files across directories with overwrite prevention, include undo/redo via bulk edit service, and automatically update the editor to reflect changes.
[pull/293069]
- Git diff view and repository state fixes: Fixes a race condition causing stale repository state in the diff view by ensuring empty content is shown on the left side when unstaging new files, addressing issue #264340 in the GitFileSystemProvider.
[pull/293423]
- Windows file type registration fix: Registers supported file types under the Applications and Capabilities registry keys on Windows to fix "Open With" functionality issues and improve user scenarios.
[pull/293033]
- Subtle animation improvements: Introduces and refines subtle entry and exit animations within the project, including fixes to exit animation behavior.
[pull/293489]
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: 372
Key Closed Pull Requests
1. disable modal editor for now from core: This pull request proposes temporarily disabling the modal editor feature from the core of the project, as indicated by the title and the commit message "disable modal editor for now from core," and it was not merged.
- URL: pull/293680
- Associated Commits: 2c8b7, 224c7, cbb83, 4b4de, 0d384, 97c93, f0623, 1b11b, c3ff7, c5268, aa1a2, 5e23e, 0efcb, ac28f, e6d31, 91bb4, 4d684, 7f277, 97118, c5b7b, 1adb1, 384b1, 0f40d, 5c6aa, fcb07, 59f5e, 08d1c, be047, f7e9a, 4a102, abaed, e98b1, 9136d, 22ddc, f390c, 83a5f, af734, 36fa9, ce530, fc921, 36738, d01ed, 81830, c8ee7, 2a2c8, 340a9, fff0d, 7aba5, 0f6f0, ad804, e05b5, 4c914, d4360, 7ad7e, 868b5, 33ad9, 52cc5, 8e7d8, 633b5, 2b601, cc911, c1b60, 5c875, f089a, c1021, 628c5, 3ccea, 09695, 870aa, 87442, 2d80a, 4c1d4, 1cf24, 0d564, f4e3f, 5162a, 9a8a3, ec83f, 248ef, 981fa, 5999d, 86e0f, 4bbf7, 35f34, 8ed51, a4942, 068e1, ca007, bb856, d3549, 9eb8d, da2c6, 067e1, 30430, 4c536, 86baf, c9f95, e1dfb, 1ff17, ab9a7, 9a04a, 8f119, 5b7c6, 3e8a6, 6dab6, 58ec1, b05a6, 738a3, d1024, dda90, 79819, 8524c, 46557, 4c0cb, 9a98b, 64e3a, 1fd40, 44b73, 07da5, 6d297, bcdaa, 7ad3d, 254aa, 0987a, 86acd
- Associated Commits: 2c8b7, 224c7, cbb83, 4b4de, 0d384, 97c93, f0623, 1b11b, c3ff7, c5268, aa1a2, 5e23e, 0efcb, ac28f, e6d31, 91bb4, 4d684, 7f277, 97118, c5b7b, 1adb1, 384b1, 0f40d, 5c6aa, fcb07, 59f5e, 08d1c, be047, f7e9a, 4a102, abaed, e98b1, 9136d, 22ddc, f390c, 83a5f, af734, 36fa9, ce530, fc921, 36738, d01ed, 81830, c8ee7, 2a2c8, 340a9, fff0d, 7aba5, 0f6f0, ad804, e05b5, 4c914, d4360, 7ad7e, 868b5, 33ad9, 52cc5, 8e7d8, 633b5, 2b601, cc911, c1b60, 5c875, f089a, c1021, 628c5, 3ccea, 09695, 870aa, 87442, 2d80a, 4c1d4, 1cf24, 0d564, f4e3f, 5162a, 9a8a3, ec83f, 248ef, 981fa, 5999d, 86e0f, 4bbf7, 35f34, 8ed51, a4942, 068e1, ca007, bb856, d3549, 9eb8d, da2c6, 067e1, 30430, 4c536, 86baf, c9f95, e1dfb, 1ff17, ab9a7, 9a04a, 8f119, 5b7c6, 3e8a6, 6dab6, 58ec1, b05a6, 738a3, d1024, dda90, 79819, 8524c, 46557, 4c0cb, 9a98b, 64e3a, 1fd40, 44b73, 07da5, 6d297, bcdaa, 7ad3d, 254aa, 0987a, 86acd
2. Add initial hooks support: This pull request introduces the initial configuration handling and API implementation to support hooks in the project, enabling basic hook execution and integration within the core system.
- URL: pull/292699
- Associated Commits: 5bc9d, a86d5, a2295, 968d1, 534f7, d4eac, 7d7e7, a33d5, 53989, 4f314, 2c8d3, df607, 1033f, cd6e7, c9dbe, ed068, 65d04, 0d4c9, bc362, 6ebd9, c61f7, 323c0, f8528, 34965, b3695, b3fc1, 96dd8, 7108c, b73d0, aee2a, f0bb0, 88725, 62d9c
- Associated Commits: 5bc9d, a86d5, a2295, 968d1, 534f7, d4eac, 7d7e7, a33d5, 53989, 4f314, 2c8d3, df607, 1033f, cd6e7, c9dbe, ed068, 65d04, 0d4c9, bc362, 6ebd9, c61f7, 323c0, f8528, 34965, b3695, b3fc1, 96dd8, 7108c, b73d0, aee2a, f0bb0, 88725, 62d9c
3. fix: improve QuickInput accessibility for screen readers: This pull request aims to fix and enhance the accessibility of the QuickInput dialog for screen reader users by removing redundant ARIA attributes, dynamically managing aria-haspopup and aria-autocomplete states, improving label announcements, and ensuring proper character and navigation feedback, specifically addressing issues in the Ctrl+G Go to Line dialog.
- URL: pull/292227
- Associated Commits: 672b4, 9d903, d11f0, f1c91, ee4f5, 9c846, a16dc, a0ed6, 32b51, 3bc0f, 51715, 218e4, 2f64d, a9fb6, e83b9, 4c438, e36c6, 84a93, 3a613, cd3c1, e3d11, cc851, 6069c, 1d9e9, cd811, 73b6f, 9b7c0
- Associated Commits: 672b4, 9d903, d11f0, f1c91, ee4f5, 9c846, a16dc, a0ed6, 32b51, 3bc0f, 51715, 218e4, 2f64d, a9fb6, e83b9, 4c438, e36c6, 84a93, 3a613, cd3c1, e3d11, cc851, 6069c, 1d9e9, cd811, 73b6f, 9b7c0
Other Closed Pull Requests
- Metered Network Connection Support: This pull request adds comprehensive support for metered network connections in Visual Studio Code by introducing a public API, user settings, a status bar icon, and a new service that delays or pauses automatic network operations such as update downloads, extension updates, settings sync, Git auto-sync, and telemetry uploads while the connection is metered. These operations resume automatically once the connection is no longer metered, improving network usage control.
- Agent Sessions UI and Improvements: Multiple pull requests focus on the agent sessions feature, including the implementation of an Agent sessions window with minimal UI and session management, as well as UI refinements such as improved descriptions, diff badges, color schemes, and formatting for a cleaner appearance. Although the initial implementation was not merged, the UI improvements enhance user experience in managing agent sessions.
- Chat Feature Enhancements: Several pull requests improve chat functionality by adding user action confirmations from toast notifications, introducing a streaming hook for chat content rendering with updated API and styling, and clarifying internal versus external chat hook types for better code structure. These changes enhance interactivity and maintainability of the chat system.
- Hooks System Improvements: Pull requests introduce a common blocking behavior for hooks, add an
onDidExecuteHookevent with detailed payloads, and propose a stop hook feature with deny functionality (not merged). These updates improve hook management, execution tracking, and control within the project.
- Update Status Bar and Service Enhancements: This pull request enhances the update status bar item by adding dynamic hover information showing update progress and status, quick actions for downloading, installing, and restarting updates, and modifies the update service to provide detailed update states. It also updates the "Show Release Notes" command to accept a version parameter and adds settings to control the update status bar's visibility and behavior, improving user feedback during updates.
- Codebase Refactoring and Settings Management: A pull request refactors the code by hardcoding a readonly constant for commonly used settings, replacing the dynamic list from
productService, addsGitHub.copilot.manageExtensionto this list, removes the dependency onproductService, and updates related functions and types for consistency and type safety. This improves maintainability and clarity of settings management.
- Accessibility Improvements: Multiple pull requests add comprehensive accessibility features including an Accessibility Help System for find and filter dialogs with keyboard shortcuts and screen reader guidance, and the first repository skill with detailed accessibility guidelines for Visual Studio Code features. These efforts enhance usability for users with disabilities.
- External Tool and Experimentation Integration: Pull requests enable tracking of external tool calls with related cleanup, and add the use of
copilotTrackingIdas an assignment unit in the experimentation service to allow consistent experiment assignments across VS Code and the Copilot Chat extension. These changes improve telemetry and experimentation consistency.
- Performance and Memory Leak Fixes: A pull request fixes memory leaks in the terminal task system by cleaning up event listeners and following established patterns, resolving issue #269006. Another optimizes the
whenPanelAgentHasGuidancefunction by filtering context key change events to reduce unnecessary checks and ensure proper updates. These improvements enhance performance and resource management.
- Editor and Model Event Refactoring: This pull request refactors event delivery between text models and view models to ensure immediate awareness of model events by all view models, enforcing strict event processing order. This improves cursor position accuracy during undo/redo operations and simplifies model-view connections.
- Modal Editor Group Concept: A pull request introduces a new
MODAL_GROUPconcept for a modal editor part in the editors component, enhancing management of modal editor groups within the project.
- Find in Page Prepopulation Feature: This pull request implements prepopulating the Find in Page search textbox with the currently selected text, using a preload script to securely expose
window.getSelection()via Electron's context isolation. The feature activates only if the selection contains no newlines and the page is fully loaded, improving search usability.
- Vision Policy for Image Attachments: A pull request adds vision policy handling for image attachments in the editor by showing warnings when editor preview features are disabled, enhancing user awareness and control over image content.
- Simple Browser AI Feature Gating: This pull request updates the Simple Browser's "Add element to chat" overlay to reactively respect AI feature settings, allowing the overlay to show or hide immediately without requiring a restart. This ensures consistent gating of AI features in real-time.
- GitHub Actions Workflow Addition: A pull request adds a new GitHub Actions workflow file named
generator-generic-ossf-slsa3-publish.ymlto the repository, enhancing CI/CD capabilities.
- Claude.md Support and File Handling Improvements: This pull request adds support for claude.md, including tests and improvements for handling symlinks and duplicate file paths, enhancing file management and integration.
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 | 931 | 72 | 0 | 613 |
| bpasero | 369 | 42 | 20 | 17 |
| meganrogge | 182 | 25 | 19 | 51 |
| dmitrivMS | 219 | 22 | 3 | 20 |
| roblourens | 173 | 23 | 14 | 37 |
| pwang347 | 192 | 18 | 5 | 9 |
| sandy081 | 188 | 6 | 3 | 3 |
| osortega | 148 | 6 | 3 | 9 |
| joshspicer | 143 | 6 | 7 | 7 |
| mrleemurray | 113 | 23 | 9 | 11 |
Access Last Week's Newsletter:
Don't miss what's next. Subscribe to Weekly Project News: