Weekly GitHub Report for Vscode: March 23, 2026 - March 30, 2026 (22:24:09)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
The version released on March 12, 2025, primarily focuses on addressing a range of issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." This update emphasizes bug fixes and stability improvements, with full release notes available on the official Visual Studio Code updates page.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
The default theme color change in Visual Studio Code code is very ugly and terrible: This issue addresses user dissatisfaction with the automatic change of the default theme color in Visual Studio Code after an update, which many find visually unappealing and harmful to the eyes. Users express frustration over the forced theme switch without consent, noting that the new syntax highlighting is confusing and less ergonomic compared to the previous "Dark Modern" theme.
- The comments reveal widespread user frustration and confusion about the forced theme change, with many sharing workarounds to revert to the old theme and criticizing the decision to impose the new default; a maintainer acknowledged the issue as an unintended edge case, apologized, and provided instructions to revert the theme while promising a fix.
- Number of comments this week: 31
-
Unknown tool github/issue_read error after auto extension update in VS Code: This issue describes repeated warnings of an "Unknown tool 'github/issue_read'" error appearing in the Problems tab of Visual Studio Code after the GitHub Copilot Chat extension auto-updated, causing the Copilot agent to become unresponsive or slow in generating code. Users report that uninstalling and reinstalling the extension or reloading VS Code does not permanently resolve the warnings, and the problem seems linked to compatibility issues between the extension and the latest VS Code version or corrupted extension paths.
- Commenters suggest the error may be due to corrupted registry paths from the auto-update, recommend installing related extensions like GitHub Pull Requests and MCP Server to reduce errors, and share temporary workarounds such as disabling certain built-in tools in the Copilot Chat customization settings; some users note the issue resolved itself after subsequent extension updates without further action.
- Number of comments this week: 31
-
Unwanted new default themes without consent: This issue addresses the problem of Visual Studio Code automatically changing the default theme to a new "Dark Modern" version without user consent during an update, which disrupts users' established workflows and preferences. The reporter requests an option to opt out of such automatic theme changes or to retain the old theme as a selectable option to avoid losing familiar color schemes and syntax highlighting.
- The comments largely express frustration over the unexpected theme change, with multiple users thanking others for sharing how to revert to the old theme; many emphasize that changing the default theme without explicit user consent is a major disruption and poor user experience, while some provide detailed critiques of the new theme’s color choices and accessibility issues.
- Number of comments this week: 15
-
[TRIAGE-NEEDED] “Closing the window is taking a bit longer…” since upgrade to v1.113.0: This issue reports that since upgrading to VS Code version 1.113.0, closing a workspace window takes significantly longer than before, displaying a modal warning that the window is "taking a bit longer" due to the extension host shutdown process. The problem appears to stem from a change in the shutdown sequence where extension termination and window closing now happen synchronously rather than asynchronously, causing delays especially when many extensions are active.
- Commenters confirmed the issue affects multiple platforms and is not caused by a single extension but rather the cumulative shutdown time of multiple extensions; some found that disabling heavy extensions like GitHub Copilot Chat mitigates the delay, while others reverted to version 1.112.0 to avoid the problem entirely.
- Number of comments this week: 13
-
[INFO-NEEDED] [TRIAGE-NEEDED] hit limit issue : This issue reports a bug where users experience persistent and severe rate-limiting problems despite upgrading to the Pro plan, questioning the value of the paid subscription. Users describe hitting global rate limits quickly, receiving error messages, and express frustration over the limitations affecting their ability to use the service effectively.
- The comments reveal widespread user frustration with sudden and strict rate limits, including screenshots of error messages and rate-limit notifications. Multiple users confirm the issue persists even after upgrading to the Pro plan, with some demanding refunds and others noting that changing settings does not alleviate the problem.
- Number of comments this week: 12
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
As of our latest update, there are no stale issues for the project this week.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 799
Summarized Issues:
- Command and Tool Execution Failures: Multiple issues report that commands or code changes acknowledged by the Copilot or chat extensions are not actually executed or applied, causing user frustration and wasted tokens. This includes failures in applying code changes, tool calls returning errors, and commands being ignored despite confirmation prompts.
- Chat and Session UI/UX Issues: Several reports highlight problems with chat session management, including disappearing or missing chat responses, inability to delete or archive chats properly, UI glitches with code blocks disappearing, and confusing or inconsistent session lists. Users also report issues with session titles, switching, and chat input behavior.
- Performance and Resource Usage Problems: Numerous issues describe high CPU usage, memory leaks, and system slowdowns caused by the Copilot extension or VS Code itself, often triggered by large workspaces, chat sessions, or specific extension versions. These problems lead to crashes, freezes, and degraded user experience across platforms.
- Model and AI Behavior Issues: Many users report that AI models, especially GPT-5.3-Codex and Claude variants, fail to perform as expected, including not modifying files, generating incomplete or garbled output, entering infinite loops, or producing irrelevant or psychotic responses. There are also complaints about model selection, auto-switching, and rate limiting.
- Extension Installation, Activation, and Compatibility Problems: Users report issues with extensions not activating, failing signature verification, not compatible with certain VS Code versions or remote environments, and problems with extension updates causing breakage or crashes.
- Terminal and Integrated Shell Issues: Several issues describe terminal problems including cursor misplacement, terminal hangs, incorrect rendering, command approval prompts, and integration problems with shells like PowerShell, zsh, and fish, often exacerbated by sandboxing or recent VS Code updates.
- Session and Workspace Management Problems: Issues include sessions not appearing or updating correctly, problems with session trust and archiving, difficulty managing worktrees, and inconsistent behavior when switching or deleting sessions, causing confusion and potential data loss.
- Rate Limiting and Subscription Issues: Users report unexpected rate limiting, false usage warnings, and subscription problems despite having paid plans, leading to inability to use features or extensions properly.
- Theme, Syntax Highlighting, and UI Appearance Regressions: Multiple reports describe regressions in themes and syntax highlighting, including poor contrast, broken color schemes, unwanted theme changes, and UI elements not rendering correctly after updates.
- File and Code Editing Anomalies: Issues include files not updating correctly after renaming, code blocks disappearing in chat, incorrect file language modes, and problems with file creation or modification commands not completing.
- Extension and Feature Requests: Users request improvements such as better telemetry, UI enhancements, new features for managing sessions, bookmarks, model tags, and integration with other tools or workflows.
- Network, Update, and Installation Errors: Reports include update failures, network errors during extension installation or usage, and problems with proxy or certificate configurations causing crashes or inability to connect.
- Localization and Translation Issues: Some issues report incorrect or unclear translations in various languages, affecting user understanding and interface clarity.
- Security and Privacy Concerns: Users raise concerns about sensitive data exposure, such as usernames and passwords being generated or leaked by the AI, and request masking or removal of such data from models.
- Miscellaneous Bugs and Unknown Issues: Various reports of crashes, freezes, unexpected errors, and vague problems without clear reproduction steps or detailed descriptions.
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: 1091
Summarized Issues:
- Terminal and Integrated Terminal Issues: Multiple bugs affect the terminal in VS Code, including buffer overflows corrupting multiline commands, infinite loops of carriage returns or new lines, freezing or becoming unresponsive, and problems with shell integration causing endless loops or input failures. These issues cause severe usability problems such as inability to input commands, terminal output truncation, and crashes, often requiring restarts or workarounds.
- Copilot Extension and Chat Functionality Failures: Numerous reports describe the Copilot extension and chat features failing to respond, freezing, entering infinite loops, or not performing requested edits despite indicating otherwise. Users experience issues such as inability to select models, repeated error messages, missing or disappearing code blocks, and failures in agent mode to apply changes, severely impacting productivity and trust in the tool.
- issues/299958, issues/300154, issues/300256, issues/301053, issues/302247, issues/302248, issues/302531, issues/302784, issues/303114, issues/303424, issues/304386, issues/304393, issues/304400, issues/304461, issues/304462, issues/304663, issues/304688, issues/304810, issues/305145, issues/305201, issues/305284, issues/305299, issues/305326, issues/306069, issues/306124, issues/306284
- Rate Limiting and Quota Management Problems: A large cluster of issues report users encountering unexpected or premature global rate limits and quota resets despite having paid subscriptions or remaining usage credits. These rate limits cause interruptions, inability to use premium models, and frustration due to lack of clear communication or warnings, severely impacting user workflows and trust in the service.
- issues/302685, issues/304239, issues/304430, issues/304515, issues/304583, issues/304834, issues/304835, issues/304848, issues/304849, issues/305392, issues/305393, issues/305394, issues/305395, issues/305397, issues/305404, issues/305405, issues/305407, issues/305411, issues/305412, issues/305413, issues/305414, issues/305415, issues/305416, issues/305417, issues/305419, issues/305420, issues/305421, issues/305422, issues/305425, issues/305427, issues/305428, issues/305429, issues/305430, issues/305431, issues/305433, issues/305434, issues/305435, issues/305439, issues/305440, issues/305441, issues/305444, issues/305445, issues/305446, issues/305447, issues/305448, issues/305449, issues/305450, issues/305451, issues/305453, issues/305454, issues/305455, issues/305456, issues/305457, issues/305458, issues/305459, issues/305460, issues/305461, issues/305462, issues/305463, issues/305464, issues/305465, issues/305466, issues/305467, issues/305468, issues/305469, issues/305471, issues/305472, issues/305473, issues/305474, issues/305475, issues/305476, issues/305477, issues/305479, issues/305480, issues/305481, issues/305482, issues/305483, issues/305484, issues/305485, issues/305487, issues/305488, issues/305489, issues/305491, issues/305492, issues/305493, issues/305494, issues/305495, issues/305496, issues/305497, issues/305498, issues/305499, issues/305500, issues/305501, issues/305503, issues/305504, issues/305506, issues/305507, issues/305508, issues/305509, issues/305510, issues/305511, issues/305512, issues/305513
- Chat UI and Rendering Problems: Several issues report that chat responses, especially those containing multiple code blocks or markdown tables, fail to render correctly or disappear after streaming completes. Dropdown menus and model selectors in new or detached chat windows flicker or close immediately, preventing user interaction. These UI bugs degrade the user experience and hinder effective use of chat features.
- Model and Agent Selection Issues: Users report problems with model pickers and agent dropdowns not appearing, closing immediately, or not functioning in new or detached windows. Some models are missing or not accessible despite valid tokens, and switching models sometimes fails or causes errors. These issues prevent users from effectively selecting or using desired AI models or agents.
- Chat Session Storage and Serialization Errors: Multiple issues describe errors occurring during serialization of chat sessions for storage, causing loss of session data if the window is closed. These errors often involve unreachable errors or invalid string lengths during diffing or JSON stringification, leading to lost chat history and user frustration.
- Performance and Stability Regressions: Several reports highlight severe performance degradations, including slow typing, laggy UI, high CPU usage, and crashes after recent updates or in specific VS Code versions. These regressions affect both the core editor and extensions like Copilot, causing frustration and loss of productivity.
- Extension Compatibility and Installation Issues: Some users report incompatibility of Copilot or other extensions with specific VS Code versions, causing warnings, crashes, or non-functionality. Others experience problems with extension updates breaking functionality or causing persistent errors.
- Image and Media Handling Bugs: Multiple issues describe errors related to image processing, including invalid image URLs, unsupported image formats, oversized images causing request failures, and images disappearing from chat context after reload. These bugs cause request failures and disrupt workflows involving images.
- Agent and Tool Invocation Problems: Reports include agents failing to execute tools properly, subagents not receiving full toolsets, tool calls not being confirmed or logged, and agents entering loops or failing to complete tasks despite indicating progress. These issues undermine the reliability of AI-assisted coding workflows.
- Search and Workspace Loading Failures: Some users report workspace search failures on specific architectures, inability to open folders or files, and issues with Remote-SSH causing search and quick open to fail, often resolved by rolling back VS Code versions.
- Accessibility and UI Usability Issues: Problems include lack of screen reader announcements for split views, inaccessible dropdowns, confusing icons, and overlapping UI elements, which hinder users relying on assistive technologies or keyboard navigation.
- Miscellaneous Bugs and Feature Requests: Other issues include requests for improved telemetry, sandboxing enhancements, better error messages, UI polish, and feature additions such as text-to-speech, macro support, and improved chat customization.
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.
-
Copilot is not working at all in MAC
- Toxicity Score: 0.75 (Rapid escalation, confrontational language, gatekeeping accusations, name-calling)
- This GitHub conversation begins with a user seeking help and others requesting clarification and additional details in a polite tone. The discussion shifts when a user suggests a workaround, which triggers a defensive and confrontational response from another participant accusing the first of giving inappropriate advice. Subsequent comments include apologies and attempts to de-escalate, but tensions rise again as users debate the legitimacy of contributions and gatekeeping behavior, culminating in name-calling and dismissive remarks.
-
VS code (1.113) stopped showing me
user profileprompt files from my UserData on windows- Toxicity Score: 0.85 (Rapid escalation, aggressive language)
- This GitHub conversation features a single comment from a user expressing strong negative sentiment and frustration towards the software, using aggressive and dismissive language. The tone is hostile and unconstructive, with no engagement from other participants or attempts at resolution. The comment triggers tension by attacking the software rather than addressing the issue constructively.
-
- Toxicity Score: 0.65 (Rapid escalation, sarcastic remarks, accusatory tone)
- This GitHub conversation begins with the original poster expressing confusion and frustration about an issue with their PRO+ account. Subsequent comments reflect escalating irritation, with one user sarcastically criticizing the application and implying misuse of resources. The tone shifts from confused to accusatory, indicating growing tension among participants.
-
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, unresolved frustration)
- This GitHub conversation involves a user expressing strong dissatisfaction and frustration regarding the service, emphasizing unmet expectations and perceived unfairness. The tone is highly emotional and accusatory, with the user repeatedly highlighting their negative experience and financial concerns. There is no evidence of responses or attempts at resolution from other participants, which may contribute to the user's escalating frustration. This lack of engagement and the user's intense language suggest a potential for continued negative interactions.
-
its not working wont let me use it. if this isnt fixed in 24 hours i will quit your services.
- Toxicity Score: 0.65 (Rapid escalation, threatening language, urgent tone)
- This GitHub conversation involves a single user, deathdcl, who reports a critical issue with a service and expresses frustration with a firm deadline for resolution. The tone is urgent and somewhat threatening, indicating dissatisfaction and a potential decision to discontinue use if the problem is not fixed promptly. There are no responses or interactions from other users, so the conversation remains one-sided with a high level of tension implied by the initial message.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, spam content)
- This GitHub conversation consists solely of an initial post by a user with no subsequent comments or interactions, featuring nonsensical content and labeled as spam, indicating no engagement or constructive dialogue.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, lack of moderation)
- This GitHub conversation consists of a single initial comment by one user expressing strong dissatisfaction and using profane language, with no subsequent comments or interactions. The tone is highly negative and aggressive, and the issue is labeled as spam, indicating a lack of constructive engagement or resolution.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms)
- This GitHub conversation features a user expressing strong frustration and anger towards the GitHub Copilot tool and Microsoft, using aggressive and offensive language. The tone is highly negative and confrontational, with no attempts at constructive dialogue. The initial comment triggers a tense atmosphere likely to provoke defensive or equally hostile responses.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, profanity, one-sided frustration)
- This GitHub conversation involves a single user expressing strong frustration and anger about a rate limit issue, using aggressive and profane language. The tone is highly emotional and confrontational, triggered by repeated interruptions due to the rate limit. No other participants or responses are present to moderate or escalate the discussion.
-
- Toxicity Score: 0.75 (Rapid escalation, offensive language, lack of constructive dialogue)
- This GitHub conversation involves a single user posting a message with repetitive and potentially offensive language, accompanied by detailed system and environment information. The tone is neutral in the technical details but the use of language in the main message suggests frustration or provocation. There are no responses or interactions from other users, and the issue is labeled as spam, indicating a lack of constructive engagement and potential for negative reactions if the conversation were to continue.
-
- Toxicity Score: 0.75 (Rapid escalation, offensive language, spam label)
- This GitHub conversation involves a single user posting a message with repetitive and potentially offensive language, accompanied by detailed system and environment information. The tone is neutral in the technical details but the use of language in the main message suggests frustration or provocation. There are no responses or interactions from other users, and the issue is labeled as spam, indicating a lack of constructive engagement and potential for negative reactions if the conversation were to continue.
-
Гребанные дебилы во главе с маньяком Идийцем
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, spam labels)
- This GitHub conversation involves no user comments but includes labels indicating the issue is considered invalid and spam, suggesting a negative initial reception and potential disregard by the community.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, lack of moderation)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with a software issue, using highly negative and aggressive language. There are no responses or interactions from other users, and the tone is entirely hostile and confrontational. The lack of engagement or moderation contributes to a stagnant but potentially volatile environment.
-
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, unresolved frustration)
- This GitHub conversation consists of a single initial comment by one user expressing frustration and confusion regarding a technical issue, using strong language that conveys anger and urgency. There are no responses or further interactions, so the tone remains unmoderated and potentially volatile. The lack of engagement or attempts at resolution leaves the situation unresolved and the sentiment negative.
-
User tools and Interface issues!!
- Toxicity Score: 0.65 (Rapid escalation, aggressive language, dismissive response)
- This GitHub conversation involves a user expressing strong dissatisfaction and frustration with recent updates, using all caps and exclamatory language to emphasize their grievances. A respondent points out that the issue is a duplicate, which may contribute to the user's heightened frustration. The tone is tense and confrontational, with the original poster feeling ignored or misunderstood, and the response potentially perceived as dismissive. This dynamic suggests a buildup of tension triggered by perceived lack of resolution and communication.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with a service, using aggressive and profane language without any responses or further discussion. The tone is highly confrontational and the message is emotionally charged, indicating a potential for conflict if others were to engage.
-
500 Internal Server Error when using custom models
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, hostile tone)
- This GitHub conversation begins with a user reporting a technical issue and providing detailed logs and settings to seek help. The initial comment from another user, identified as @vs-code-engineering, expresses a highly negative and hostile sentiment with a confrontational and aggressive tone, which introduces tension into the discussion. There is no evidence of constructive dialogue or resolution attempts following this comment.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms, no moderation yet)
- This GitHub conversation consists of a single initial comment by a user expressing intense frustration and dissatisfaction with a product, using highly aggressive and offensive language; no other participants have engaged, so there is no shift in tone or sentiment, and the issue has been labeled as spam.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, one-sided hostility)
- This GitHub conversation involves a single user expressing intense frustration and anger using profane language directed at the service provider, triggered by a rate limit error message. The tone is highly aggressive and hostile, with no other participants or attempts at resolution visible. The conversation is marked by a lack of constructive dialogue and a strong emotional outburst.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, explicit profanity)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with a system, using emphatic and negative language that conveys anger and disappointment. The tone is confrontational and accusatory, with no responses or attempts at resolution visible in the thread. The lack of engagement from others and the user's use of explicit language suggest a potential for escalating tension if further comments occur.
-
- Toxicity Score: 0.75 (Rapid escalation, suspicious content, spam label)
- This GitHub conversation involves a single user posting a message containing a suspicious external link, with no subsequent comments or interactions. The tone is neutral but the content triggers concern due to the nature of the link and the spam label applied by moderators. There is no visible sentiment or dialogue, but the presence of spam indicates potential for negative reactions if the conversation were to continue.
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: 168
Key Open Pull Requests
1. sessions: polish run task quick input modal: This pull request polishes the Agent Sessions "Run Task" quick input modal by adding close and back buttons, refining spacing, alignment, and styling for improved visual consistency, updating labels and copy for clarity, and scoping modal-specific styles to enhance the user experience while keeping changes localized to this interface.
- URL: pull/304652
- Associated Commits: 6fecd, 2c7db, 6cd08, f98fe, dc781, d7769, 8affc, 8ea20, b849e, c7a32, 0ecf7, a7812, 6c558, 3322c, 6ac14, c507e, e93c1, 8c8de, 29e11, c1a6b, f9ba7, 35319, 98d86, e16e5, c0aaf, debd6, 0b2e4, a7b7a, 4a5ab, cc0f9, e5288, 5df29, 3e33a, 30622, 8a197
2. Enable CLI DevTunnel sanity tests: This pull request enables CLI DevTunnel sanity tests by refactoring the test code into a separate file, adding retries around the authentication flow, capturing screenshots on test failures, and addressing various fixes and improvements to ensure reliable test execution.
- URL: pull/305807
- Associated Commits: 77cf8, 29d17, 3f363, dda6a, 8d67d, 70458, c1181, 35026, a5c20, 6c72a, f7918, 475ae, 2fc3c, 2c3e8, d451f, e452e, d3a8f, 60532, dacc8, fba18
3. Add SSH remote agent host bootstrap: This pull request introduces an automated SSH-based bootstrap flow for connecting to a remote agent host in VS Code, which streamlines the process by SSH-ing into the remote machine, installing the VS Code CLI if needed, starting the code agent-host service, forwarding the agent host port through an SSH tunnel, and integrating this functionality into the UI with a multi-step connection flow and a new command, all implemented with dynamic imports to comply with layering rules.
- URL: pull/304882
- Associated Commits: f89f5, 56453, b1018, 5e598, 1d65b, 81d31, bb557, d738c, 31a72, 7700a, e7123, 4a8e2
Other Open Pull Requests
- GitHub Actions workflow fixes: These pull requests address stability issues in the Linux/Electron GitHub Actions workflow by analyzing logs, fixing root causes, and adding tests to ensure reliability. Changes include environment variable adjustments to enable retries without sandboxing and updates to existing tests.
pull/304884
- Sign-in and session UI improvements: Updates to the sign-in experience introduce the first step of the first-time use flow for sessions, enhancing walkthroughs, accessibility, and UI elements like logos and icons. Additionally, the Sessions app update dialog was simplified to an informational-only dialog with cleanup of unused code.
pull/304307, pull/305346
- Theme and UI enhancements: Migration of legacy color theme defaults preserves user preferences by pinning last applied themes and setting appropriate defaults for light and dark modes. UI improvements include fixing update bugs, setting the title bar UI as default, removing legacy components, and enhancing scrollbar visibility.
pull/305631, pull/306251, pull/305757
- Chat and inline widget improvements: Enhancements to the chat feature include refining cloud handoff availability based on Git repository presence and implementing horizontal clamping for the inline chat input widget to prevent it from going offscreen. These changes improve session-specific behavior and widget positioning.
pull/305877, pull/304795
- Terminal and link handling fixes: The terminal OSC-8 link feature was improved by aligning tooltips and click behavior with local file links, refining link detection, and preserving scheme allow prompts. A rendering fix on macOS high-resolution displays ensures terminal selection highlights align correctly with UI elements.
pull/306075, [pull/306133](https://github.com/pull/306133]
- Custom editor and outline API: A proposed extension API enables Custom Editor extensions to provide outline data for the Outline view, Breadcrumbs, and Go to Symbol quick-pick. This allows custom editors to supply hierarchical outline items and contribute to inline toolbars and context menus despite using non-standard text models.
pull/304909
- Context menu icon fixes: Fixes for missing icons in plain Action items in context menus include automatic icon rendering based on CSS classes, adding a separate icon element to prevent font issues, and ensuring icons remain visible regardless of checked state. Related tests and fixtures were updated accordingly.
pull/305371
- Code rendering and markdown fixes: Simplification of codeblock rendering in chat markdown addresses related errors and streamlines code. Additionally, markdown syntax highlighting was fixed to properly support multiline math expressions enclosed in single dollar signs by updating the TextMate grammar pattern.
pull/305845, pull/304800
- Avatar rendering and account UI: Functionality was added to render authentication account avatars by forwarding the GitHub
avatar_urlto display the avatar in the Accounts activity bar icon, while preserving the default icon when no avatar is available. Tests cover GitHub sign-in, window reload, and account visibility toggling.
pull/305902
- File creation and diff editor limits: Fixes to the create file process prevent indefinite runs by skipping save dialogs when filenames are provided and validating file paths. A configurable maximum file count limit was introduced to the multi-file diff editor to prevent freezing by truncating displayed documents and improving performance.
pull/305967, pull/304732
- Agent host session renaming and cleanup: Renaming of agent host sessions involved multiple commits with updates, fixes, cleanups, and comment resolutions, including co-authorship by Copilot. This improves clarity and maintainability of session management code.
pull/306204
- Performance optimizations: CPU usage was reduced by optimizing spinner animations with GPU compositor hints, motion preference support, and throttling animation timing functions. The
getNodeLocation()method in the tree widget was optimized by caching child indices to reduce complexity from linear to constant time.
pull/305610, pull/306226
- Environment variable support on Linux: Support for the
XDG_CONFIG_HOMEenvironment variable was added to determine the location of theargv.jsonconfiguration file on Linux, changing its resolution path while keeping macOS and Windows behavior unchanged. Relevant code and tests were updated to ensure correct functionality.
pull/305206
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: 437
Key Closed Pull Requests
1. sessions: Extensible sessions provider architecture and ISessionData migration: This pull request introduces a new extensible sessions provider architecture for the Agent Sessions window in VS Code, replacing scattered hardcoded session logic with a registry-based provider system, migrates all consumers from the deprecated IActiveSessionItem API to use the unified ISessionData interface exclusively, enriches session data with new observables like isArchived, isRead, and lastTurnEnd, removes deprecated APIs, updates over 20 consumers accordingly, implements new session providers including CopilotChatSessionsProvider and RemoteAgentHostSessionsProvider, and redesigns the sessions list view with improved grouping, sorting, and styling, thereby significantly refactoring and modernizing session management and UI integration.
- URL: pull/304626
- Associated Commits: 145f8, c74aa, 04a60, 9a465, f9cb8, 3d809, 6649b, 04247, d14d3, c6882, 73258, cffbf, 44c1d, 77c22, 8e380, 1fb16, ddab9, ee4db, aa208, ae2cd, 1ffee, 854b0, b903e, 91825, 2f251, 9988f, 694cd, aed0c, 3f403, fe640, cc576, 787f2, 07051, bc402, 4c766, f9b29, 45ffc, 889a0, d2c51, c347a, 9ea0e, f25b9, 3b5df, e760c, f43f1, 80c5d, 1c833, 48f38, 7b3bf, 40c5f, edfcf, 25632, 2d310, 542ff, fe5f1, ca85e, 21d07, e56dd, 1d85b, a5863, a8cbf, b196d, 66b06, 23392, 3594d, 50dd0, 17c1f, 1c394, df6ba, 1dea5, 161ad, 6e23f, 45e7d, 76dd7, 8364a, 1e5f1, c3147, 9947d, e2286, 1a351, 6961a, b9801, 8615f, 90e77, 3dbef, f080e, 63631, 16523, 46749, 0e5df, 9834d, 63695, 9fb9d, d377e, 8c36d, d1740, 2a3c5, 37daa, aa162, ac762, e04ba, 60fe2, f4345, a0ee5, 33d02, 7a257, c7d1c, 4a16a, 08d28, ed0d6, 7d30a, 0ec7e, bf50e, af1c4, efab4, 9a47d, a3ade, 80017, d6314, 01d26, c0c15, 9fbac, c398a, 9479a, 553af, 8fb0f, 1cfac, 1c4db, 1a5f5, 5ee23, 5c5ae, 7c8e5, 48518, 2316c, f880d, 638b6, 28b9f, 30af6, 90073, bb033, b7ba5, 09593, d8fae, 0d8ae
- Associated Commits: 145f8, c74aa, 04a60, 9a465, f9cb8, 3d809, 6649b, 04247, d14d3, c6882, 73258, cffbf, 44c1d, 77c22, 8e380, 1fb16, ddab9, ee4db, aa208, ae2cd, 1ffee, 854b0, b903e, 91825, 2f251, 9988f, 694cd, aed0c, 3f403, fe640, cc576, 787f2, 07051, bc402, 4c766, f9b29, 45ffc, 889a0, d2c51, c347a, 9ea0e, f25b9, 3b5df, e760c, f43f1, 80c5d, 1c833, 48f38, 7b3bf, 40c5f, edfcf, 25632, 2d310, 542ff, fe5f1, ca85e, 21d07, e56dd, 1d85b, a5863, a8cbf, b196d, 66b06, 23392, 3594d, 50dd0, 17c1f, 1c394, df6ba, 1dea5, 161ad, 6e23f, 45e7d, 76dd7, 8364a, 1e5f1, c3147, 9947d, e2286, 1a351, 6961a, b9801, 8615f, 90e77, 3dbef, f080e, 63631, 16523, 46749, 0e5df, 9834d, 63695, 9fb9d, d377e, 8c36d, d1740, 2a3c5, 37daa, aa162, ac762, e04ba, 60fe2, f4345, a0ee5, 33d02, 7a257, c7d1c, 4a16a, 08d28, ed0d6, 7d30a, 0ec7e, bf50e, af1c4, efab4, 9a47d, a3ade, 80017, d6314, 01d26, c0c15, 9fbac, c398a, 9479a, 553af, 8fb0f, 1cfac, 1c4db, 1a5f5, 5ee23, 5c5ae, 7c8e5, 48518, 2316c, f880d, 638b6, 28b9f, 30af6, 90073, bb033, b7ba5, 09593, d8fae, 0d8ae
2. sessions: Redesign session list with hover-reveal show-more, PR status icons, and compact layout: This pull request redesigns the agent sessions list in the sessions app by implementing a hover-reveal show-more/show-less feature with smooth height animations, adding pull request status icons, introducing compact layout options, and ensuring timestamps are always visible, all scoped specifically to the sessions app without affecting the core workbench session list.
- URL: pull/304637
- Associated Commits: 3ab55, fa984, 44497, 76dd8, b0d93, 1d107, e5e43, 6e8ea, e2226, 07489, ac75c, 61a25, ea887, 4e34d, 21739, 13b51, f3218, 1eeb4, cf9bf, 219c7, f6521, 934a7, 8a841, aad82, f78e5, 10c00, 0d3b8, 0fe94, adfcb, 53ffd, 25d01, 9191c, 06875, c7ab9, 39004, bc23c, bdfe9, 274a1, fda9a, 89534, d006b, 31880, 3f584, 29f9b, 23694, fade5, 2a7d6, b8fc7
- Associated Commits: 3ab55, fa984, 44497, 76dd8, b0d93, 1d107, e5e43, 6e8ea, e2226, 07489, ac75c, 61a25, ea887, 4e34d, 21739, 13b51, f3218, 1eeb4, cf9bf, 219c7, f6521, 934a7, 8a841, aad82, f78e5, 10c00, 0d3b8, 0fe94, adfcb, 53ffd, 25d01, 9191c, 06875, c7ab9, 39004, bc23c, bdfe9, 274a1, fda9a, 89534, d006b, 31880, 3f584, 29f9b, 23694, fade5, 2a7d6, b8fc7
3. Remove getInProgressSessionDescription from interface: This pull request proposes removing the getInProgressSessionDescription method from the service interface because it is not directly related to chat sessions and therefore does not need to reside on the service.
- URL: pull/304845
- Associated Commits: 004ec, 6112a, 2863f, 2cd17, 101eb, 31c34, e4052, bd46e, b92c0, 3bf51, 44130, ba911, bb193, dbd8e, a3e51, df2aa, fa8b3, 49062, bab42, d14c3, 4f098, aae76, 01885, 46490, ce3a0, 6ca79, ece2f, 3b79f, a44ba, c7da3, 73958, 4c6eb, 3c116, 3212c, df333, b8f01, 8675e
- Associated Commits: 004ec, 6112a, 2863f, 2cd17, 101eb, 31c34, e4052, bd46e, b92c0, 3bf51, 44130, ba911, bb193, dbd8e, a3e51, df2aa, fa8b3, 49062, bab42, d14c3, 4f098, aae76, 01885, 46490, ce3a0, 6ca79, ece2f, 3b79f, a44ba, c7da3, 73958, 4c6eb, 3c116, 3212c, df333, b8f01, 8675e
Other Closed Pull Requests
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 | 297 | 61 | 0 | 836 |
| sandy081 | 762 | 33 | 6 | 10 |
| bpasero | 351 | 80 | 24 | 20 |
| roblourens | 268 | 52 | 53 | 72 |
| joshspicer | 321 | 35 | 8 | 29 |
| mrleemurray | 262 | 51 | 1 | 3 |
| meganrogge | 222 | 28 | 11 | 51 |
| connor4312 | 205 | 32 | 6 | 24 |
| justschen | 173 | 28 | 4 | 21 |
| benibenj | 154 | 44 | 9 | 8 |