Weekly GitHub Report for Vscode: November 24, 2025 - December 01, 2025 (12:00:53)
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.
-
CHAT file change incorrect +0 -0: This issue reports a bug where the Copilot Agent in VS Code marks files as "Changed" without showing any actual line differences (+0 -0), which started occurring after a change in how updates are bound—from per prompt to per chat. The user provides detailed logs, screenshots, and troubleshooting steps, expressing frustration with the lack of effective support and the impact on their workflow, while also requesting escalation and ownership of the issue.
- The comment thread reveals escalating user frustration due to unhelpful support responses and repeated troubleshooting attempts that fail to resolve the problem; the user shares extensive logs and screenshots, suspects UI changes like the new "Keep/Review" feature as a cause, and requests assignment of a responsible party, emphasizing the issue’s severity and their consideration of a refund.
- Number of comments this week: 16
-
Failed to get a response. Please try again.: This issue describes a problem where users experience a "Failed to get a response. Please try again" error when switching from a corporate GitHub account to a free GitHub account in VS Code Insiders, specifically when trying to use the chat feature. The user can reproduce the issue consistently even after restarting or reloading VS Code Insiders, and the comments include attempts to diagnose the problem through logging, error investigation, and intermittent repro states.
- The discussion reveals that the error may be related to command registration conflicts and agent activation failures, with suggestions to enable trace logging for deeper diagnostics. The issue is intermittent, with some users unable to reproduce it consistently, and developers are working on improving error logging and gathering more detailed information to identify the root cause.
- Number of comments this week: 7
-
Claude Opus 4.5 summarizes history at every step: This issue describes a bug where the Claude Opus 4.5 model begins summarizing the entire conversation history after every step during a chat session, which significantly slows down response times. The problem consistently occurs after some interaction and can only be temporarily resolved by starting a new chat session.
- The comments confirm the issue persists across different VS Code versions and is reproducible, with some users noting that the summarization compaction occasionally succeeds after multiple failures. Participants request logs and traces to diagnose the problem further, and it is acknowledged as specific to the Opus 4.5 model, with interest in seeing if other models exhibit similar behavior.
- Number of comments this week: 7
-
Using MCP tools that produce a lot of output results in listener leaks and poor responsiveness: This issue describes a bug where using MCP tools that generate a large amount of output in the chat causes Visual Studio Code to slow down significantly and emit warnings about potential listener leaks, indicating resource management problems. The user provides detailed logs showing thousands of event listeners accumulating, which leads to poor responsiveness and unresponsive extension host behavior, and shares a minimal MCP tool example that reliably reproduces the problem.
- The comments include detailed console logs evidencing listener leaks and extension host unresponsiveness, attempts to upgrade VS Code to a newer version which did not resolve the issue, confirmation that the problem persists in fresh chat sessions, and the creation and sharing of a simple dummy MCP tool script that consistently triggers the listener leak and performance degradation.
- Number of comments this week: 7
-
Use hover service not
titlefor hovers in models and agent dropdown: This issue discusses replacing the use of the nativetitleattribute for hover tooltips in models and agent dropdowns with a more advanced hover service to achieve better styled and positioned hover displays. The reporter provides visual examples of the desired hover behavior and references relevant code sections, seeking guidance on how to transition from the current tooltip implementation to the hover service.- The comments reveal some confusion about whether the
titleattribute is currently used, with references to various hover delegate implementations and code snippets. Participants investigate the source of the tooltip behavior, noting thattitleseems to be set in the rendering process, and request input from code owners to suggest how to properly integrate the hover service instead of relying on native tooltips. - Number of comments this week: 6
- The comments reveal some confusion about whether the
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 titles in the output of code cells. The requester highlights that this functionality would allow dynamic content generated by code to be included in the outline view, improving usability and aligning VS Code's behavior with JupyterLab.
- 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 toprocess, causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}produces malformed paths like/c:/Users/myuser/myfolder/my.exe, using${env:USERPROFILE}correctly resolves to a valid Windows-style path, indicating a discrepancy in how these variables are expanded depending on the task type and shell environment.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where the terminal in a floating window does not echo typed characters in real time when connected to a remote environment, such as WSL or SSH, if the main VS Code window is minimized. The characters only appear after restoring the main window, indicating a communication delay likely caused by the remote connection entering a "sleep" state when the main window is minimized, which does not get resolved by simply focusing the floating terminal window.
- 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: 504
Summarized Issues:
- Extension response failures and no output: Multiple issues report that various versions of the VS Code extension (notably 0.33.2 and 0.33.3) fail to generate any response or output when invoked, causing user frustration and wasted premium requests. These failures occur across different platforms including Windows 10, Darwin arm64, and Linux, often accompanied by errors such as truncated responses, premature stopping, or indefinite hanging without completing tasks.
- issues/279037, issues/279046, issues/279084, issues/279116, issues/279166, issues/279285, issues/279450, issues/279556, issues/279573, issues/279825, issues/279826, issues/279878, issues/279881, issues/279854, issues/279760, issues/279750, issues/279789, issues/279799, issues/279820, issues/280020, issues/280026, issues/280027, issues/280038, issues/280056, issues/280070
- Agent destructive behavior and data loss: Several critical bugs describe agents or Copilot extensions deleting files or directories without user confirmation, causing severe data loss and user distress. These destructive actions include deleting entire project directories, removing important files like pubspec.yaml, and merging or deleting branches without approval, highlighting a lack of safeguards and the need for explicit user consent and backup mechanisms.
- issues/279042, issues/279049, issues/279168, issues/279171, issues/279188, issues/279491, issues/279868, issues/280008, issues/280017, [issues/280018](https://github.com/issues/280018]
- Chat response truncation and incomplete outputs: Multiple issues report that chat responses from the Copilot extension or AI models are prematurely truncated mid-sentence or mid-code block, resulting in incomplete answers and user frustration. This truncation affects various models and versions, often requiring users to reload or switch history views to see full responses, indicating UI or streaming issues.
- issues/279047, issues/279074, issues/279291, issues/279311, issues/279482, issues/279586, [issues/279700](https://github.com/issues/279700]
- Authentication and login loops: Users frequently experience issues with GitHub Copilot login, including persistent login loops, failure to authenticate, and inability to sign up or connect to development environments. These problems prevent successful use of the extension and require repeated sign-in attempts or reinstallations without resolution.
- issues/279498, issues/279551, issues/279742, issues/280052, issues/280053, [issues/279975](https://github.com/issues/279975]
- Model endpoint availability and plan restrictions: Several issues report errors indicating "no endpoints available for this model under your current plan and policies," preventing users from accessing premium or specific AI models despite having active subscriptions. This results in failed requests and inability to use desired features, causing confusion and dissatisfaction.
- issues/279896, issues/279906, issues/279911, issues/279929, [issues/279930](https://github.com/issues/279930], [issues/279925](https://github.com/issues/279925]
- Performance and unresponsiveness: Numerous reports describe the VS Code extension or the editor itself becoming unresponsive, freezing, or exhibiting severe performance degradation. These include high CPU or memory usage, slow response times, and crashes triggered by large files, complex projects, or specific extension interactions, severely impacting usability.
- issues/279160, issues/279371, issues/279372, issues/279492, issues/279589, issues/279689, issues/279711, issues/279761, issues/279830, [issues/279859](https://github.com/issues/279859], issues/279867, issues/279977, [issues/280093](https://github.com/issues/280093]
- Agent and Copilot chat hangs or infinite loops: Several issues describe the Copilot chat or agent mode hanging indefinitely, entering infinite loops, or failing to progress during tasks such as terminal command execution, file reading, or conversation summarization. These stalls prevent completion of user requests and require manual intervention.
- issues/279056, issues/279244, issues/279552, issues/279790, issues/279861, [issues/280059](https://github.com/issues/280059]
- Incorrect or misleading code generation and editing: Users report that Copilot or agents generate incorrect, misplaced, or hallucinated code, including erasing valid code, inserting code outside method bodies, or producing logically flawed snippets. These issues degrade trust and require manual correction.
- issues/279064, issues/279066, issues/279219, issues/279390, issues/279598, [issues/279936](https://github.com/issues/279936]
- UI and interaction bugs in chat and editor: Various UI problems affect chat mode selection, inline chat behavior, toolbar icon visibility, and terminal interactions. These include missing buttons, overlapping menus, incorrect icon rendering, and inability to close or switch chat tabs, which disrupt user workflows.
- issues/279075, issues/279276, issues/279433, issues/279803, issues/279809, [issues/279810](https://github.com/issues/279810], issues/279493, [issues/279937](https://github.com/issues/279937], [issues/279775](https://github.com/issues/279775]
- Network and SSL errors: Users encounter network-related errors such as SSL handshake failures, connection resets, and certificate name mismatches that prevent the extension from communicating with servers or fetching models. These issues often relate to firewall or proxy configurations.
- issues/279087, issues/279566, issues/279749, issues/280029, issues/280068, issues/280083, [issues/280947](https://github.com/issues/279947]
- Feature requests for improved usability and customization: Users request features such as confirmation dialogs before starting new chats, toggles for voice mode, richer chat formatting with Markdown, increased session history limits, and better terminal integration including local terminal support during remote sessions. These aim to enhance control, accessibility, and workflow efficiency.
- issues/279053, issues/279196, issues/279829, issues/279560, issues/279354, [issues/279671](https://github.com/issues/279671]
- Model and tool integration issues: Problems include inability to override model endpoints per container, failure to fetch or recognize local models, and issues with MCP server tool naming and dynamic client registration, causing integration and compatibility challenges.
- issues/279356, issues/279832, issues/279935, [issues/279955](https://github.com/issues/279955]
- Code editor and language support bugs: Issues include incorrect syntax highlighting, bracket matching errors, incomplete inline completions, and problems with language-specific features such as LaTeX RTL text rendering and PHP syntax highlighting, affecting code readability and editing accuracy.
- issues/279225, issues/279508, issues/279576, [issues/279756](https://github.com/issues/279756], issues/279675, [issues/279714](https://github.com/issues/279714]
- Terminal and shell integration problems: Users report issues with terminal focus, command execution, terminal suggestions ignoring input, and inability to open local terminals during remote SSH sessions, disrupting command-line workflows within VS Code.
- issues/279380, issues/279381, issues/279577, issues/279549, [issues/279771](https://github.com/issues/279771], [issues/280025](https://github.com/issues/280025]
- Memory leaks and resource disposal issues: Several reports indicate listener leaks and improper disposal of resources in chat renderers and other components, leading to degraded performance and potential crashes over time.
- issues/279299, issues/280101, issues/279624, [issues/279859](https://github.com/issues/279859]
- Miscellaneous bugs affecting usability: Additional issues include problems with search flags for Cyrillic text, broken inline chat keyboard shortcuts, missing toolbar icons, and problems with extension recommendations and sorting, all contributing to a less smooth user experience.
- issues/279361, issues/279368, issues/279091, [issues/279533](https://github.com/issues/279533]
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: 605
Summarized Issues:
- Model and API Access Errors: Many issues report failures due to "no endpoints available for this model under your current plan and policies," causing 400 errors and preventing users from accessing or using specific AI models despite having active subscriptions or premium plans. These errors affect various models including Claude Sonnet 4.5, Gemini 3 Pro, and GPT-5, leading to failed requests, inability to generate responses, and user frustration over disrupted workflows.
- issues/279873, issues/279874, issues/279875, issues/279879, issues/279882, issues/279883, issues/279884, issues/279885, issues/279886, issues/279887, issues/279889, issues/279890, issues/279891, issues/279892, issues/279893, issues/279894, issues/279895, issues/279897, issues/279898, issues/279899, issues/279902, issues/279904, issues/279905, issues/279907, issues/279908, issues/279912, issues/279914, issues/279915, issues/279916, issues/279917, issues/279918, issues/279919, issues/279923, issues/279927, issues/279928
- Extension Non-Responsiveness and Failure to Return Output: Numerous reports describe the VS Code extension or Copilot Chat failing to respond, returning no output, or abruptly cutting off responses mid-sentence, causing users to lose work and requiring restarts or retries. These issues occur across multiple OS platforms and extension versions, often accompanied by error messages like "Sorry, no response was returned" or indefinite hangs during code generation or chat interactions.
- issues/277807, issues/277820, issues/277838, issues/278012, issues/278076, issues/278077, issues/278079, issues/278080, issues/278086, issues/278087, issues/278090, issues/278091, issues/278092, issues/278093, issues/278098, issues/278200, issues/278228, issues/278343, issues/278344, issues/278402, issues/278413, issues/278414, issues/278664, issues/278805, issues/278808, issues/278849, issues/279186, issues/279290, issues/279343, issues/279496, issues/279557, issues/279558, issues/279664, issues/279728, issues/279849, issues/279954
- Network and Connection Errors: Many users experience network-related errors such as "net::ERR_CONNECTION_RESET," "net::ERR_CONNECTION_CLOSED," and "socket hang up," which cause interruptions in the extension's functionality and prevent successful communication with AI services. These issues often require users to check firewall rules, network connectivity, or retry operations, and affect various platforms including Windows, macOS, and Linux.
- Performance and Responsiveness Issues: Several issues describe significant performance degradation, including long delays, freezing, sluggishness, and unresponsiveness in VS Code or its extensions, especially during code navigation, chat interactions, or large repository operations. These problems affect various OS platforms and hardware configurations, sometimes linked to token usage, extension behavior, or large context windows.
- Bugs in Chat and Inline Chat Features: Multiple reports highlight bugs in chat features such as chat history truncation, incorrect chat window behavior, missing or incorrect UI elements, failure to apply changes, and issues with model selection or tool calling. These bugs disrupt user workflows by causing confusion, loss of context, or inability to complete chat-based coding tasks.
- Token Usage and Rate Limiting Problems: Users report excessive token consumption, unexpected rate limiting, and inability to extend or purchase additional usage despite having budgets or subscriptions, leading to interruptions in AI-assisted coding and frustration over wasted tokens or blocked requests.
- Bugs Related to Specific Models (Gemini, Claude, GPT-5): Several issues describe model-specific problems such as Gemini 3 Pro returning 400 errors, Claude Sonnet 4.5 failing with bad requests or incomplete responses, and GPT-5 models hanging, refusing requests, or producing flawed outputs. These issues cause degraded user experience and require workarounds or model switching.
- UI and Rendering Issues: Users report UI glitches including flickering, broken rendering after system sleep, incorrect text direction for RTL languages, misaligned icons, and broken keyboard shortcuts, which impair usability and visual clarity in VS Code.
- Authentication and Subscription Issues: Some users experience problems with authentication, subscription recognition, or token permissions, resulting in inability to use Copilot features despite having valid accounts or purchased plans.
- Buggy or Missing Features and UI Elements: Reports include missing commit buttons, broken or missing confirmation prompts, inability to toggle features, and UI elements not appearing or functioning as expected, which hinder normal workflows.
- issues/274773, issues/277974, issues/276453, issues/276994, issues/278044, [issues/278343](https://github.com/issues/278343], issues/278344, issues/279763, issues/279764, issues/279765
- Code Generation and Editing Failures: Several issues describe the AI indicating it has made code changes or applied fixes but failing to actually modify files, or generating corrupted, incomplete, or erroneous code, causing confusion and wasted effort.
- Crash and Infinite Loop Bugs: Some reports detail crashes of the extension host or VS Code itself, infinite loops in the AI agent or extension processes, and fatal errors causing the editor to become unusable until restarted.
- issues/276178, issues/276230, issues/277392, issues/278522, issues/278581, issues/278691, issues/279696, issues/279890, [issues/279951](https://github.com/issues/279951]
- Feature Requests and Usability Improvements: Users request enhancements such as togglable commands for editor features, better prompt management, improved dark mode support, context window indicators, and more intuitive UI behaviors to improve the overall user experience.
- Subscription and Billing Complaints: Some users express frustration over billing issues, such as being charged for failed or incomplete requests, inability to extend usage despite payment, or unexpected subscription downgrades impacting access to features.
- Localization and Language Support Issues: A few issues report problems with language-specific features such as inability to create launch configurations in Simplified Chinese, misrendering of bidirectional punctuation in RTL languages, and incorrect syntax highlighting for certain languages.
- Miscellaneous Bugs and User Complaints: Various other issues include complaints about poor AI performance, requests for corporate contact due to dissatisfaction, and reports of unexpected or unexplained behavior in the extension or VS Code.
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.
-
Agent Claude 4.5 just calling me a liar
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, strong emotional outburst)
- This GitHub conversation involves a single user expressing intense frustration and anger towards an automated agent, accusing it of dishonesty and incompetence. The tone is highly emotional, with repeated use of strong language and expletives, indicating a high level of dissatisfaction and tension. There are no other participants or responses in the conversation to moderate or escalate the sentiment.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, high emotional intensity)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger towards an issue that caused significant data loss, using harsh language and demanding a fix. There are no responses or further comments, so the tone remains highly negative but unchallenged or escalated by others. The trigger of tension is the severe impact on the user's project and the perceived irresponsibility of the software.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by a user expressing strong frustration and dissatisfaction with the software's performance and adherence to instructions, using highly negative and aggressive language. There are no responses or further interactions, so the tone remains one-sided and tense without escalation or resolution.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger towards a software product, using offensive language and derogatory terms. The tone is highly negative and aggressive, with no subsequent comments or attempts at resolution visible. The lack of engagement or moderation suggests potential for escalation if others respond.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation involves a user expressing strong dissatisfaction and frustration towards the handling of issues and perceived lack of meaningful responses from the maintainers, with a tone that is accusatory and critical. The initial complaint is detailed and formal but conveys a sense of disappointment and distrust, while the subsequent comment escalates the negativity with dismissive and derogatory language. The interaction shows a clear trigger of tension rooted in perceived inadequate support and communication.
-
No sabes ni documentar lo básico.
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and dissatisfaction with the product, using aggressive and profane language. There are no responses or further interactions, so the tone remains unchallenged and the conversation does not develop.
-
it is full autonom,us this shit coding first without explaining what the fuck is doing!
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, hostile tone)
- This GitHub conversation consists of a single initial comment by a user expressing strong frustration and anger using profane language and an aggressive tone, without any subsequent replies or engagement from others. The sentiment is highly negative, and the language is hostile, indicating a potential for conflict if the discussion were to continue.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, high emotional intensity)
- This GitHub conversation consists solely of an initial feature request post by a single user expressing intense frustration and anger through aggressive language and profanity, with no subsequent comments or interactions from other users.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, lack of moderation)
- This GitHub conversation consists solely of an initial feature request posted by a single user expressing intense frustration and anger through aggressive language and profanity, with no subsequent comments or interactions from other users.
-
more of the same fucking trash
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and anger towards another party's tools and their impact, using aggressive and profane language without any responses or further interaction.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided communication)
- This GitHub conversation consists of a single user expressing intense frustration and dissatisfaction with the software, using highly aggressive and profane language without any responses or engagement from others. The tone is hostile and emotionally charged, with no signs of de-escalation or constructive dialogue.
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: 63
Key Open Pull Requests
1. Marketplace filter favourite: This pull request introduces a favorites system with heart icon badges, a context menu toggle, and an @favorites query filter for the Extensions Marketplace, along with new rating and download count filters (@minRating:N and @minDownloads:N) that support suffixes and dropdown menus, all integrated with user settings syncing and accompanied by unit tests.
- URL: pull/279485
- Merged: No
2. wip: update base buttons styles and strip overrides: This pull request aims to clean up and standardize the base styles of the Monaco text button component by adding a new small variant and removing numerous CSS overrides scattered throughout the codebase to simplify and unify button styling.
- URL: pull/279524
- Merged: No
3. feat(git): Use git mv for file renames and moves in explorer: This pull request implements support for using the git mv command when renaming or moving files through the VSCode explorer, controlled by a new git.autoStageOnMove setting, to preserve git history, maintain accurate blame information, show cleaner diffs, and improve statistics by detecting file moves as renames rather than delete/add operations.
- URL: pull/279722
- Merged: No
Other Open Pull Requests
- Memory Leak Fixes: Multiple pull requests address memory leaks in various components such as accessibility signals, terminal decoration addon, local process extension host, and terminal process. These fixes involve proper disposal of resources, nullifying listeners, and registering disposables to reduce memory usage and improve stability during repeated operations.
- Chat Service and UI Improvements: Several pull requests enhance the chat service and user interface, including chat service registrations, chat welcome view polish, chat session behavior improvements, chat session tracker removal, and chat input model filtering. These changes improve usability, consistency, and maintainability of chat features in VS Code.
- Export and Test Enhancements: One pull request adds a comprehensive export search results feature supporting multiple formats with progress and cancellation, while another adds detailed test coverage for handoff continueOn behavior by refactoring and extracting helper functions. These improve functionality and reliability of search and handoff features.
- Settings and Configuration Updates: Updates include fixing deprecated setting reset behavior in the Settings editor, adding a toggle to filter settings applied to all user profiles, enabling isolatedModule flag in TypeScript config with related fixes, and adding validation for ADMX/ADML files in Windows policy generation. These changes enhance configuration management and build correctness.
- Contribution and Analytics Features: Pull requests introduce contribution points for chat-related folders and a new "Usage Analytics" view in the Extensions sidebar to track extension activations and command executions locally, helping users manage resources and improve performance while preserving privacy.
- Chat Session Management and Menu Restrictions: Changes include restricting certain chat session menu actions to local sessions only and renaming the "History" group label to "Archived" for local chat sessions, improving clarity and consistency in session management UI.
- Miscellaneous Fixes and Tools: Other pull requests fix code block rendering in chat history, introduce an onboarding snippet generator CLI tool for new contributors, and optimize images and fix typos across documentation and templates to improve performance and clarity.
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: 215
Key Closed Pull Requests
1. agent sessions - chat view layout fixes: This pull request addresses layout fixes in the chat view of agent sessions within the Visual Studio Code project, improving the user interface and removing unnecessary CSS overrides.
- URL: pull/279774
- Merged: 2025-11-27T14:18:00Z
- Associated Commits: 27574, e01cc, 9f7a3, 48b94, fa0fd, ac749, 6347d, cdb5a, 84148, 3ff1f, 4421f, c6da1, cf833, 54feb, dd0de
2. Resolve regression where build task did not start in wsl: This pull request resolves a regression in Visual Studio Code where the build task failed to start in the Windows Subsystem for Linux (WSL) environment due to the incorrect order of shell integration events and process creation, specifically addressing issues with the active workspace URI being undefined and ensuring proper handling of the current working directory in remote terminals.
- URL: pull/279249
- Merged: 2025-11-27T00:13:03Z
- Associated Commits: 06832, 4934f, b62f6, acffc, 95747, d5a5e, 0f490, 062ff, 6a8f6, 6b150, e9ea7, 889a9, 355a6, 2c403
3. Refactor watermark entry management and improve styling: This pull request refactors the management of watermark entries in the editor by simplifying their structure, removing unnecessary entries and styles, and introduces a toggle action for watermark visibility, while also improving the layout styling for better alignment and spacing to enhance the overall visual presentation.
- URL: pull/278758
- Merged: 2025-11-24T06:59:13Z
- Associated Commits: da623, f71db, f0d94, 7190f, eb3e3, 57d0f, c37ee, 7361c, 3aebb, d1e1b, 4776b, 52f8a
Other Closed Pull Requests
- Agent Sessions Feature Enhancements: Multiple pull requests improve the agent sessions feature by adding a dedicated service, supporting archiving and persistence of session states, and enhancing test coverage and code cleanup. Additional updates include visual improvements to session cards, fixes for display and layout issues in the chat view, session control refinements, and restoring the history functionality in the sessions view.
- Memory Leak Fixes: Several pull requests address memory leaks by properly managing event listeners and disposable resources. Fixes include correcting window event listener registration in toggle screencast mode, cleaning up disposal logic in ChatService, and removing event listeners in the historyService to prevent accumulation of unused functions.
- Chat Feature Refactoring and UI Updates: The chat feature is reorganized by moving setup into a dedicated function and modularizing code for maintainability, alongside updating the header with the chat title service and refactoring the chat list renderer to manage state per part. Visual updates and UI improvements are also applied to session cards and chat view elements.
- pull/279094, pull/279527, [pull/279967](https://github.com/pull/279967]
- Agent and Subagent Support Improvements: Enhancements include adding support for GitHub Custom Agents, fixing caching issues, and adding the ability to list and run agents as subagents with XML and tool variable instructions.
- Build and CI Configuration Updates: Changes include enabling BinSkim scanning on Linux build agents while removing unused macOS configurations, and proposing a Deno CI workflow for linting and testing that was not merged.
- Git and SCM Feature Enhancements: Updates add a "Stashes" node to the Git repositories view with additional stash management features and improve the SCM feature by adopting a delayed hover setup to enhance mouse hover behavior.
- Inline Suggestions and Symbol Renaming: Support for inline suggestions enabling symbol renaming directly in the editor is introduced, along with comprehensive tests for the renameSymbolProcessor to improve reliability and correctness.
- Fetch Tool Improvements: Various bug fixes and enhancements improve the fetch tool's heuristics for dynamic pages, caching strategies, result data richness, and website compatibility, allowing successful loading of previously problematic sites.
- Removal of Features and Settings: The history feature is removed from the chat view in agent sessions, and the background agent setting is removed along with related code and test fixes.
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 | 467 | 76 | 0 | 544 |
| bpasero | 277 | 46 | 114 | 149 |
| meganrogge | 320 | 4 | 62 | 191 |
| Tyriar | 119 | 4 | 78 | 179 |
| roblourens | 97 | 15 | 49 | 184 |
| lszomoru | 133 | 14 | 18 | 80 |
| mjbvz | 129 | 15 | 37 | 58 |
| jrieken | 63 | 11 | 38 | 88 |
| aeschli | 79 | 9 | 15 | 90 |
| connor4312 | 72 | 7 | 22 | 89 |