Weekly GitHub Report for Vscode: October 27, 2025 - November 03, 2025 (12:04:48)
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.
-
can u put my coding langugae in vscode: This issue is a feature request from a user who created their own programming language called Zeta and wants the Visual Studio Code team to officially add support for it, including its file type (.zeta), directly into VSCode. The user emphasizes that they have developed the language's components and firmware and requests that the VSCode team integrate Zeta as a built-in language rather than as an extension.
- The comments clarify that adding a new language to VSCode requires creating an extension, with links provided to the official extension development documentation. The user expresses reluctance to create an extension themselves and seeks the VSCode team’s help to integrate Zeta natively, but contributors explain that this is not how language support is typically added, suggesting either building an extension or hiring someone to do so.
- Number of comments this week: 10
-
VS Code Speech not Working in Visual Studio Code Insiders Edition (Version: 1.106.0-insider): This issue reports that the VS Code Speech extension is not functioning correctly in the Visual Studio Code Insiders Edition on an Ubuntu 25.04 system running Wayland, where voice input is not converted to text and the GitHub Copilot Voice Chat feature also fails. The user has isolated the problem to the VS Code Speech extension after disabling other extensions, but encounters system stability issues related to GPU acceleration on Chromium-based browsers under Wayland, complicating the reporting and debugging process.
- The discussion involved detailed troubleshooting steps including enabling trace logging for the speech extension, reproducing the issue, and sharing output logs showing repeated aborts of speech-to-text sessions; the user also generated and uploaded crash dump files for further analysis, while clarifications about the Remote Extension Host and system resource limits on Linux were provided, and the investigation was escalated for deeper examination by the development team.
- Number of comments this week: 6
-
[URGENT] [IMPORTANT] Auto Allow Dropdown is missing since todays update...: This issue reports that the "Auto Allow Dropdown" feature, which lets users always allow certain commands in the Copilot Chat extension for VS Code Insiders, has disappeared following a recent update. The user describes inconsistent behavior where the dropdown intermittently appears and disappears, and notes that the available options are fewer compared to the stable version.
- Commenters observed the dropdown reappearing and disappearing unpredictably without restarting VS Code Insiders, with some noting partial restoration of functionality. Further investigation was requested, including sharing settings and command details, as recent changes in the Insiders build might affect this feature's behavior.
- Number of comments this week: 5
-
Insiders icon are blurry as compare to current stable build: This issue reports that the icons in the Insiders build appear blurry compared to those in the current stable build, with specific concerns about the clarity and design of certain icons such as the copy and diff-multiple icons. The user highlights inconsistencies in icon border placements and overall legibility, prompting a discussion about aligning icon design elements for better visual coherence.
- The comments include clarifications about which icons are being referenced and explanations of recent updates to improve legibility. The discussion addresses the inconsistency in border placement on file-type icons, with a commitment to work with the icon designer to standardize the stacking direction and improve the overall icon design.
- Number of comments this week: 5
-
Context menu in watch during debugging not working: This issue reports a problem where the context menu in the Watch window during debugging in VS Code does not open, preventing actions like copying variable values. The user experiences this issue on Kubuntu 24.04 with gdb and C++, and it appears related to the Variables pane being hidden during an active debug session, as the context menu works when the Variables pane is visible.
- The discussion involved attempts to reproduce the issue on different systems and configurations, with one participant unable to replicate it on Ubuntu and Windows. The original reporter confirmed the problem persists even without debug extensions and shared code and launch configurations. It was discovered that hiding the Variables pane causes the Watch context menu to fail, and this behavior was reproduced by another commenter who is now investigating a fix.
- Number of comments this week: 5
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request to enable code cells in the notebook outline to display markdown content generated dynamically by the code, similar to how JupyterLab handles titles in its outline view. The requester wants an option for the outline to recognize and show these markdown outputs from code cells, enhancing the dynamic and interactive capabilities of the notebook interface in VS Code.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue reports a bug in Visual Studio Code where using a vscode:// link with the query parameters ?new-window or ?reuse-window does not behave as expected when opening remote SSH connections. Instead of opening a new window or reusing the existing one, the current remote connection is disconnected and replaced by the new connection, causing loss of the original session.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set toprocess, 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 no actual freeze occurring.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is pasted into VS Code, it is incorrectly rendered as a question mark instead of displaying the correct symbol. The problem occurs on Fedora 39 with VS Code version 1.87.2, and the character displays properly in other applications like Firefox, indicating a rendering or font handling bug within VS Code.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 502
Summarized Issues:
- Agent Mode Code Application Issues: Multiple reports indicate that agent mode in the VS Code extension often fails to apply suggested code changes despite showing correct responses or indicating success. Users experience silent failures where code is not updated, no "keep code" button appears, or changes revert unexpectedly, causing significant workflow disruption and frustration.
- Chat Interface Stop Button Missing: The chat interface in the Copilot Chat extension lacks a stop button while the model is generating responses, preventing users from interrupting ongoing processes. This causes the model to continue running and modifying files beyond the intended scope, leading to user frustration.
- Performance and Responsiveness Problems: Numerous issues report severe slowness, freezing, or unresponsiveness in the VS Code extension, especially version 0.32.3 and 0.32.4 on Windows 10 and Darwin arm64 systems. Problems include infinite loading, chat freezing, high CPU usage, and failure to provide suggestions or responses, significantly impacting usability.
- issues/273417, issues/273419, issues/273427, issues/273438, issues/273476, issues/273652, issues/273746, issues/273786, issues/273994, issues/274080, issues/274340, [issues/274534](https://github.com/issues/274534]
- Network and Connectivity Errors: Users frequently encounter persistent network errors such as connection resets, timeouts, and repeated "Sorry, there was a network error" messages in the Copilot Chat extension. These errors occur despite stable internet connections and cause failures in submitting chat requests or receiving responses.
- issues/273464, issues/273952, issues/274489, [issues/274507](https://github.com/issues/274507]
- Premium Features and Subscription Access Problems: Several users report being unable to access premium features or see premium content despite having active subscriptions or added budgets. Issues include missing premium features in chat, incorrect premium request indications, and accusations of deceptive billing due to model version mismatches.
- issues/273430, issues/274138, issues/274465, issues/273950, [issues/273951](https://github.com/issues/273951]
- Chat Feature Freezing and No Response: The chat feature in the VS Code extension often freezes or fails to respond after input, with no visible feedback or output. This includes issues where chat remains stuck on "Working…", no chat content displays, or the chat window fails to update until restarting VS Code.
- issues/273713, issues/273566, issues/273569, issues/273884, [issues/273762](https://github.com/issues/273762], [issues/274110](https://github.com/issues/274110]
- Auto-Approval and Command Execution Issues: The auto-approve feature for terminal commands is inconsistent, especially with complex or environment-variable-containing commands, requiring repeated manual approval. Additionally, some commands cause hangs or errors, and the system sometimes misinterprets command syntax, blocking auto-approval.
- issues/273415, issues/273857, issues/274133, [issues/273887](https://github.com/issues/273887]
- Code Generation and Suggestion Quality Problems: Users report incomplete, incorrect, or overly aggressive code generation and suggestions from Copilot and GPT-5 agents. Problems include partial patches, hallucinated code, syntax errors introduced by Copilot, and inability to revert changes, leading to mistrust and workflow disruption.
- issues/273512, issues/273525, issues/273533, issues/273534, issues/273598, issues/273800, [issues/273785](https://github.com/issues/273785], issues/274024, [issues/274260](https://github.com/issues/274260], [issues/274330](https://github.com/issues/274330]
- Chat History and Conversation Management Bugs: Issues include incorrect summarization of conversation history, loss of chat sessions or conversations, inability to restore checkpoints properly, and repeated or duplicated chat content, causing confusion and loss of context.
- issues/273555, issues/273556, issues/274084, [issues/274522](https://github.com/issues/274522]
- Extension Crashes and Stability Issues: The VS Code extension host and Copilot extensions frequently crash or become unstable, sometimes due to missing declarations, native errors, or signature verification failures, rendering VS Code unusable or requiring restarts.
- issues/273855, issues/274095, [issues/274155](https://github.com/issues/274155], [issues/274233](https://github.com/issues/274233]
- Terminal and Shell Integration Problems: Users report issues with the integrated terminal including unresponsiveness, inability to type, slow output loading, incorrect shell usage, and UI problems such as hidden close icons or oversized right margins.
- issues/273753, issues/274495, issues/274526, [issues/274536](https://github.com/issues/274536], [issues/274306](https://github.com/issues/274306]
- UI and Accessibility Concerns: Problems include missing or misaligned UI elements such as close buttons, blurry icons, confusing chat scrolling behavior, lack of screen reader support for certain features, and inconsistent keyboard shortcut behavior.
- issues/273678, issues/273691, issues/273933, issues/273587, [issues/274211](https://github.com/issues/274211], [issues/274346](https://github.com/issues/274346]
- Model Selection and Switching Bugs: Selecting certain AI models causes automatic switching to other models or errors when switching between agents, especially when image attachments are involved, leading to failed requests or unexpected behavior.
- issues/273428, issues/274081, [issues/274111](https://github.com/issues/274111]
- Feature Requests for Improved Customization and Usability: Users request enhancements such as configurable truncation in search results, per-workspace response style persistence, command palette entries for agent creation, grouping of chat input suggestions, and multi-agent interfaces for parallel workflows.
- issues/273410, issues/273433, issues/273441, issues/273774, [issues/274126](https://github.com/issues/274126]
- Authentication and Account Management Issues: Problems include inability to sign in or out of GitHub Copilot, conflicting authorization flows causing errors, and incorrect account associations preventing proper syncing or access.
- issues/273695, issues/274073, [issues/274475](https://github.com/issues/274475], [issues/274533](https://github.com/issues/274533]
- File and Workspace Handling Bugs: Issues with file operations include inability to create folders, unexpected file deletions, failure to open or recognize folders, and problems with workspace chunk search or multi-folder workspaces.
- issues/273439, issues/273517, issues/274519, [issues/274499](https://github.com/issues/274499]
- Billing and Usage Discrepancies: Users report being charged for incomplete or non-applied code changes, receiving filtered responses without explanation, or being misled about subscription status and discounts.
- issues/274523, issues/274373, [issues/274270](https://github.com/issues/274270], [issues/274510](https://github.com/issues/274510]
- Extension Installation and Marketplace Issues: The Copilot Chat extension is missing from some marketplaces after repository renames, causing confusion for users of open-source VS Code distributions, and users face problems installing or downgrading extensions.
- issues/273508, [issues/273681](https://github.com/issues/273681]
- Miscellaneous Bugs: Other issues include problems with markdown hover command links, broken commit message language settings, and unexpected behavior in the chat input or terminal suggestion features.
- issues/273511, issues/273516, [issues/273732](https://github.com/issues/273732]
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: 285
Summarized Issues:
- Terminal and Chat Terminal Issues: Multiple issues report problems with terminal behavior in VS Code, including terminals not opening or showing expected output, focus and alignment problems, and terminals hanging or freezing during command execution. These issues affect both integrated terminals and chat-related terminals, causing user confusion and workflow interruptions.
- GitHub Copilot Chat and Extension Failures: Several issues describe bugs where the GitHub Copilot Chat extension fails to respond, crashes, or produces errors such as invalid JSON formats, rate limiting, or unexpected model switching. Users also report problems with authentication, premium request limits, and model availability, leading to degraded or unusable AI-assisted coding experiences.
- issues/273413, issues/273416, issues/273442, issues/273485, issues/273530, issues/273540, issues/273541, issues/273750, issues/273777, issues/273826, issues/273834, issues/273835, issues/273864, issues/273867, issues/273870, issues/273877, issues/273938, issues/273943, issues/274015, issues/274023, issues/274029, issues/274032, issues/274121, issues/274129, issues/274300, issues/274302, issues/274315, issues/274386, issues/274388, issues/274392, issues/274426, issues/274429, issues/274444, issues/274445, issues/274515, issues/274516
- Performance and Stability Problems: Users report severe performance degradation, freezing, memory leaks, and crashes in VS Code and its extensions, especially on Darwin arm64 systems and macOS with Apple Silicon. These issues include slow responses, indefinite hangs, and native crashes, significantly impacting usability and developer productivity.
- Authentication, Account, and Licensing Issues: Multiple reports highlight problems with signing out, switching accounts, applying student benefits, and managing premium or business licenses in GitHub Copilot and VS Code extensions. These issues cause confusion, denial of service, or unexpected behavior in account management and feature access.
- Request Failures and Network Errors: Numerous issues describe request failures with HTTP 400, 413, 408, 500, and 504 errors, often related to invalid JSON, large request bodies, or server-side problems. Network errors such as connection closures and SSL alerts also disrupt extension functionality, requiring users to retry or troubleshoot connectivity.
- issues/273342, issues/273426, issues/273431, issues/273455, issues/273486, issues/273498, issues/273633, issues/273709, issues/273798, issues/273814, issues/273870, issues/274048, issues/274052, issues/274130, issues/274184, issues/274185, issues/274184, issues/274429, [issues/274444](https://github.com/issues/274444]
- UI and Rendering Bugs: Several issues report visual glitches such as misaligned icons, incorrect tooltip behavior, gaps in UI elements, and rendering problems in markdown previews and terminal outputs. These bugs affect usability and accessibility, sometimes causing confusion or difficulty in interacting with the interface.
- Feature Requests and Usability Improvements: Users request enhancements such as event listeners for commands, separate file icon themes for light/dark modes, debouncing audio cues for screen readers, better progress indicators, and improved management of language models and account preferences. These requests aim to improve developer experience and accessibility.
- Agent and AI Model Behavior Issues: Reports include problems with agent sessions creating multiple entries, chat features stuck on "Working...", model dropdown rendering issues, and unexpected model switching or failures in AI responses. These issues degrade the AI-assisted coding experience and cause confusion.
- issues/273436, issues/273459, issues/273641, issues/273645, issues/273673, issues/273685, issues/273885, issues/274141, issues/274183, [issues/274300](https://github.com/issues/274300], issues/274302, issues/274351
- Extension Crashes and Runtime Errors: Multiple issues describe runtime errors such as "Cannot read properties of undefined (reading 'bind')" occurring in VS Code Insiders and other versions, causing extensions to fail or crash. These errors have affected GitHub Copilot Chat and related extensions, requiring updates or rollbacks to resolve.
- issues/274085, issues/274086, issues/274087, issues/274089, issues/274090, issues/274098, issues/274101, issues/274123, issues/274227, issues/274323, issues/274324, issues/274359, issues/274435, [issues/274386](https://github.com/issues/274386]
- Miscellaneous Bugs and Reports: Other issues include problems with folder visibility, image uploads, comment formatting, keyboard shortcuts causing unexpected behavior, and problems with saving or running code. Some reports lack sufficient detail or are placeholders without actionable information.
- issues/273409, issues/273411, issues/273372, issues/273808, issues/273554, issues/273764, issues/273784, issues/273971, issues/273977, issues/274010, issues/274151, issues/274401, issues/274517, [issues/274518](https://github.com/issues/274518]
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.
-
You faking Sonnet 4.5 but this is 3.5
- Toxicity Score: 0.65 (Rapid escalation, accusatory language, strong dissatisfaction, defensive responses, potential for further conflict)
- This GitHub conversation begins with a user expressing strong dissatisfaction and accusing the service of deception regarding the version and quality of a model they are paying for. Another participant responds curtly, warning against unfounded accusations, which escalates the tension. The original user then provides a detailed, evidence-based explanation to support their claims, maintaining a serious and formal tone. A third user replies with a conciliatory and professional tone, acknowledging the concerns and suggesting possible technical reasons while supporting further investigation. The conversation ends with another user expressing agreement with the original complaint and frustration, using strong language that implies distrust.
-
Request | Migrate VSCode to Tauri
- Toxicity Score: 0.65 (Rapid escalation, aggressive language)
- This GitHub conversation involves a user expressing a strong negative sentiment towards the feature request, using capitalized text that conveys frustration or dismissal. The tone is abrupt and confrontational, with no constructive engagement or elaboration. The trigger of tension appears to be the disagreement with the proposed migration, leading to a terse and potentially inflammatory comment.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, hostile tone, lack of moderation)
- This GitHub conversation consists of a single initial post by an anonymous user expressing extreme frustration and hostility through repeated profanity without any subsequent comments or engagement from other users. The tone is aggressive and confrontational, with no signs of constructive dialogue or resolution attempts. The lack of responses means no escalation or de-escalation occurs within the thread.
-
- Toxicity Score: 0.65 (Rapid escalation, disruptive content, lack of constructive dialogue)
- This GitHub conversation involves a single user posting a message that is flagged as spam, indicating a negative and disruptive tone. There is no further interaction or response from other users, and the conversation does not develop beyond this initial comment. The sentiment is neutral to negative due to the spam content, and the tone is abrupt. The trigger of tension is the spam message itself, which could provoke moderation or removal.
-
- Toxicity Score: 0.65 (Rapid escalation, inappropriate content, lack of constructive discussion)
- This GitHub conversation involves a single user posting a message that appears to be a spam command, with no further interaction or responses from other participants. The tone is neutral but the content is inappropriate for the context, potentially triggering moderation actions. There is no escalation or dialogue present.
-
- Toxicity Score: 0.65 (Rapid escalation, inappropriate content, lack of constructive discussion)
- This GitHub conversation involves a single user posting a message that appears to be a spam command, with no further interaction or responses from other participants. The tone is neutral but the content is inappropriate for the context, potentially triggering moderation actions. There is no escalation or dialogue present.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, hostile tone)
- This GitHub conversation involves a single user expressing strong frustration and using aggressive language directed at an unspecified party, with no responses or further interaction visible. The tone is hostile and accusatory, and the lack of replies suggests potential for escalation if others engage.
-
AI NOT FOLLOOWING ANY INSTRUCTIONS, SPENTING MY MONEY AND DO NOTHING
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, repeated expressions of frustration)
- This GitHub conversation involves a user expressing strong frustration and dissatisfaction with the AI's performance, using capitalized text and emphatic language, followed by a brief, similarly terse comment that suggests ongoing irritation. The tone is confrontational and exasperated, with tension triggered by perceived failure and wasted resources.
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: 53
Key Open Pull Requests
1. Creating biased random numbers from a cryptographically secure source: This pull request introduces a new feature that enables the generation of biased random numbers using a cryptographically secure source, thereby improving the application's capability to produce random numbers with specified distributions while ensuring strong security guarantees.
- URL: pull/273618
- Merged: No
- Associated Commits: ba48f, 133f3, d26c8, e5c57, 0e25a, 3a815, 2cf50, 532ef, 3cae1, 4cad9, e9155, e35a1, 7ae05, ea36d, e7f38, 83a28, 4d8ba, 18fb4, b3122, a6f8e, d0253, e7dcd, 0b416, 4512b, c46bb, 7598f, c3284, a912c, f834a, ce5f5, d0f97, 41fa3, ae034, 63d9d, bbb21, 3f688, 6acd1, 2011d, a90af, 8fdc5, 151c1, a93b7, ae429, d20e3, 08cde, 952b8, 949be, c5a81, 98e39, c0ed5, 04668, 9acd9, 24d93, 1c2f3, a846b, d6514, 458ff, c70d2, fb38c, 9e3af, f1bee, 17a6b, c30a3, 37db5, a384e, d73aa, de8c9, c93b7, 8f470, 80a99, 62783, 5615e, f2feb, 9a624, e3656, a899b, 91344, 0728a, 2433a, 800e2, 7767a, c21d0, f253b, 91f21, 73221, ef29e, 7a02b, 18a50
2. Expand hover setting to allow for key modifier mode: This pull request expands the existing hover.enabled setting in Visual Studio Code from a boolean to an enum with values on, off, and onKeyboardModifier, enabling hover tooltips to appear only when a specific key modifier (determined by the opposite of the current Multi Cursor Modifier setting) such as ctrl, cmd, or alt is held down, thereby providing more granular control over hover behavior.
- URL: pull/274001
- Merged: No
- Associated Commits: e44a2, 91258, b6731, 3d162, 3e4a3, ce013, 64468, d9615, e03fe, 983cc, 58d7b, 34d6d, 74ab6, 3817e, 03693, 3589d
3. Add per-PromptsType caching mechanism with URI-based lookup: This pull request implements a comprehensive per-PromptsType caching mechanism with URI-based lookup for prompt, instructions, and agent types, introducing new public methods to list and synchronously retrieve cached parsed prompt files, a unified event for cache changes, background cache population, robust cache invalidation, and improved test reliability without timing dependencies.
- URL: pull/273910
- Merged: No
- Associated Commits: c9003, c60af, f9b74, 70f79, f0c91, cd153, 66a95, 0a58e, 189c7, eeb58, 3c3d5, f9551, 27257
Other Open Pull Requests
- Chat and Conversation Enhancements: Multiple pull requests improve chat functionality by adding a contributable chat context feature with API cleanups and resource resolution improvements, enabling chat session sharing via shareable URLs, and ensuring full conversation history metadata is propagated to chat session agents. Additionally, support for switching to custom chat agents with keybindings and managing chat mode actions is introduced to enhance user interaction with chat features.
- Memory Leak Fixes: Two pull requests address memory leaks by properly disposing of disposable objects in the SessionViewPane and adding cancellation cleanup in the ChatEditorInput component to prevent leaks caused by rapid editor replacements during workspace chat clearing. These fixes improve resource management and prevent orphaned disposables from leaking memory.
- Git and SCM Improvements: Several pull requests enhance Git integration by adding
Revert CommitandReset Commitcommands to the SCM graph view, introducing ano-verifyoption to bypass pre-commit hooks with warnings, and fixing a bug to enable opening staged new files directly from Git. These changes improve commit workflows and user control over Git operations.
- Search and Ignore Functionality: Pull requests add native folder search support to the search service with new query types and integration tests, implement case-insensitive glob support for ignore files and ripgrep/file search, and mark
.ignoreand.rgignorefiles as belonging to the ignore language. These updates enhance search accuracy and ignore file handling across the project.- pull/274026, pull/274232, [pull/274063](https://github.com/pull/274063]
- Accessibility and UI Improvements: Accessibility is improved by adding screenreader support for terminal tool notifications using ARIA roles and keyboard navigation enhancements. UI updates include improving the Command Palette to show exact command matches without irrelevant suggestions and updating the QuickPick UI title and placeholder for clarity.
- Editor and IntelliSense Enhancements: A new per-language editor setting is introduced to exclude commit characters from accepting IntelliSense suggestions, preventing unintended commits in languages like C#. Additionally, a precondition is added to prevent the Enter key from triggering replace actions during text composition.
- pull/273592, [pull/273450](https://github.com/pull/273450]
- Terminal and Configuration Updates: One pull request attempts to generate the ITerminalConfiguration type using a JSON schema to improve type accuracy and consistency within terminal configuration code.
- Feature Flags and Mode Support: Support for disabling custom modes is added along with related fixes and updates to ensure proper functionality and passing tests.
- Sample Explorer Implementation: A minimal "Sample Explorer" view is implemented in the workbench, including service injection, sidebar container registration, startup integration, unit tests, and documentation, serving as a reference for custom explorer views.
- Search Result Preview Configuration: Configurable truncation options and size thresholds for search result previews are introduced, allowing users to control line truncation behavior and improve readability while maintaining default behavior for existing users.
- Code Renaming and Build Process: An attempt is made to use tsgo in LSP mode for property mangling to improve renaming, but it currently results in longer build times and unsuccessful compilation after bulk renaming.
- Learnings Tracking System: A learnings tracking system is implemented by adding standardized "## Learnings" sections to multiple instruction files, converting existing learnings to this format, enabling counters to track usefulness, and allowing users to add learnings on request.
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: 249
Key Closed Pull Requests
1. persist command in pty service, refactor how commands are restored on window reload for inline chat terminal: This pull request implements a system to pre-assign and persist command IDs for terminal commands executed by chat agent tools in the VSCode terminal, refactors the restoration of these commands on window reload for the inline chat terminal by introducing a terminalCommandId field and related methods to propagate and track command execution across the renderer and ptyHost, and removes the storage of command IDs from the chat service to centralize and simplify command ID management.
- URL: pull/274417
- Merged: Yes
- Associated Commits: 104b4, 64be1, 20662, 90984, 1c9cd, b0f1a, cf9fc, f4e6d, ec7ac, bafb6, 49de5, 4060a, 36388, d402d, 702e8, ffc12, 211e9, 21336, 5f724, a0869, a2aa2, 0df96, c1dc8, 40005, 8b14e, a7feb, 215d1, 9c6c8, 86f2d, c0174, 16738, b5ec5, 8fa79, 7860b, 47e57, ee28e, 866da, 354dc, 9b2e7, d404e, ca3c6, b60f1, 158c1, f2d7c, dd492, c81d9, f557a, fa993, 07f23, 194dc, 21fa0, 4d544, 754d2, 5767f, 341ba, 47baf, daf34, 6e752, fc741, 7013a, d8801, 02be8, db401, dc9f3, b770d, d2ecc, 5a80b, 92736, 5af57, f68c2, 5683f, 67ab4, 368c0, 064ac, 2196d, 880cd
2. Updates to Go To quick access: This pull request proposes updates to the "Go To" quick access feature by replacing previous case-sensitive glob implementations with a new case-insensitive glob API, specifically improving MIME type pattern matching and correcting minor spelling errors, although it was not merged.
- URL: pull/274222
- Merged: No
- Associated Commits: 69b99, 0bb62, fd5cf, 58c4b, bc5b8, 4d57d, acc51, 5c4eb, f0199, 26e1f, 013f1, 73a36, bd957, de3c8, 8cec3, 84f64, 71d87, 01dde, bef20, 807d4, d6366, ed216, 793c1, 8a1d5, 2701a, 0c2e0, df3bc, a818c, 3b699, 966d6, 28a1f, 249b9, 4d2ad, bfabe
3. Inline chat v2 updates: This pull request introduces updates to the inline chat v2 UI in Visual Studio Code by streamlining the interface with fewer commands, removing the request-response and "hide on request" modes, adding an exit tool for new intents, eliminating irrelevant suggestions and context, and improving the in-progress user experience.
- URL: pull/273986
- Merged: Yes
- Associated Commits: 58b89, 4de13, 4616d, 9c19c, e929d, 00fa6, e249e, f3d2c, 3971b, 0c472, 05d7e, 979bb, bb5ef, 371fe, 2bff4, f5c1e, 39ace, 0d86c, 19c26, 6d5c6, 12638
Other Closed Pull Requests
- Edit operations timeline refactor and agent edit integration: These pull requests refactor the edit operations timeline by replacing the snapshot-based model with an operation-based log to better track file changes and improve undo/redo functionality. Additionally, they introduce an integration point and callback API for external agents or CLI tools to perform edits recognized as agent-made, updating internal models accordingly.
- Terminal feature enhancements and fixes: Multiple pull requests improve the terminal experience by adding a user interface for managing terminal chat sessions, implementing detection of file redirection operations, adding a new setting to insert trailing spaces after command suggestions, and debugging terminal resize event handling. These changes include UI cleanups, command line analyzer integration, and refined resize implementations to enhance usability and reliability.
- Source Control Management (SCM) graph and artifact support: These pull requests add incoming and outgoing nodes to the SCM graph, improve rendering and functionality of the SCM history view, and introduce foundational plumbing to support artifacts within the repositories view. They also include event wiring and cleanup to handle changes in artifact groups and improve resource management.
- Chat and inline chat widget improvements: Pull requests enhance the chat feature by adding drag-and-drop support, context menus, extension installation actions, and provider-specific actions in the agent sessions view. They also improve the inline chat widget with UI tweaks, keybinding fixes, better input behavior, and removal of unnecessary actions to optimize user experience.
- Prompt file management enhancements: These pull requests add new commands and UI elements for managing prompt files, including a "Save as Prompt File" command and a blue button in the interface. They also introduce support for naming prompt files and include various fixes and updates related to untitled prompt files and action IDs.
- pull/274140, [pull/274020](https://github.com/pull/274020]
- Toolbar and UI responsiveness improvements: A pull request introduces a responsive option to the toolbar, refining width computations and improving rendering polish to enhance adaptability in the Visual Studio Code interface.
- TypeScript and JSON schema type safety improvements: These pull requests improve code quality by reducing explicit 'any' types in debug contributions and enhance type safety around JSON schemas for extension points. They add helpers for schema conversions, support for additionalProperties and array items, and improve checking of required versus optional properties.
- Glob matching enhancements: A pull request introduces an option to enable case-insensitive glob expressions and matching as a foundational step toward fixing related issues. The default remains case-sensitive, preparing for future enhancements that will utilize this new option.
- Code quality and linting improvements: A pull request adds a new ESLint rule disallowing the use of the
inoperator, including configuration, an ignore list, a utility function with tests, and updates to comply with the rule.
- Auto-approve functionality and analyzer integration: This pull request merges auto-approve functionality into the new analyzer, addressing related issues and simplifying code flows while removing unused comments.
- Performance improvements with caching: A pull request implements a temporary caching mechanism for Tree-sitter trees to improve performance and fixes a related issue, including test and code organization updates.
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 | 305 | 64 | 0 | 489 |
| Tyriar | 173 | 30 | 91 | 216 |
| meganrogge | 280 | 13 | 22 | 108 |
| bpasero | 191 | 38 | 69 | 109 |
| mjbvz | 178 | 42 | 14 | 81 |
| dmitrivMS | 211 | 17 | 2 | 59 |
| connor4312 | 64 | 13 | 12 | 140 |
| lszomoru | 158 | 38 | 5 | 22 |
| pwang347 | 151 | 10 | 1 | 18 |
| TylerLeonhardt | 45 | 9 | 14 | 98 |