Weekly GitHub Report for Vscode: September 22, 2025 - September 29, 2025 (12:05:11)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
The version released on March 12, 2025, primarily focuses on resolving various issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." For a comprehensive overview of all updates and improvements, users are directed to the official release notes on the Visual Studio Code website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
VScode crash: This issue reports frequent crashes of VS Code, specifically related to the extension host or Copilot Chat, which result in numerous files becoming empty and effectively lost, causing significant data loss for the user. The user describes losing over 226 files after a crash triggered while interacting with the model, and despite autosave being enabled, the files were overwritten with blank content and could not be recovered from Git or logs.
- The discussion clarifies that the crash is likely related to the extension host rather than the entire VS Code window closing, with the user explaining that their GitHub repo is full and cannot accept pushes, complicating recovery. The user provides detailed context about the crash symptoms, file loss, and extension refresh behavior, while maintainers request logs and further information to diagnose the issue, noting the absence of crash logs and the difficulty in reproducing the problem without more data.
- Number of comments this week: 9
-
Enable discoverability of language model BYOK providers: This issue requests a feature to improve the discoverability of language model Bring Your Own Key (BYOK) providers by enabling users to search for these providers in the marketplace, similar to how VS Code allows searching for notebook kernels. The proposal includes adding a "BYOK" tag and possibly integrating a marketplace query or using a service like unpkg to fetch and display available providers within the Manage Models action.
- The comments show agreement on the feature's value and mention prior discussions on the topic. Contributors express openness to accepting a pull request, discuss potential implementation approaches including marketplace queries and unpkg service usage, and emphasize a seamless user experience where users cannot distinguish between built-in and marketplace providers.
- Number of comments this week: 7
-
Microsoft Authentication repeatly asks for sign in: This issue reports that Microsoft Authentication in VS Code repeatedly prompts the user to sign in again after an initial successful login, despite no recent password changes or expirations. The user provided logs showing errors related to invalid or expired sessions with Azure AD, and Microsoft support requested detailed authentication runtime logs to diagnose the problem further.
- The comments include error logs indicating session invalidation due to reasons like expired SSO artifacts or invalid tokens, the user confirming no password changes occurred, and detailed instructions from Microsoft on how to collect and submit authentication runtime logs using provided PowerShell scripts; the user then ran these scripts and shared the output, facilitating deeper investigation by the support team.
- Number of comments this week: 6
-
Code executable, High GPU usage on Windows: This issue reports unusually high GPU usage by the VS Code application on Windows when the window is maximized, particularly noting that GPU usage drops significantly when the window is minimized or resized smaller. The user suspects a rendering problem linked to the GitHub Copilot Chat sidebar, where an active spinner causes sustained high GPU utilization, and requests a way to disable GPU acceleration as a potential workaround.
- The comments clarify that high GPU usage with larger window sizes is expected due to GPU-accelerated rendering, and a related issue on macOS is not applicable to Windows. Further investigation narrows the cause to the GitHub Copilot Chat sidebar’s spinner animation, which is graphics-intensive and not well optimized, with suggestions to report the problem to the Copilot Chat repository for better handling.
- Number of comments this week: 6
-
Enable
window.autoDetectColorSchemeby default: This issue proposes enabling thewindow.autoDetectColorSchemesetting by default in VS Code, allowing the editor to automatically switch themes based on the user's environment. The suggestion includes migrating users who have no theme configured or use default light or dark themes to have this setting enabled, while others would have it disabled.- The comments discuss concerns about the default theme choice, especially on macOS where switching to a light theme by default might be unexpected. Participants consider running an experimental rollout to observe user behavior, note that the website already implements automatic theme detection, and explore technical possibilities for detecting system preferences, including macOS-specific settings.
- Number of comments this week: 6
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request asking for the ability to display markdown generated by code cells within the notebook outline, similar to how JupyterLab handles dynamic titles rendered in the output of code cells. The requester highlights that this functionality would allow outlines to reflect dynamically generated content, improving usability by showing code cell markdown in the outline view.
- 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 open a new window as expected, but instead hijacks and replaces the existing remote connection window. Specifically, when connected remotely to one server, clicking such a link to open a different remote server causes the current connection to disconnect and be replaced, rather than opening the new connection in a separate window.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set to "process," causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}works correctly when the task type is "shell" with PowerShell as the default shell, it produces malformed paths in the "process" type, and suggests that using${env:USERPROFILE}is a viable workaround since it generates valid paths.- 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, and the main VS Code window is minimized. The characters only appear after restoring the main window, indicating that the remote connection may enter a sleep state when the main window is minimized, preventing immediate communication with the terminal in the floating window.
- Unicode character displayed as a question mark ?: This issue reports that the fullwidth quotation mark Unicode character (U+FF02) is displayed as a question mark when pasted into Visual Studio Code, despite rendering correctly in browsers like Firefox. The problem persists even with all extensions disabled, indicating a potential bug in how VS Code handles or renders certain Unicode characters on Fedora 39 with version 1.87.2.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 458
Summarized Issues:
- Command Execution and Auto-Approve Issues: The "Always allow exact command line" auto-approve rule in the Copilot Chat Extension is too permissive, allowing appended commands with logical operators to run without explicit approval, which risks unintended command execution. Additionally, the terminal's auto-approve feature does not parse commands passed as arguments within shell executables, forcing users to over-approve entire shells or manually approve commands, reducing security and usability.
- Chat and Agent Mode Freezing or Unresponsiveness: Multiple reports indicate that the Copilot Chat or Agent mode in VS Code freezes indefinitely or becomes unresponsive after executing commands or during interactions, requiring manual termination or restart. This includes stalls after approving terminal commands, freezing in high-performance computing environments, and hanging after command completion without detecting command finish.
- Chat Message Sending and Response Failures: Users experience issues where messages disappear without sending, requests are not processed or visibly sent, or chat responses fail to appear, often accompanied by network errors or extension version problems. This affects multiple platforms and VS Code versions, causing significant disruption to chat functionality.
- Extension Version and Upgrade Problems: Several issues report persistent messages about needing upgrades despite using the latest versions, signature verification failures preventing extension functionality, and problems with extension loading or refusing valid requests. These problems affect user experience and extension reliability across platforms.
- Performance and Responsiveness Issues: VS Code and the Copilot extension suffer from severe performance degradation, including slow startup, high CPU usage, lag, and freezing, especially on certain hardware like Mac M1/M2 chips and Windows systems with RTX GPUs. These issues also include slow chat responses and extension readiness delays.
- Authentication and Sign-In Problems: Users face repeated authentication prompts, invalid or expired sessions, firewall blocking access, and inability to sign in to GitHub Copilot or related services, causing continuous failures and requiring detailed troubleshooting.
- Code Modification and Instruction Following Bugs: The Copilot extension often ignores explicit user instructions, modifies code unexpectedly, fails to apply requested changes, or corrupts files by treating notebooks as plain text. Users report repeated unwanted edits, failure to update code after prompts, and the agent falsely reporting completion without changes.
- New Chat and Chat Session Management Issues: Users cannot open new chats, experience chat windows that do not clear TODO lists, or get stuck in chat sessions that cannot be exited. There are also requests for features to create chat modes from current chats and to manage multiple parallel chat sessions.
- Keyboard Shortcut and Input Problems: Several bugs involve keyboard shortcuts not working or conflicting, such as tab key indent issues, missing pause buttons, shortcut conflicts causing loss of work, and input boxes smaller than recommended sizes affecting accessibility.
- Terminal and Shell Integration Bugs: Problems include terminal commands not fully clearing the screen, terminals closing unexpectedly during agent processes, inability to view terminals running tests, and issues with terminal intellisense and command execution in various shells and remote environments.
- issues/267725, issues/267770, issues/268053, issues/268149, [issues/268344](https://github.com/issues/268344], issues/268347
- Network and API Errors: Users encounter frequent network errors such as ERR_TUNNEL_CONNECTION_FAILED, ERR_CONNECTION_CLOSED, ERR_NETWORK_CHANGED, and 400 Bad Request errors, often related to specific models like Claude or during fetch tool operations, causing failures in chat requests and tool usage.
- File and Workspace Management Issues: Problems include files flagged as outside the workspace incorrectly, inability to view or search older chats, missing files in source control, and issues with multi-root workspace configurations and file explorer views.
- UI and Accessibility Problems: Issues include missing or misplaced buttons (pause, run, close sidebar), incorrect rendering of UI elements in different languages, focus and tab order problems, and accessibility concerns such as small input targets and screen reader misbehavior.
- Feature Requests for Improved Usability and Functionality: Users request features such as keyboard shortcut for "ask copilot," transferring chat sessions to remote agents, one-time payment options for billing, better tool set management, customizable terminal tabs, improved chat session APIs, accessible mode for Copilot Chat, and enhanced chat history UI.
- Model and AI Behavior Issues: Problems include the AI providing incomplete or nonsensical answers, leaking context from unrelated projects, switching languages unexpectedly, refusing to process requests, and failing to follow instructions properly, leading to user frustration and reduced trust in the tool.
- Crash and Data Loss Reports: Users report crashes causing loss of files, blank windows, and corrupted data, including notebooks being corrupted by the agent, VS Code crashing after sleep, and extension host crashes leading to empty files.
- Miscellaneous Bugs: Other issues include problems with icon colors, missing run buttons, incorrect hover tooltips, broken markdown validation, and problems with specific language features like folding or blame ignoring whitespace.
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: 275
Summarized Issues:
- Model Availability and Selection Issues: Several issues report problems with the availability and selection of AI models in the GitHub Copilot Chat extension for VS Code, including the disappearance of the "Model selection to Auto" option and Claude-related models, which disrupts user workflows and requires workarounds like downgrading the extension or proxy configuration. These issues significantly affect users' ability to access desired models and maintain productivity, especially in restricted network environments.
- Performance and Responsiveness Problems: Multiple reports highlight severe performance degradation in VS Code and its extensions, including typing delays of several seconds, editor freezes, slow token retrieval, and intermittent unresponsiveness of the Copilot extension. These issues cause significant hindrance to usability and user frustration, with some users describing the experience as a waste of time and money.
- 400 Errors and Request Failures in Extensions: A large cluster of issues report 400 Bad Request errors caused by invalid JSON formats, unexpected or missing tool_use_id blocks, invalid request bodies, or timeouts when downloading files or attaching images in the VS Code Copilot extension. These errors lead to failed requests, repeated retry attempts, and loss of data, severely impacting extension functionality and user experience.
- Copilot Subscription, Quota, and Rate Limiting Issues: Several users report problems with subscription recognition, quota enforcement, and rate limiting in GitHub Copilot, including inability to start free trials, unexpected quota exhaustion messages despite active subscriptions, and persistent rate limiting errors that block paid feature usage. These issues cause confusion and prevent users from fully utilizing their paid or trial access.
- Terminal and Shell Integration Bugs: Users report multiple issues with the integrated terminal in VS Code, including command errors on Windows 11, terminal input prompt discrepancies, failure to kill processes properly, terminal text duplication on resize, and unresponsive arrow keys in custom terminal profiles. These problems disrupt terminal workflows and cause confusion or resource conflicts.
- Chat and UI Focus/Accessibility Problems: Several issues describe bugs where focus is lost after closing accessibility views or dialogs, keyboard navigation is impaired in chat interfaces, tooltips are not announced by screen readers, and chat input focus is not retained as expected. These accessibility and UI focus issues degrade the user experience, especially for users relying on assistive technologies.
- Copilot Chat Extension Bugs and Crashes: Numerous reports detail bugs in the Copilot Chat extension such as chat disappearing unexpectedly, failure to respond or stuck waiting states, crashes after running shell scripts, and issues with copying selected text or tool selections persisting incorrectly. These bugs cause interruptions in chat workflows and loss of user input or context.
- Network and Connectivity Errors: Several issues report network-related errors such as "network changed" errors despite stable connections, connection resets, and firewall or proxy-related access problems, which cause failures in chat, extension requests, or downloads. These connectivity problems disrupt normal operation and require network configuration adjustments.
- Feature Requests for Enhanced Functionality: Users request new features including support for GPT-5-Codex model, API or commands to retrieve context memory usage, crypto coin reward systems, negative search filters in Extensions view, tab grouping with collapsible functionality, keyboard shortcuts for terminal break signals, and UI customization options for fonts and backgrounds. These requests aim to improve usability, monitoring, and customization of VS Code and its extensions.
- Extension and Tool Configuration Issues: Some issues describe problems with configuration settings such as MCP server visibility, custom relative path separators not respected in diff views, missing schema support for MCP settings in workspace files, and redundant API key prompts for Cerebras models. These configuration problems cause confusion and reduce efficiency in managing extensions and tools.
- Miscellaneous Bugs and User Complaints: Additional issues include bugs with import statement reordering breaking environment variables, inability to run C++ code properly, corrupted PHP files due to extension conflicts, and user complaints about intrusive AI features or privacy concerns. These diverse problems affect various aspects of the VS Code experience and user satisfaction.
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, emotional tone)
- This GitHub conversation begins with a user expressing strong frustration about performance issues, using emphatic and hyperbolic language to convey dissatisfaction. Another participant responds briefly with agreement and informal, expletive-laden language, indicating shared frustration but without constructive input. The tone is tense and emotionally charged from the outset, with no signs of de-escalation or attempts at resolution. This GitHub conversation
-
copilot is crap, i dont want it disabled i want it to be removed
- Toxicity Score: 0.65 (Rapid escalation, sarcastic tone, emotional language)
- This GitHub conversation begins with a user expressing strong dissatisfaction and frustration regarding a feature, using emphatic language to demand its removal. Another participant responds with a sarcastic tone, implying that the feature's existence supports developer employment, which may subtly escalate tension. The interaction is brief but marked by emotional expressions and a lack of constructive dialogue, indicating potential for further conflict.
-
COPILOT CHAT IS COMPLETELY BROKEN
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, repeated threats, communication breakdown)
- This GitHub conversation involves a user expressing strong frustration and dissatisfaction with the handling of their issue, including perceived poor customer service and unresolved technical problems. The tone is initially aggressive and confrontational, with the user threatening to take their business elsewhere. A bot response requesting more information triggers further irritation. Subsequent comments show a mix of continued frustration and some relief when the issue appears to resolve temporarily, though technical difficulties persist. The overall sentiment fluctuates between anger and cautious optimism, with tension primarily driven by communication breakdowns and unresolved functionality problems.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, explicit profanity)
- This GitHub conversation involves a single user expressing intense frustration and dissatisfaction with the software's performance and responsiveness, using strong and explicit language to convey their anger. The tone is highly negative and aggressive, with no responses or attempts at resolution visible in the thread. The tension is triggered by repeated failures of the software to meet the user's expectations and follow instructions, leading to a venting of emotions rather than constructive dialogue.
-
don't works, don't respond, this is pure shit
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, unresolved tension)
- This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and frustration with the software's performance, using harsh and aggressive language. There are no responses or further interactions, so the tone remains one-sided and highly negative without any attempts at resolution or dialogue. The lack of engagement from others leaves the tension unaddressed and the sentiment unresolved.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
- This GitHub conversation consists of a single initial comment from one user expressing strong frustration and using aggressive language, with no subsequent comments or responses from other participants. The tone is hostile and confrontational, and the lack of engagement suggests unresolved tension.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, confrontational tone)
- This GitHub conversation involves a user reporting an issue with a highly agitated and confrontational tone, expressing frustration through aggressive language and threats of spamming. Another participant responds briefly and neutrally by marking the issue as a duplicate, which does not escalate the tension but also does not address the emotional state of the original poster. The initial hostility and lack of constructive engagement suggest potential for further toxic exchanges.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, privacy concerns)
- This GitHub conversation involves a user expressing strong dissatisfaction and concern over privacy issues, using confrontational and accusatory language towards the team managing the repository. The tone is defensive and frustrated, with the user demanding closure and deletion of the issue, indicating a breakdown in communication and trust. The conversation shows signs of tension triggered by perceived privacy violations and dissatisfaction with the handling of the issue.
-
who in the fuck told you to enable this bullshit
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, explicit profanity)
- This GitHub conversation consists of a single initial comment by a user expressing strong frustration and anger towards a feature, using aggressive and explicit language without any responses or further discussion.
-
it becomes stupid about 80-90 percent in project
- Toxicity Score: 0.75 (Rapid escalation, accusatory tone, threat of public exposure)
- This GitHub conversation involves a single user expressing strong frustration and suspicion towards the project maintainers, accusing them of intentional misconduct and threatening public exposure if demands are not met. The tone is confrontational and accusatory, with no responses or dialogue from other participants, indicating a one-sided venting rather than a collaborative discussion.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided hostility)
- This GitHub conversation involves a single user expressing extreme frustration and anger towards a tool, using highly aggressive and profane language without any responses or engagement from other participants. The tone is hostile and accusatory, with no signs of de-escalation or constructive dialogue. The lack of comments suggests the conversation did not evolve beyond the initial outburst.
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: 43
Key Open Pull Requests
1. Feature/107183 add ability to right align tree items description: This pull request adds a new feature allowing VS Code extensions that use the TreeView API to right-align the description property of TreeItems, with the default alignment remaining left, and includes styling to hide the description when TreeItem actions are shown to prevent visual clashes.
- URL: pull/268093
- Merged: No
- Associated Commits: e8217, b0697, e99d6, eae91, f2e12, 8db50, fe74b, f8d11, 29b4e, 1c4e8, 4345b, 1a6af
2. File icon display handling in chat sessions : This pull request addresses the issue where chat session file icons were unintentionally hidden when global file icons were disabled by replacing the current resourceLabel with IconLabel in chat sessions to prevent the CSS rule from affecting these icons.
- URL: pull/268364
- Merged: No
3. feat(scm): detect worktree hierarchy from inside and outside primary worktree closes #259083 #267612 #259083: This pull request enhances the Git worktree support in the SCM view by improving detection of worktree hierarchies both inside and outside the primary worktree, ensuring consistent display of the worktree hierarchy regardless of which worktree is opened, and updates the ${activeRepositoryName} window title variable to reflect the primary worktree folder name for better customization.
- URL: pull/267692
- Merged: No
Other Open Pull Requests
- Engineering workflow and environment configuration: Multiple pull requests focus on improving the engineering workflow by integrating running mangling checks, adjusting node options, and fixing environment variable inheritance in the integrated terminal across platforms. These changes ensure consistent build and runtime environments, including the addition and removal of macOS jobs and preserving NODE_OPTIONS for Node.js processes.
- Chat interface enhancements and features: Several pull requests enhance the VS Code chat experience by adding Alt+Click support for new chats, implementing queued messaging with status display, ensuring reactive updates to chat history, managing the visibility and accessibility of the "Delegate to Coding Agent" action, and adding descriptive tooltips for chat buttons. These improvements streamline user interaction and maintain consistent UI behavior.
- Git and SCM improvements: Pull requests introduce new Git features such as ignoring whitespace in blame information, creating Git worktrees with auto-generated branch names, and fixing SCM Graph hover tooltip links to correctly point to upstream repositories. These changes improve Git integration accuracy and usability within VS Code.
- UI and styling fixes: Multiple pull requests address UI improvements including CSS cleanups for icon alignment, increasing input box padding for better usability, and adding an explain action to the DiffHunkWidget. These updates enhance the visual consistency and user experience of the editor interface.
- Bug fixes and issue resolutions: Several pull requests fix specific bugs such as preventing colored symbol-* codicons on toolbars, restoring extension feature visibility after tab interactions, fixing Wayland detection in the snap launcher, and repairing non-functional settings links in Release Notes. These fixes improve stability and correctness of the VS Code interface and functionality.
- API and configuration enhancements: Pull requests add support for the
onDidChangeSemanticTokensevent to improve semantic token refresh performance, introduce local configuration overrides for MCP discovery with backward compatibility, and change default editor settings to suppress inline suggestions during snippet mode. These changes enhance extension capabilities and user customization.
- Build and release process improvements: One pull request ensures valid authentication tokens are used in the release build script to improve build reliability and security.
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: 190
Key Closed Pull Requests
1. Engineering - pipeline perf improvements: This pull request improves pipeline performance by declaring artifacts using the templateContext, refining compilation stage outputs, and optimizing CI job outputs and artifact handling in the build process.
- URL: pull/268041
- Merged: Yes
- Associated Commits: b9835, 89e1c, 68a60, 636a8, 52466, 50a20, 45959, 7d62d, 8e961, 4cf51, 4dc52, 821ff, 11c7d, af5e7, bb21f, c0a11, d7c1c, a3230, 77af2, 3cadb, 53b3c, e6b18, 5ea98, c911a, 9301a, 70ca6, 77d3c
2. Added section title: This pull request introduces a section title along with various UI improvements such as fixing overlapping disclaimer text, replacing the history toolbar with a chat history link, adding tooltip support and CSS styling for chat history items, implementing a right-click menu for the chat empty state, and refining padding and prompt styling to enhance the overall user experience.
- URL: pull/268586
- Merged: Yes
- Associated Commits: bf6af, 3234e, 9e466, 5472e, 2ffd4, 150ed, 43a59, d47a6, 67f76, e0422, 9afbe, b6768, c0fcc, 6e2fd, 82ef3, f6608, b2060, ede03, 032f3, de707, 75287
3. Implement fallback to .well-known/oauth-protected-resource for MCP OAuth discovery: This pull request refactors the MCP OAuth discovery process by implementing a fallback to the .well-known/oauth-protected-resource URI and simplifies the fetchAndValidateMetadata helper function to always throw errors and delegate error handling to callers, resulting in cleaner code, a simpler function signature without the throwOnError parameter, consistent return types, and preserved behavior compliant with RFC 9728.
- URL: pull/268211
- Merged: No
- Associated Commits: 78acd, 63a6f, 99cae, 6aecb, d912d, d8d70, 8ee73, f1532, d67fb, 657b6, 8bc44, 48151
Other Closed Pull Requests
- Chat Sessions API Redesign: This pull request redesigns the chatSessions API by removing dynamic registration of chat participants and requiring extensions to register them instead. It introduces 'untitled' chat sessions to prevent loss of the first request and adds an event to commit chat session items for swapping untitled sessions with backed sessions, resulting in a non-backward-compatible change that streamlines chat participant handling.
- Chat Feature Improvements and Accessibility: Multiple pull requests enhance the chat feature by adding tweaks for anonymous users, improving anonymous user indicators, adjusting overlay button styles, fixing padding in chat disclaimers, adding a command to focus the last focused chat item, and enhancing the accessibility help dialog. These changes collectively improve usability, layout, and accessibility of the chat experience in VS Code.
- Chat Notifications Enhancements: These pull requests add opt-in settings for OS notifications on chat responses and long-running task completions, addressing issues with sound notifications and media restrictions. They also refine task OS notification settings by changing thresholds, suppressing notifications for chat agent tool tasks, and removing redundant progress messages for a cleaner notification experience.
- Chat UI and Tooltip Improvements: This set of pull requests improves the chat UI by implementing position-aware tooltip placement to prevent overlap with other UI elements and enhancing the Local Chat Sessions window to show full date and time on hover for relative timestamps. These changes improve user experience and clarity in the chat interface.
- Chat Tooling and Metadata Support: A pull request adds support for a
toolMetadataproperty to Language Model Tool Results, enabling tools to attach arbitrary metadata for better integration and analytics. Another connectsLanguageModelDataPartto the chat output renderer system, allowing extensions to render custom content like diagrams within chat responses without new APIs.
- Chat Thinking Items and Icon Customization: These pull requests implement changes to thinking item headers to reflect their finished state and support multiple thinking items, along with fixing scrolling and addressing code review feedback. Additionally, a custom icon for Chat Sessions is introduced to ensure visibility even when the global file icon theme is off.
- Task and Terminal Enhancements: Pull requests add a
preserveTerminalNameoption to task presentation settings to maintain terminal names after task completion and add the word "compilation" to task progress messages in watching mode. These changes improve terminal identification and task status clarity.
- Test Coverage and Test Results Layout: One pull request adds the capability to run tests with a coverage tool including file input support and fallback options, while another implements a configurable layout option for the Test Results view allowing the test run tree to be displayed on the left side with a toolbar toggle. These enhance testing workflows and UI customization.
- Engineering and Build Process Improvements: Multiple pull requests clean up and consolidate engineering jobs, including Windows CLI job refactoring, compilation and Windows-specific task consolidation into reusable templates, and updating npm_and_yarn dependencies to keep them current and secure. These changes streamline the build and engineering workflows.
- Memory Optimization: A pull request optimizes memory usage by refactoring the
toDisposablefunction to use a class with a single dispose method on its prototype instead of creating a dispose closure for each call, resulting in significant memory savings and reductions in function instances and closures.
- Telemetry Fix: One pull request replaces an observable with a callback to fix telemetry issues where the accept count was incorrectly reported as multiple times greater than the shown count, addressing a specific telemetry problem.
- Network Connection Enhancements: A pull request adds support for connecting to MCP servers over Unix Domain Sockets and Windows Named Pipes, enhancing network connection capabilities without increasing bundle size due to existing dependencies.
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 | 319 | 73 | 0 | 222 |
| meganrogge | 180 | 21 | 37 | 132 |
| bpasero | 119 | 30 | 49 | 64 |
| roblourens | 41 | 11 | 49 | 152 |
| TylerLeonhardt | 37 | 6 | 25 | 118 |
| mjbvz | 50 | 13 | 57 | 61 |
| connor4312 | 59 | 10 | 24 | 79 |
| lszomoru | 106 | 22 | 15 | 26 |
| Tyriar | 30 | 1 | 47 | 54 |
| aeschli | 58 | 9 | 4 | 49 |