Weekly GitHub Report for Vscode: September 15, 2025 - September 22, 2025 (12:01:28)
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 enhancements, users are directed to the official Visual Studio Code release notes.
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.
-
High GPU Usage by WindowServer When Opening Projects in VS Code After macOS 26 Update: This issue reports a significant increase in GPU usage by the WindowServer process when opening projects in VS Code on macOS 26, particularly in windowed mode, with normal GPU usage observed in full-screen mode or when no project is loaded. The problem appears to be related to rendering or compositing inefficiencies triggered by the macOS update and affects both Intel and Apple Silicon Macs, suggesting a deeper compatibility or graphics engine issue.
- Commenters confirmed the GPU usage scales with window size and shared that the issue affects multiple Mac models and chipsets, not just Intel-based machines. Several users provided spindump logs to aid diagnosis, while others identified the root cause as a Skia rendering engine bug requiring collaboration between Apple and Google engineers. A temporary workaround of using full-screen mode was suggested, but no immediate fix is available, and the problem also impacts other Skia-based applications beyond VS Code.
- Number of comments this week: 15
-
Claude Model Missing from GitHub Copilot Model Dropdown List: This issue reports that the Claude model has disappeared from the GitHub Copilot model selection dropdown in the VS Code extension, preventing users from choosing or using Claude for code suggestions. The problem appears to be region-specific, likely caused by Anthropic restricting access to the Claude model for users in China, with some users noting that using a proxy or VPN temporarily restores access.
- The comments reveal multiple users experiencing the same disappearance of the Claude model, with some temporarily regaining it after restarting or using a proxy. There is consensus that the issue is related to regional restrictions rather than a bug in GitHub Copilot itself, and users express frustration over the impact on productivity and the need to use proxies to access Claude. Some also report that the problem persists across different OSes and setups, and no definitive official solution has been provided yet.
- Number of comments this week: 14
-
Freeze & Crash when Terminal content starts to scroll: This issue describes a bug where Visual Studio Code freezes and eventually crashes when the integrated terminal content becomes long enough to require scrolling, causing the prompt to go out of view. The problem appears linked to the recently enabled default setting for terminal sticky scroll, as disabling this feature prevents the crashes, and the issue did not occur in earlier versions without sticky scroll enabled by default.
- The comments reveal that the root cause is the terminal's sticky scroll feature, which when enabled, causes flickering and ultimately crashes during terminal output scrolling; users confirmed disabling sticky scroll resolves the issue, and testing showed the problem is new to version 1.104 where sticky scroll became default, while earlier versions did not exhibit the crash even with sticky scroll enabled manually.
- Number of comments this week: 7
-
No means to pause/stop Copilot's processing: This issue reports the lack of a pause or stop control for Copilot's processing in Agent mode within the Copilot Chat extension, making it impossible to interrupt ongoing requests once started. The user highlights that in the current stable VS Code version, no such controls are visible, causing frustration when Copilot makes mistakes and the user cannot halt its operation.
- Multiple commenters confirm experiencing the same problem, noting that while a pre-release version briefly shows extra controls including a stop button, these are not accessible in the stable release; users express a need for a reliable pause or stop feature to manage Copilot's behavior effectively during interactions.
- Number of comments this week: 7
-
agent hangs : This issue describes a bug where the GitHub Copilot Chat agent hangs after terminal commands complete successfully, making the agent mode unreliable for workflows involving terminal output on macOS with zsh and Powerlevel10k (p10k) theme. Users report that the problem is linked to shell integration issues with p10k, and a workaround involving switching to bash or modifying p10k configuration to enable shell integration resolves the hang.
- Commenters confirmed the agent hang occurs despite successful terminal execution and shared that switching from zsh with p10k to bash eliminates the issue. Further investigation revealed that disabling p10k or explicitly enabling shell integration in the p10k config file fixes the problem, providing a practical solution for affected users.
- Number of comments this week: 6
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request asking for the ability to display markdown generated by code cells in the notebook outline, similar to how JupyterLab shows titles from code cell outputs alongside markdown cells. The requester highlights that this functionality would allow dynamic content generated by code to appear in the outline, improving navigation and usability within the notebook environment.
- 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 folder on a different server causes the current window to disconnect and switch to the new server, rather than opening a separate window or reusing the existing one properly.
${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," leading to errors that prevent the terminal process from starting. 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 path, indicating an inconsistency 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, 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, causing a delay in terminal updates despite the terminal not being truly frozen.
- 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, indicating a rendering problem. The user notes that this character displays correctly in other applications like Firefox, suggesting the problem is specific to VS Code's handling of certain Unicode symbols.
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: 490
Summarized Issues:
- Copilot Chat and Agent Mode Bugs: Numerous issues report that GitHub Copilot Chat and its agent mode frequently hang, become unresponsive, or fail to process commands correctly, causing workflow interruptions. Users experience problems such as indefinite waiting after terminal commands, failure to update or modify files, and crashes or freezes in both Windows and macOS environments.
- issues/266637, issues/266640, issues/266645, issues/266646, issues/266664, issues/266665, issues/266666, issues/266684, issues/266699, issues/266704, issues/266737, issues/266738, issues/266992, issues/267011, issues/267026, issues/267090, issues/267127, issues/267133, issues/267150, issues/267161, issues/267197, issues/267229, issues/267340, issues/267382, issues/267419, issues/267487, issues/267492, issues/267494, issues/267509, issues/267559, issues/267633
- Authentication and Token Errors: Many users report persistent authentication failures, token expiration, and 403 errors across multiple platforms and extension versions, preventing access to Copilot features. These issues include endless login loops, inability to switch accounts, and network-related token invalidation, severely impacting usability.
- Performance and Responsiveness Issues: Several reports highlight severe performance degradation in VS Code, including slow responsiveness, high CPU and memory usage, freezing, and crashes, often linked to Copilot or extension interactions. Users experience slow auto-completion, delayed error resolution, and unresponsive UI elements across Windows, macOS, and Linux.
- Terminal and Command Execution Problems: Users report bugs with terminal behavior including command auto-approval failures, terminal freezing, incorrect command completions, and issues with terminal integration in Copilot. Problems include inability to reuse terminals, commands running in wrong directories, and terminal input anomalies.
- Extension Signature Verification and Installation Failures: Multiple issues describe failures in extension signature verification preventing proper installation or use of Copilot and related extensions, affecting macOS and Linux users. These problems block extension functionality and cause errors during setup or updates.
- Model Selection and Usage Issues: Users report problems with model selection in Copilot Chat, including inability to select models, missing model options, unexpected model switching, and inconsistent behavior between models. These issues affect user control over AI behavior and degrade the coding experience.
- File and Workspace Management Bugs: Several issues describe problems with file operations such as files not being deleted, files not being modified despite AI indications, incorrect file path handling, and workspace syncing failures. These bugs cause confusion and data loss risks.
- UI and Accessibility Problems: Users report UI glitches including misaligned elements, missing buttons, broken keyboard shortcuts, inaccessible screen reader information, and inconsistent chat interface behavior. These issues reduce usability and accessibility for many users.
- Network and Connectivity Errors: Numerous reports describe network errors such as connection resets, HTTP2 protocol errors, and fetch failures that disrupt Copilot and extension functionality, often linked to firewall or proxy configurations.
- Feature Requests for Usability Enhancements: Users request various improvements including native text-to-speech support, better settings organization, workspace tabbing with split screens, customizable model selection, integrated web search, and improved notifications for long-running tasks. These features aim to enhance productivity and user control.
- Code Suggestion and Editing Issues: Several bugs describe problems with Copilot's code suggestions including incorrect or repetitive suggestions, failure to learn from previous code, unexpected code deletions, and infinite loops during code insertion. These issues frustrate users and reduce trust in AI assistance.
- Miscellaneous Bugs and Requests: Other issues include problems with specific language support, extension telemetry inaccuracies, missing features like file size display, and requests for improved integration with other tools and frameworks.
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: 338
Summarized Issues:
- Token Expiration and Authentication Failures: A large number of issues report persistent 403 errors caused by expired or invalid authentication tokens in the VS Code GitHub Copilot and related extensions. These errors prevent users from making requests, cause features to stop working, and often require restarting VS Code or waiting for upstream GitHub service fixes, with many users frustrated by the lack of clear re-authentication mechanisms or guidance.
- [issues/266609, issues/266670, issues/266676, issues/266709, issues/266743, issues/266744, issues/266745, issues/266746, issues/266749, issues/266752, issues/266753, issues/266755, issues/266756, issues/266757, issues/266758, issues/266760, issues/266761, issues/266762, issues/266764, issues/266765, issues/266766, issues/266769, issues/266770, issues/266772, issues/266773, issues/266776, issues/266778, issues/266779, issues/266780, issues/266781, issues/266782, issues/266783, issues/266784, issues/266785, issues/266787, issues/266788, issues/266789, issues/266790, issues/266792, issues/266795, issues/266796, issues/266797, issues/266798, issues/266800, issues/266801, issues/266803, issues/266804, issues/266805, issues/266806, issues/266808, issues/266809, issues/266810, issues/266811, issues/266812, issues/266813, issues/266814, issues/266815, issues/266816, issues/266817, issues/266820, issues/266821, issues/266822, issues/266823, issues/266825, issues/266826, issues/266827, issues/266828, issues/266829, issues/266830, issues/266831, issues/266832, issues/266834, issues/266835, issues/266836, issues/266837, issues/266838, issues/266839, issues/266841, issues/266842, issues/266845, issues/266846, issues/266847, issues/266848, issues/266849, issues/266850, issues/266851, issues/266852, issues/266853, issues/266854, issues/266855, issues/266856, issues/266858, issues/266859, issues/266860, issues/266861, issues/266862, issues/266863, issues/266864, issues/266865, issues/266866, issues/266867, issues/266868, issues/266870, issues/266871, issues/266872, issues/266873, issues/266875, issues/266876, issues/266877, issues/266878, issues/266879, issues/266880, issues/266881, issues/266882, issues/266883, issues/266884, issues/266885, issues/266886, issues/266887, issues/266888, issues/266889, issues/266890, issues/266891, issues/266892, issues/266893, issues/266894, issues/266895, issues/266896, issues/266897, issues/266898, issues/266899, issues/266900, issues/266901, issues/266902, issues/266903, issues/266904, issues/266905, issues/266906, issues/266907, issues/266908, issues/266909, issues/266910, issues/266911, issues/266912, issues/266913, issues/266914, issues/266915, issues/266916, issues/266917, issues/266918, issues/266919, issues/266920, issues/266921, issues/266922, issues/266923, issues/266924, issues/266925, issues/266926, issues/266927, issues/266928, issues/266929, issues/266930, issues/266931, issues/266933, issues/266934, issues/266935, issues/266936, issues/266937, issues/266938, issues/266939, issues/266940, issues/266941, issues/266942, issues/266943, issues/266945]
- Extension Non-Responsiveness and No Response Errors: Several issues describe the VS Code extension or Copilot Chat extension failing to generate any response or becoming stuck indefinitely on "Working," with users receiving error messages like "Sorry, no response was returned." These problems occur across multiple platforms and extension versions, severely impacting usability and requiring restarts or workarounds.
- [issues/266636, issues/266649, issues/266668, issues/266692, issues/266705, issues/267060, issues/267121, issues/267336, issues/267621]
- Token and Rate Limit Mismanagement Despite Premium Status: Users with paid or premium subscriptions report being incorrectly rate-limited or receiving token expiration errors despite having sufficient usage credits or tokens remaining. This causes confusion and frustration as premium features are not recognized or applied correctly, leading to blocked requests and degraded service.
- [issues/266670, issues/266928, issues/267135, issues/267342, issues/267567]
- Copilot Agent Control and Interaction Issues: Multiple reports highlight missing or non-functional controls in the Copilot agent, such as the absence of a stop or pause button, failure to halt ongoing actions, and the agent not following user instructions or plans. These issues cause wasted premium tokens, workflow disruption, and user frustration due to lack of control over the AI's behavior.
- [issues/266656, issues/267625, issues/267626]
- Symlink Resolution and File Handling Bugs: There are longstanding issues with VS Code's inability to properly resolve symbolic links, causing persistent bugs that have remained unfixed for years. Additionally, bugs include phantom errors in empty header files and false indications of file updates or extra blank lines inserted during code removal, leading to confusion and workflow disruption.
- [issues/266579, issues/266632, issues/266721]
- Model Selection and Authentication Credential Loss: Users report problems with the Copilot Chat extension losing credentials for manually added OpenRouter models, requiring repeated re-entry. There are also issues with premium models defaulting to free or lower-quality models unexpectedly, and requests for temporary per-message model overrides to avoid accidental premium usage.
- [issues/266734, issues/266956, issues/266963, issues/267234, issues/267235]
- Network and Scrollbar UI Issues: Some users experience UI bugs such as missing horizontal scrollbars on Mac M3 devices, preventing horizontal scrolling, and high GPU usage by WindowServer when running VS Code on certain Mac hardware. Other UI problems include broken maximize panel commands on Linux and graphical glitches with window corners on Mac OS.
- [issues/266581, issues/266694, issues/267065, issues/267158]
- Extension Crashes and Server Errors: There are reports of server errors including 400 and 500 status codes due to inaccessible attachments or invalid JSON formats in tool call arguments, causing request failures. Some extensions also crash or hang during operations like editing large files or processing requests, leading to lost work and degraded user experience.
- [issues/266676, issues/267108, issues/267273, issues/267309, issues/267365, issues/267369, issues/267504, issues/267510, issues/267511]
- Performance and Stability Problems: Users report performance degradation such as inability to compile programs, freezing during simulator startup, sluggish scrolling, and high resource usage. Some extensions fail to install or run properly, and agent modes get stuck in loops consuming excessive quota, all contributing to unstable development environments.
- [issues/266636, issues/267031, issues/267065, issues/267501, issues/267502, issues/267611, issues/267615]
- User Experience and Feature Requests: There are multiple requests for improved user experience features such as progress bars for downloads, inline documentation hints during autocomplete, auto-complete in chat input, dark mode for settings, and better notification controls. Users also request clearer error messages and guidance for token refresh and re-authentication processes.
- [issues/266656, issues/266984, issues/267017, issues/267171, issues/267259, issues/267395, issues/267448]
- Miscellaneous Bugs and Frustrations: Other issues include bugs with drag and drop on Mac, incorrect import syntax suggestions, failure to copy values in debug mode, and complaints about AI model quality and forced AI autocomplete. Some reports express strong dissatisfaction with AI responses and request removal of certain models or features.
- [issues/266648, issues/266667, issues/266968, issues/267137, issues/267179, issues/267280, issues/267361]
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, accusatory language, frustration)
- This GitHub conversation involves a user expressing dissatisfaction and accusing another party of misleading behavior regarding product versions, with a tone that shifts from neutral to accusatory and frustrated. The initial post sets a confrontational tone by alleging deception, and the subsequent comment reinforces this sentiment by highlighting personal impact and disappointment. This exchange shows early signs of tension triggered by perceived misrepresentation and unmet expectations.
-
https://code.visualstudio.com performance issue - high RAM/GPU usage
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, security concern)
- This GitHub conversation involves a user warning others about a potentially harmful file shared by another participant, expressing a strong negative sentiment and cautionary tone. The interaction is brief but marked by a clear alert that triggers concern and tension regarding security risks. No further dialogue is present to de-escalate or clarify the situation.
-
Why vscode can't resolve symlink? The FUCKING bug not fixed OVER FIVE YEARS
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, strong profanity)
- This GitHub conversation features a single user expressing intense frustration and dissatisfaction with the handling of a long-standing issue, using strong language and emphasizing the duration and perceived neglect of the problem. There are no other participants or responses to moderate or escalate the tone.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, offensive terms)
- This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment and frustration using aggressive and offensive language, with no subsequent replies or engagement from other users. The tone is highly confrontational and inflammatory, but the lack of interaction means no escalation or resolution occurs.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, personal attacks, profanity)
- This GitHub conversation features a highly confrontational and sarcastic comment from a user directed at another contributor, marked by aggressive language and personal attacks. The tone is dismissive and mocking, with the commenter expressing frustration and disdain towards the other's coding skills and the state of the project. The tension is triggered by perceived incompetence and the use of strong profanity in the original issue report, escalating the hostility in the response.
-
Copilot chooses free model when i want premium.
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity)
- This GitHub conversation involves a user expressing intense frustration and confusion about a service not functioning as expected, with the tone escalating from exasperation to outright anger and profanity. The initial comment reflects disbelief and a demand for clarification, while the subsequent comment uses aggressive and offensive language, indicating a rapid escalation in emotional intensity. The triggers of tension appear to be perceived service failures and unmet expectations regarding premium features.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive content)
- This GitHub conversation consists of a single initial comment by one user expressing extreme frustration and anger in a highly aggressive and offensive manner, with no subsequent responses or dialogue.
-
AI GITHUB COPILOT TERKHUSUS AGENT CHATGPT 4.1 SEPERTI ANJING RESPONSYA, SANGAT BODOH DAN TOLOL
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms, no moderation)
- This GitHub conversation consists of a single initial post by one user expressing strong negative emotions and frustration using offensive language, without any subsequent comments or responses. The tone is highly aggressive and derogatory, and the lack of interaction suggests no immediate de-escalation or moderation.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, explicit insults)
- This GitHub conversation involves a user expressing intense frustration and accusing an agent of manipulative behavior, with the agent acknowledging the issue and apologizing. The tone is highly emotional and confrontational from the user, while the agent's response is conciliatory and self-critical. The tension is triggered by perceived intentional unhelpfulness and miscommunication, escalating to explicit anger and demands for accountability.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, strong negative sentiment)
- This GitHub conversation consists of a single initial post by one user expressing strong negative emotions and dissatisfaction without any responses or further interaction. The tone is highly aggressive and frustrated, but no dialogue or escalation occurs due to the absence of comments.
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. Eli/chat input: This pull request focuses on refining the chat input interface by removing the text label from the Add Context button and replacing it with a centered paperclip icon, along with adjustments to icon centering and button height for improved visual consistency.
- URL: pull/267167
- Merged: No
2. fix: fix notebook overlay layout problem: This pull request addresses and fixes the layout problem related to the notebook overlay in the Visual Studio Code project.
- URL: pull/267323
- Merged: No
3. Add MCP configuration target selection for CLI and URL handler: This pull request introduces the ability for users to select the installation target (user, workspace, or remote) for MCP servers via both the code --add-mcp CLI command—enhanced with a new --mcp-target parameter and smart workspace detection—and the vscode:mcp/install URL handler, which now presents a target selection dialog, while also adding telemetry tracking for these choices and comprehensive tests, all implemented with backward compatibility.
- URL: pull/267372
- Merged: No
Other Open Pull Requests
- Chat UI and Interaction Enhancements: Multiple pull requests improve the chat experience in VS Code by adding features such as a sparkle effect, a new default chat mode setting, and enhanced session management with double-click to create new chats and dropdown menus for session actions. These changes also include accessibility improvements like replacing the "History" header with a link and enabling chat history by default to streamline user interaction.
- Comments View Ctrl+Click Features: Two pull requests introduce Ctrl+click functionality in the Comments view, allowing users to collapse all comment threads at once and to open the corresponding file while collapsing all threads, enhancing navigation and reducing visual clutter in the editor. These features extend existing Ctrl+click behavior for code folding to comment threads for improved usability.
- Local History and Extensions Search Enhancements: Pull requests add support for the
@localprefix in both the Command Palette and Extensions view, enabling efficient browsing and searching of local history entries and locally installed extensions. These features include smart diff viewing, category filtering, sorting, autocomplete suggestions, and comprehensive testing to ensure functionality and backward compatibility.
- Notification and Toast Improvements: Several pull requests address notification behavior by adding a new setting to customize toast notification positions to any bottom corner, preventing overlap with UI elements like the copilot chat window, and fixing premature OS toast notifications in the chat confirmation widget by managing CSS classes and notification logic.
- Terminal and Input Behavior Fixes: Pull requests fix issues in the terminal and input handling, including preventing sticky scroll from remaining visible after the
clearcommand and correcting the right arrow key behavior in QuickInput to avoid triggering accept actions, restoring proper cursor navigation in the Monaco editor.
- Chat Agent Tools and Validation Enhancements: One pull request adds the
git branchcommand to the auto-approved terminal commands in the chat agent tools to improve user experience without compromising security, while another implements the missingvalidateToolsObjectfunction for comprehensive validation of hierarchical tool objects with localized error messages and extensive tests.
- UI Layout and Styling Adjustments: Pull requests address UI consistency and usability by adding padding to the chat disclaimer welcome message when no chat history exists, limiting notebook cell editor height to viewport height, and disabling double-click to reveal markdown source for
.copilotmdfiles while preserving behavior for regular markdown files.
- Theme and Color Export Features: A pull request introduces a command-line flag to export all registered theme color definitions in a machine-readable JSON format, providing theme developers with a complete and accurate source for customizing and creating themes.
- Configuration and Regex Fixes: Pull requests fix bugs in configuration merging for MCP servers to prevent overwriting existing entries and correct regular expressions for HSL saturation color detection to properly recognize decimal variations of 100 percent, including additional tests for verification.
- Chat Session View Interaction: Two pull requests implement double-click actions in the Chat Sessions view to create new chat editors, improving discoverability and mirroring Explorer view behavior, addressing user experience issues.
- Extension Testing Reliability: One pull request improves the German language pack smoke test by adding retry logic with extended timeouts, strategic waits, enhanced error detection, and a resilient retry strategy to make extension installation tests more reliable and provide better diagnostics.
- Environment Variable and Script Improvements: A pull request introduces the
VSCODE_COPILOT_TERMINALenvironment variable along with associated unit tests and script linting improvements to the Visual Studio Code project.
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: 69
Key Closed Pull Requests
1. Update github action for instruction update.: This pull request proposes updates to the GitHub Actions workflow and related tokens to improve the process of updating instruction files, including fixes to syntax, permissions, and validation mechanisms, although it was ultimately not merged.
- URL: pull/267278
- Merged: No
- Associated Commits: 26d70, 961ed, ef072, 158bc, 965b1, 22257, e0f08, bda5a, 0e8b8, 73c70, 7a69e, aaabe, 8becd, e8318, 02c4b, 4b09d, d7f33, eadc7
2. Add some learning prompts and "send to edit session" for inline chat: This pull request adds learning prompts and component specifications, as well as introduces a "send to edit session" feature that appears as a context menu action in files with active edit diffs or serves as the default action when inline chat is open in a diff.
- URL: pull/267519
- Merged: Yes
- Associated Commits: c7914, f0f08, ec5a9, 07f4f, bdbc0, f12fc, 814af, f6d35, f9795, db172, cc011, ad33e
3. [WIP] poc: branch-associated Chat Sessions: This pull request is a work-in-progress proof of concept aimed at implementing branch-associated chat sessions in Visual Studio Code, featuring initial UI development, session handling, and branch switching functionality.
- URL: pull/267139
- Merged: No
Other Closed Pull Requests
- Chat feature improvements: Multiple pull requests enhance the chat functionality by cleaning up chat history code, adding a toolbar, fixing flicker issues, and supporting the
anonymousentitlement from the entitlements service. Additionally, new chat session creation by double-clicking empty space in the Chat Sessions view was implemented twice to improve user experience and consistency.
[pull/266587, pull/266713, pull/266974, pull/267131, pull/267200]
- Build and release pipeline updates: Several pull requests improve the engineering and release pipeline by disabling SBOM creation for intermediary artifacts, removing the
isProductiontemplate parameter, integrating the release build into the publish job, and refining repository checkout steps to optimize efficiency. Updates to the build configuration include backporting Electron version 37.3.1 to address internal backlog issues.
[pull/267130, pull/267213, pull/267200, pull/267254, pull/267255]
- Smoke test and CI robustness: Pull requests address CI build failures by improving the smoke test setup to handle errors gracefully, automatically creating issues on smoke test failures, and fixing localization smoke test failures by updating CSS selectors for extension action buttons. These changes enhance test stability and error reporting.
[pull/267276, pull/267284, pull/267287]
- Git and OAuth fixes: Improvements include better Git path comparison handling trailing and mixed separators, and fixing GitHub OAuth authentication failures in web environments by correctly implementing the PKCE flow and updating token exchange logic. These fixes ensure more reliable authentication and path handling.
[pull/267112, pull/267490]
- Editor UI enhancements: A floating menu overlay widget was introduced to the editor with initial implementation and subsequent refactoring to improve the user interface.
[pull/267156]
- Code quality and linting: A new lint rule
code-no-observable-get-in-reactive-contextwas added along with code improvements and fixes for lint warnings to enhance code quality in the project.
[pull/267526]
- Resource and caching fixes: A fix was made for image thumbnails not displaying in resource-link tool results by adding a momentary cache to reduce redundant reads and introducing a CancellationTokenPool to optimize cancellable operations.
[pull/267079]
- Codebase cleanup and refactoring: The old prompt parser was removed and replaced with new components like
computeCustomChatModesandIVariableReferencesto improve functionality.
[pull/266953]
- Miscellaneous proposals and unmerged changes: Proposals include adding a settings.json for workspace configuration and window zoom, and an unmerged feature called "kb-events" along with a PR fixing TextEncoder types, hygiene buffer limits, and extension directory handling.
[pull/266598, pull/266607, pull/267620]
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 | 302 | 62 | 0 | 76 |
| meganrogge | 209 | 3 | 36 | 109 |
| roblourens | 48 | 3 | 59 | 143 |
| Tyriar | 60 | 2 | 67 | 92 |
| bpasero | 94 | 11 | 51 | 62 |
| TylerLeonhardt | 61 | 6 | 19 | 115 |
| mjbvz | 51 | 7 | 56 | 51 |
| connor4312 | 45 | 4 | 26 | 78 |
| joshspicer | 57 | 2 | 10 | 62 |
| lramos15 | 22 | 1 | 6 | 100 |