Weekly GitHub Report for Vscode: January 16, 2026 - January 23, 2026 (21:06:10)
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 as detailed in the linked GitHub milestone for "February 2025 Recovery 2." This update emphasizes bug fixes and stability improvements, with full 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.
-
[INFO-NEEDED] Copilot Agent file tools fail with WSL path mismatch: This issue describes a problem where GitHub Copilot Agent's file manipulation tools fail to work correctly in a WSL environment due to a path format mismatch: the grep_search tool returns Windows-style backslash paths, while read_file and replace_string_in_file tools reject these paths as being outside the workspace, causing errors. The problem occurs only in one specific project folder after it was moved to a new location within WSL, and attempts to clear workspace caches and reinstall extensions have not resolved the inconsistency, suggesting a deeper issue with path handling or workspace identity caching.
- The comments focus on confirming the environment setup, verifying that the Copilot extension runs on the WSL side, and clarifying that the issue is isolated to one relocated project folder; troubleshooting steps including cache clearing and extension reinstall were discussed but did not fix the problem, and requests for detailed request logs were made to further diagnose the path mismatch causing the file tools to fail.
- Number of comments this week: 9
-
[TRIAGE-NEEDED] Planing is broken : This issue reports a bug where the planning feature in the extension is broken, preventing users from accessing or using it properly. The user provides detailed system information and expresses frustration with the functionality, indicating repeated failures and dissatisfaction with the service.
- The comments reveal user frustration with the broken feature, including inability to see a button and repeated attempts to fix the issue without success, alongside harsh criticism of the service as unreliable and a waste of time and money.
- Number of comments this week: 8
-
Do not hide away thinking output if user is reading it: This issue addresses the problem of the "thinking" output widget disappearing suddenly while a user is actively reading it, suggesting that the widget should remain visible if the mouse cursor is hovering over it and include a manual "Hide" button for user control. The user proposes improving the interaction to prevent the jarring experience of losing the thinking output unexpectedly, aiming for a more intuitive and user-friendly behavior.
- The comments discuss differing opinions on whether the thinking output should remain visible based on cursor position, with some expressing concern about unpredictability and others emphasizing the usefulness of seeing the thinking process. Various suggestions include toggling visibility through clicks, referencing past settings that controlled auto-hide behavior, and considering telemetry to understand user preferences, while acknowledging a trend toward minimizing the prominence of thinking text.
- Number of comments this week: 6
-
[INFO-NEEDED] Devcontainer can't install any extensions or it's very slow: This issue describes a problem where installing extensions inside a Dev Container environment is extremely slow or fails, despite the same extensions installing quickly on the local machine or on other devices using the same network. The user reports that this slowdown started recently without any updates to VS Code or Docker, and that using a VPN seems to improve extension installation speed, but the root cause remains unclear as it only affects Dev Containers.
- The comments reveal that the issue also appeared on another device, with no clear update triggering it, and that the user does not use a proxy or VPN normally; some extensions install fine while others hang, and enabling a VPN improves performance, but the problem is isolated to Dev Containers and remains unresolved.
- Number of comments this week: 6
-
[INFO-NEEDED] Copilot Chat sessions unexpectedly lost;sidebar cannot recover active conversations ## Description: This issue describes a problem where Copilot Chat sessions in VS Code are unexpectedly lost, and the sidebar fails to recover or restore these active conversations, resulting in the permanent loss of important context and disruption to the user's workflow. The problem occurs randomly without a clear trigger, and attempts to restart VS Code or reinstall the extension have not resolved the issue.
- Multiple users confirm experiencing the same problem across different VS Code versions, including Insiders, with reports of the extension hanging; one user requests more detailed descriptions and error logs from the Window output channel to better understand the issue.
- Number of comments this week: 5
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: 617
Summarized Issues:
- Copilot Chat Slow Activation and Readiness Issues: Many reports describe the GitHub Copilot Chat extension and related chat features taking an excessively long time to become ready, with delays caused by token fetching failures, network connectivity errors, authentication problems, missing files, and proxy connection failures. These issues affect various platforms including Windows, macOS, Linux, and VS Code Insiders, significantly impacting usability and user experience.
- issues/288470, issues/288484, issues/288485, issues/288525, issues/288543, issues/288544, issues/288546, issues/288550, issues/288553, issues/288554, issues/288557, issues/288599, issues/288612, issues/288615, issues/288636, issues/288644, issues/288687, issues/288744, issues/288767, issues/288787, issues/288788, issues/288840, issues/288947, issues/289000, issues/289107, issues/289110, issues/289113, issues/289221, issues/289291, issues/289292, issues/289314, issues/289336, issues/289640, issues/289686, issues/289788, issues/289878, issues/289879, issues/289884
- Extension Crashes, Freezes, and Unresponsiveness: Several issues report that the VS Code extension or Copilot becomes unresponsive, crashes, or freezes during use, including infinite loops, hanging during long chat sessions, or after certain operations like starting agent mode or running commands. These problems cause loss of context, require restarts, and disrupt workflows across Windows, Linux, and macOS platforms.
- Git and Source Control Integration Problems: Multiple issues highlight problems with Git operations in VS Code, including failures in commit & push behavior, stuck source control panels, inability to open folders or repositories, issues with background sessions and worktrees, and problems with merge conflict batch deletions. These issues cause workflow disruptions and confusion in managing source control within VS Code.
- issues/288450, issues/288452, issues/288596, issues/288803, issues/288805, issues/288807, issues/289048, issues/289199, issues/289294, [issues/289448](https://github.com/issues/289448], issues/289540, issues/289541, issues/289542, issues/289632
- Agent and Subagent Functionality Bugs: There are reports of agents and subagents in Copilot chat failing to execute properly, including issues with subagents not being called, incorrect tool usage, infinite loops, premature stopping, and lack of parallelization. These bugs affect the reliability and expected behavior of AI-assisted workflows and task execution.
- File and Workspace Management Issues: Users report problems with file handling such as inability to open folders, files not appearing in chat panels, corrupted or missing generated files, issues with symbolic links, and workspace trust prompts interfering with system folders. These issues hinder file navigation, editing, and workspace management in VS Code.
- Terminal and Command Execution Problems: Several issues describe bugs in the integrated terminal including rendering corruption, input not accepted, commands hanging or failing, terminal sessions not selectable, and problems with background terminal management. These issues affect command line workflows and integration with AI agents.
- Authentication and Sign-In Failures: Users experience issues signing into GitHub or Copilot, including repeated sign-in prompts, failure to open authentication browsers, and chat features not recognizing signed-in states, leading to unusable AI features.
- UI and UX Problems: Various issues report UI glitches such as misaligned chat inputs, blurry icons, disappearing widgets, incorrect scroll behavior, overlapping responses, missing buttons, and inconsistent focus or hover states, which degrade the user experience.
- Model and API Errors: Reports include models failing to resolve, unexpected model switching, hallucinations with large context lengths, and errors in tool call arguments or JSON formatting, causing failures in AI responses and tool integrations.
- Performance and Resource Usage Issues: Users report slow performance, freezing, excessive logging, memory leaks, and high CPU usage in various scenarios including git operations, chat sessions, and extension loading, negatively impacting productivity.
- Feature Requests and Enhancements: Numerous requests include adding settings for disabling automatic file reading, batch deleting merge conflict files, renaming editor groups, adding debugging support in the integrated browser, improving session list context, and enabling more flexible terminal and agent controls.
- issues/288471, issues/288502, issues/288583, issues/288627, issues/288628, issues/288703, issues/288740, issues/288752, issues/288774, issues/288806, issues/288821, issues/288974, issues/289019, issues/289091, issues/289093, issues/289098, issues/289164, issues/289417, issues/289433, issues/289434, issues/289435, issues/289452, issues/289566, issues/289595, issues/289624, issues/289727, issues/289759, issues/289823, issues/289824, issues/289827, issues/289933, issues/289945
- Platform and OS Compatibility Issues: Some problems are specific to certain OS versions or hardware, such as VS Code failing to launch on older macOS versions, terminal rendering issues on Apple Silicon, and keyboard shortcut malfunctions on Wayland sessions.
- issues/288463, issues/288682, issues/289575, [issues/289749](https://github.com/issues/289749], issues/289901
- Security and Privacy Concerns: Issues include requests for disabling automatic file reading to prevent proprietary code leakage, concerns about Copilot sending workspace context when signed out, and the need for fine-grained file system permissions for agents.
- Miscellaneous Bugs: Various other bugs include incorrect search behavior, cursor disappearance, incorrect indentation reversion, missing Python Play Button, and problems with inline completions and code formatting.
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: 648
Summarized Issues:
- Windows Update Flow Improvements: Multiple issues focus on enhancing and rolling out the improved update flow for the Windows version of the software, including removing restrictions limiting the new update flow to insiders and addressing broken update functionality in forks. These efforts aim to stabilize and broaden the availability of the update mechanism to all Windows users.
- Copilot Chat and Extension Readiness Delays: Numerous reports describe the GitHub Copilot Chat extension and related chat features taking excessively long to become ready or failing to activate properly, often accompanied by authentication token fetch failures, network errors, or repeated login issues. These delays significantly impact user experience by preventing timely access to AI-assisted coding features.
- issues/285745, issues/287078, issues/287098, issues/287620, issues/287751, issues/287863, issues/288024, issues/288513, issues/288555, issues/288655, issues/288676, issues/288677, issues/288678, issues/288799, issues/288958, issues/288959, issues/288960, issues/288965, issues/289442, issues/289443, issues/289740, issues/289799, issues/289820, issues/289996
- Model Selection and Availability Issues: Many issues report problems with model selection in the VS Code extension, including inability to resolve or select specific models (notably "gpt-4.1"), models not appearing in selectors, automatic selection of unavailable models, and language model unavailability errors. These issues prevent users from effectively choosing or using AI models for coding assistance.
- issues/287251, issues/287260, issues/287273, issues/287294, issues/287304, issues/287317, issues/287321, issues/287329, issues/287339, issues/287351, issues/287357, issues/287363, issues/287365, issues/287371, issues/287385, issues/287393, issues/287394, issues/287404, issues/287407, issues/287408, issues/287417, issues/287423, issues/287437, issues/287463, issues/287467, issues/287504, issues/288823, issues/288824, issues/289063, issues/289529, issues/289892
- Copilot Extension Crashes and Errors: Several issues describe crashes, unresponsiveness, or errors in the GitHub Copilot extension and Copilot Chat, including "Cannot read properties of undefined (reading 'bind')" errors, activation failures, and unexpected termination of streams. These bugs disrupt the normal operation of AI-assisted coding features and cause user frustration.
- Performance and Latency Problems: Multiple reports highlight performance degradation, high CPU usage, long latency times, and freezing issues in VS Code and its extensions, especially during chat sessions or when using AI features. These problems lead to slow response times, unresponsive UI, and degraded user experience.
- Invalid JSON Format and Request Failures: Numerous issues report requests failing with 400 errors due to invalid JSON format in tool call arguments, causing repeated request failures and preventing successful AI interactions. This is a widespread problem affecting multiple versions and platforms.
- Agent and Session Management Issues: Several issues describe problems with agent sessions, including inability to select or use agents, sessions becoming stuck or zombie, missing or duplicated UI elements, and difficulties managing multiple sessions or switching chat targets. These issues complicate workflow and reduce usability of agent features.
- Copilot Token and Billing Concerns: Users report unexpected consumption of usage budget or tokens for queries that do not return resolved or useful responses, requests for clarification on billing behavior, and concerns about being charged for failed or incomplete requests. These issues highlight transparency and fairness concerns in usage accounting.
- UI and Usability Bugs: Various issues report UI glitches such as truncated buttons, misplaced icons, unreadable terminal welcome text, obstructed input areas, inconsistent checkbox styling, and problems with drag-and-drop targets or session list overflow. These bugs degrade the user interface and hinder smooth interaction.
- Agent Tool and Command Issues: Some issues describe problems with tool calls in chat responses, including incomplete or missing information, unknown tool errors when chat agent is disabled, and auto-approved commands triggering unexpected system notifications. These issues affect the reliability and clarity of tool integrations.
- Extension Signature Verification Failures: Multiple reports indicate that the GitHub Copilot Chat extension fails signature verification on various platforms, preventing proper use and requiring additional logs for investigation.
- Chat Context and Conversation History Problems: Some issues report that Copilot chat loses modification history, prematurely summarizes or drops earlier messages, or fails to maintain conversation context, leading to incoherent or incomplete AI responses.
- Miscellaneous Bugs and Feature Requests: Other issues cover a wide range of topics including performance regressions, UI improvements, feature requests for regex testers, multi-model selection, session management enhancements, and bug report automation workflows.
- Terminal and Shell Integration Issues: Several reports describe problems with the integrated terminal, including inability to type, missing path display, shell integration breaking history, and terminal commands not collapsing or expanding as expected.
- Security and Licensing Concerns: A few issues mention proprietary license declarations and security errors related to cross-origin iframe communication, highlighting concerns about access restrictions and software licensing.
- Code Generation and Editing Bugs: Some issues report bugs where Copilot duplicates code, generates code in reverse order, or applies unwanted changes without user approval, causing errors and corrupted files.
- Authentication and Sign-in Problems: Users report issues with Microsoft login failures, invalid pin codes, and repeated sign-in prompts, which prevent proper authentication and access to features.
- Chat UI and Interaction Bugs: Issues include problems with chat input box sizing, message editing glitches, inaccessible buttons, and focus management in chat accessible views, all affecting smooth user interaction.
- Miscellaneous Performance and Stability Issues: Additional reports cover extension host crashes, memory leaks, and unexpected application termination affecting overall stability.
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.85 (Rapid escalation, aggressive language, accusatory tone, repeated insults)
- This GitHub conversation begins with a user reporting an issue and sharing a screenshot, followed by several comments expressing strong dissatisfaction and frustration towards the service and its AI features. The tone quickly shifts to aggressive and accusatory language, with users venting about perceived failures and scams. The conversation shows escalating negativity without constructive engagement or resolution attempts, indicating a tense and hostile environment.
-
said it did one thing did a differnt thing
- Toxicity Score: 0.65 (Rapid escalation, accusatory language, unresolved tension)
- This GitHub conversation involves a user expressing strong dissatisfaction and accusing another party of dishonesty, with a tone that suggests frustration and mistrust. The issue is marked with labels indicating a need for more information and triage, but no comments are present to show further interaction or resolution. The sentiment is negative, and the tension is triggered by perceived repeated falsehoods.
-
wasting my time and taking my promts for money
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, user frustration)
- This GitHub conversation involves a user expressing frustration and impatience towards automated responses and perceived repetitive messages, with a tone that escalates from neutral to increasingly agitated. The user directs their dissatisfaction at the system or bot, indicating a sense of wasted time and annoyance. There is no evidence of other participants engaging, and the tension is primarily triggered by the user's negative reaction to the automated feedback.
-
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, unresolved tension)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with the product, using capitalized words and rhetorical questions that convey anger and disappointment. The tone is confrontational and accusatory, with no responses or attempts at resolution visible in the thread. The lack of engagement from other participants leaves the tension unaddressed and unresolved.
-
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, confrontational tone)
- This GitHub conversation consists of a single issue report by one user expressing strong dissatisfaction and frustration with certain suggestions, using aggressive language and a confrontational tone. There are no comments or responses from other users, so the conversation has not developed further or shown any signs of de-escalation or resolution. The initial post's tone and language indicate a potential for tension if others respond.
-
EU AI ACT VIOATION: Claude ignores instructions, lies, and makes untrue claims
- Toxicity Score: 0.65 (Rapid escalation, accusatory tone, sarcasm)
- This GitHub conversation involves a user expressing serious concerns about compliance and legal liability related to instructions not being followed, with a tone that is formal and accusatory. The initial comment from another participant responds with a sarcastic and dismissive remark, indicating frustration and a confrontational stance. The interaction shows early signs of tension triggered by the legal implications raised and the perceived disregard for compliance.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with a software feature, using aggressive and explicit language to convey their disappointment. The tone is highly negative and confrontational, with no responses or attempts at resolution visible in the thread. The lack of engagement from other participants and the user's emotional outburst suggest a potential for escalation if further comments occur.
-
- Toxicity Score: 0.65 (Rapid escalation, accusatory tone, lack of moderation)
- This GitHub conversation involves a single user expressing frustration and accusing another party of dishonesty, with a tone that is confrontational and insistent. There are no replies or further comments to moderate or de-escalate the tension, leaving the initial sentiment unchallenged. The lack of interaction and the accusatory language suggest a potential for increased toxicity if the conversation continues.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
- This GitHub conversation consists of a single initial comment by one user expressing frustration and impatience towards the development team, using a confrontational and disrespectful tone. There are no responses or further interactions to moderate or de-escalate the situation.
-
- Toxicity Score: 0.65 (Rapid escalation, accusatory tone, expressions of frustration)
- This GitHub conversation involves a user expressing increasing frustration and dissatisfaction with the unresolved issue, criticizing the handling and communication from the maintainers, while another comment echoes the sentiment of feeling unfairly restricted despite willingness to pay. The tone is accusatory and impatient, triggered by repeated rate limiting and perceived lack of effective response.
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: 75
Key Open Pull Requests
1. Adding commandLineRewriter to wrap commands with sandboxing args in sandboxed mode.: This pull request introduces a commandLineRewriter utility to enable sandboxing by wrapping terminal commands with sandboxing arguments in sandboxed mode, along with various code refactorings, test updates, and build fixes to support this functionality.
- URL: pull/289172
- Associated Commits: 40882, 0b15f, 1084d, c0b67, b1976, a7ce3, 63cac, caf2c, 5c216, cd711, 762aa, 51472, 697f4, 353d9, b6341, 94f31, a8b41, f4e9d, 49aea, 31ea4, 10ce4, 02fec, 22c6a, 544d6, 5b01c, dd41b, 47426, 4adb2, aa394, 1e046, e35e5, 2ed1d, 46534, 07dc6, 6be9a, bdd4f, b1f7c, 5ebef, ae761, afe39, b49c8, 820b1, 7833a, 4661c, 5484e, 18647
2. Metered network connections support: This pull request introduces comprehensive support for metered network connections in Visual Studio Code by adding 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, resuming them automatically once the connection is no longer metered.
- URL: pull/288919
- Associated Commits: aac9f, 44de2, b829d, 94dc0, 2ec39, cc851, 4c11d, fd376, a5a86, 24739, d8888, 6a04d, 16e8a, 41f70, 9b55a, 8a3ed, 3646c, 9e349, ada36, 521a3, 1ddd8, 0f267
3. [WIP-experimenting] Add question feature: This pull request introduces a question carousel feature to enhance user interaction within chat responses by allowing users to navigate through multiple questions, submit answers, and includes event handling, data structures, and improvements such as logging, auto-skip, answer restoration, and ignore functionality.
- URL: pull/289568
- Associated Commits: 24805, 64075, b5098, 63aff, 9ea35, 0ac36, e517e, 8365f, 23957, a167a, 11b42, 24d91, e2fae, bc2c7, 4248c, 3facf, c0cae, 41ebd, 89d3d
Other Open Pull Requests
- Chat agent model and implementation improvements: Multiple pull requests enhance the chat agent model by implementing the
chat.implementAgentModelfeature, refining agent model descriptions, filtering user-selectable modes, and improving setting checks. Additional updates include support for collapsed subagents with inline status, inline actions, hiding options from the model picker, and enabling custom agent model arrays with fallback logic for robust handling. - pull/289751, pull/289532, pull/289482, pull/289655
- Chat session and completion enhancements: Pull requests address chat session persistence by migrating sessions on workspace ID changes and improve the global chat completion menu by filtering slash commands from chat participants unless actively engaged. These changes ensure session continuity and a cleaner user experience in chat completions.
- pull/289779, pull/289732
- Code formatting fixes and tracking improvements: Several pull requests fix bugs related to the Format Document command, including timing issues causing undefined names and missing provider IDs in format edits. They also introduce draft enhancements for source edit tracking by expanding provider and extension ID coverage.
- pull/288934, pull/288953, pull/289177
- Editor and UI customization updates: Updates include new color tokens for activity bar hover states to improve icon visibility, a new setting for chat editor associations to configure editors by file glob patterns, and concise text updates on the Integrated Browser's New Tab page shown only to AI-enabled users. These changes enhance user interface customization and clarity.
- pull/289493, pull/289760, pull/289177
- Bug fixes and stability improvements in editor and UI behavior: Fixes include resolving flickering when deleting lines by updating line heights, addressing a race condition causing out-of-sync model line projections with guard checks, and preventing unintended rename actions on macOS file explorer by capturing keyup events. These ensure smoother and more stable editor interactions.
- pull/289256, pull/289250, pull/288498
- New commands and inline chat actions: A new command
workbench.action.chat.runCodeReviewis added for direct code review invocation, and a dynamic inline chat gutter action is introduced that switches between adding selection to chat and sending to active chat session based on input presence. These features streamline chat and code review workflows. - pull/289732, pull/289934
- Agent detection and filtering enhancements: The agent detection logic is improved by filtering out
README.mdfiles from custom agents in the.github/agents/directory, ensuring these files serve only as documentation and do not appear in the agent picker dropdown. This maintains support for other markdown agent files with added tests for verification. - pull/289043
- Build, dependency, and environment updates: Updates include sourcing codicons directly from the node module with build and pipeline fixes, adding an engines field to package.json to specify required Node.js and npm versions, and adding garbage collection for unused askpass directories to prevent storage bloat. These changes improve build reliability and environment compatibility.
- pull/289705, pull/289723, pull/289018
- Shell integration and AI model guidance: Integration support for the Xonsh shell is added to enable running recent commands from current and previous sessions. Additionally, AI model descriptions for the run in terminal tool are updated to instruct avoiding the
timeoutcommand in favor of the tool's built-in timeout parameter, improving command reliability. - pull/289481, pull/288442
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: 467
Key Closed Pull Requests
1. Support metered connections for updates, extensions, Git, telemetry, settings sync, and ExP with API and user settings: This pull request implements metered connection detection and handling across VS Code’s update service, extension auto-updates, Git operations, telemetry upload, settings sync, and ExP polling by introducing a new API and user setting that postpone or skip bandwidth-intensive automatic network operations when on metered connections such as mobile data or tethering, thereby reducing data usage and providing extensions with the ability to detect metered connections via a proposed vscode.env.isMeteredConnection() API.
- URL: pull/288294
- Associated Commits: fb720, 2c5ca, 38fb8, 18cd7, 0a0ad, 2d6a8, a7838, 60a0d, a9757, 23375, f68f4, b9279, 54122, a29fe, f2a54, ca452, 898ad, 06870, 046bd, 3e1c4, c6007, 6538d, e8101, cdba1, bbf9e, 033a1, dfcb9, f0a36, 73406, cbcd1, 0979d, b93c5, f4d87, 7a163, 2d9c6, b098a, 87e08, e616a, 8c060, 10f91, 6e5b8, 3a7f9, 42cc3, 549b1, 0aa2f, eca92, 45ffd, 11373, d43d6, 0f3dc, c708c, 46f20, 5a3c3, 9b016, ec98d, b3980, 98017, 4c2c2, 83318
- Associated Commits: fb720, 2c5ca, 38fb8, 18cd7, 0a0ad, 2d6a8, a7838, 60a0d, a9757, 23375, f68f4, b9279, 54122, a29fe, f2a54, ca452, 898ad, 06870, 046bd, 3e1c4, c6007, 6538d, e8101, cdba1, bbf9e, 033a1, dfcb9, f0a36, 73406, cbcd1, 0979d, b93c5, f4d87, 7a163, 2d9c6, b098a, 87e08, e616a, 8c060, 10f91, 6e5b8, 3a7f9, 42cc3, 549b1, 0aa2f, eca92, 45ffd, 11373, d43d6, 0f3dc, c708c, 46f20, 5a3c3, 9b016, ec98d, b3980, 98017, 4c2c2, 83318
2. Add skill provider API: This pull request adds support for skills in the provider extension API of the Visual Studio Code project, enabling extensions to integrate and manage skill providers more effectively.
- URL: pull/287948
- Associated Commits: 57e64, 241e7, 424a1, dc955, 696ef, 24417, 112dc, 25cd7, 1ca39, 1600c, 88bc6, d31d7, 4dd99, 63202, 3ce36, 5a440, 846fa, de3f0, bc3dc, 50f71, d334a, 05784, d2835, 36346, 2617d, 44f55, f4e9b, c0909, e5901, abd9e, a5eec, c50fc, f07a6, d93cd, 5512b, 04a7f, 72006, 0ac49, f7185, 27d41, d4c09, b4a9c, a73bc, d041e, 1fc91, da0aa, 16fe6, 87214, d535d, 8d69d, bd557, 924d1, d0ac7, 79b30, 72b56, 73735, 27a5a, fb364
- Associated Commits: 57e64, 241e7, 424a1, dc955, 696ef, 24417, 112dc, 25cd7, 1ca39, 1600c, 88bc6, d31d7, 4dd99, 63202, 3ce36, 5a440, 846fa, de3f0, bc3dc, 50f71, d334a, 05784, d2835, 36346, 2617d, 44f55, f4e9b, c0909, e5901, abd9e, a5eec, c50fc, f07a6, d93cd, 5512b, 04a7f, 72006, 0ac49, f7185, 27d41, d4c09, b4a9c, a73bc, d041e, 1fc91, da0aa, 16fe6, 87214, d535d, 8d69d, bd557, 924d1, d0ac7, 79b30, 72b56, 73735, 27a5a, fb364
3. Add hover options for ActionList, implement for chat model picker: This pull request adds hover support infrastructure to the ActionList component by introducing the IActionListItemHover interface, implements detailed model descriptions with localized strings in a new modelDescriptions.ts file, integrates hover functionality into the chat model picker to display descriptions and actions on keyboard focus and mouse hover, and enhances the model selector with a search parameter to open the models management editor pre-filled for the "Show more" action.
- URL: pull/288426
- Associated Commits: 98e15, 0d172, a73b6, 72b5f, 3cd78, cca25, 40d1f, 69c19, 6be67, 9286e, 32f87, 45695, 0407d, 6122f, 29667, dbbf5, 37837, 56f4f, 1a9e3, c337a, 1fe0a, 098e7, a7432, 56467, d1c44
- Associated Commits: 98e15, 0d172, a73b6, 72b5f, 3cd78, cca25, 40d1f, 69c19, 6be67, 9286e, 32f87, 45695, 0407d, 6122f, 29667, dbbf5, 37837, 56f4f, 1a9e3, c337a, 1fe0a, 098e7, a7432, 56467, d1c44
Other Closed Pull Requests
- Chat UI and Interaction Enhancements: Multiple pull requests improve chat-related features in VS Code by adding a gutter-based edit menu for inline chat actions, refining chat list rendering with interactive previews, and cleaning up chat row layouts to reduce flickering and autoscroll issues. These changes optimize user interaction with chat sessions and improve performance and visual consistency.
- Agent Sessions and Projection Improvements: Several pull requests focus on the agent sessions feature by introducing a prototype agent sessions window, improving recent sessions list management, refining agent control and projection logic, and fixing projection mode behavior during chat sessions. These updates enhance session usability, UI polish, and session state handling.
- Update and Platform Support Enhancements: Updates to platform-specific services include enabling Windows version update features for stable releases and improving DarwinUpdateService to better handle update states and errors. These changes aim to streamline the update process across different operating systems.
- Terminal and Debugging Features: Pull requests improve terminal usability by adding a "Continue in Background" button to the terminal progress toolbar and removing winpty support by updating node-pty, which enhances terminal handling on Windows. Debug toolbar integration with agent status and clickable status badge filters also improve debugging workflows.
- pull/287840, pull/288491, pull/289025, [pull/289927](https://github.com/pull/289927]
- Code Refactoring and Service Improvements: Refactoring efforts include implementing a post-rename refactoring service for NES, consolidating symbol rename tracking, and exposing MCP server definitions to the extension host for better integration. These changes improve code maintainability and service interoperability.
- UI and Theme Enhancements: Visual improvements are made by updating UI theme colors, hover effects, scrollbar colors, and increasing contrast in debug and status bar widgets to enhance readability and consistency across the application.
- Configuration and Build Process Updates: New settings such as includeReferencedInstructions and includeApplyingInstructions are introduced along with tests, and the build process is improved by integrating copying of the codicons file to ensure necessary icon assets are included during compilation.
- Performance and Resource Optimization: Lazy rendering for collapsible chat tool parts defers initialization until expansion to reduce resource usage, and polling and output expansion logic improvements prevent UI glitches and empty space flashes in embedded chat terminals.
- Context and Usage Tracking Enhancements: The context usage widget is refined by relocating it to the title area and powering it through the extension API to provide detailed chat result usage information and enable contributable actions for better context 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 | 549 | 121 | 0 | 558 |
| bpasero | 155 | 42 | 37 | 30 |
| Tyriar | 121 | 9 | 48 | 18 |
| dmitrivMS | 169 | 5 | 2 | 18 |
| roblourens | 93 | 26 | 18 | 46 |
| meganrogge | 107 | 16 | 16 | 35 |
| sandy081 | 97 | 29 | 5 | 6 |
| pwang347 | 110 | 9 | 5 | 7 |
| joshspicer | 77 | 18 | 2 | 18 |
| lszomoru | 68 | 27 | 0 | 6 |