Weekly GitHub Report for Vscode: July 21, 2025 - July 28, 2025 (12:03:56)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
The version released on March 12, 2025, primarily focuses on addressing a range of issues resolved under the "February 2025 Recovery 2" milestone. For detailed information, users are directed to the complete release notes available on the official Visual Studio Code updates page.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
Consistantly can't see terminal or gets confused about terminal: This issue reports a bug where GitHub Copilot Chat inconsistently fails to detect terminal output or becomes confused about the terminal state, particularly when running commands in a remote WSL2 environment with bash. The problem is linked to custom bash prompt configurations (specifically the use of the
bash-git-prompt), which interfere with Copilot's ability to parse command output, causing it to incorrectly report "command produced no output" despite output being present.- The discussion reveals that the root cause is the custom bash prompt interfering with Copilot's shell integration, and disabling the prompt restores proper output detection. Users shared detailed debug logs and terminal screenshots, confirming the issue occurs with certain prompt themes. A workaround involves deactivating the custom prompt or modifying it, but no perfect solution exists yet because Copilot cannot currently distinguish between normal terminals and those it opens; a dedicated environment variable was suggested as a potential improvement.
- Number of comments this week: 11
-
Ctrl + Tab stops working after moving terminal to new window and back: This issue reports that after moving an integrated terminal into a new window and then back into the panel in VS Code, the keyboard shortcut Ctrl + Tab stops working to cycle through open files until a new file is opened. The problem persists even with all extensions disabled and appears to be related to context keys not resetting correctly after the terminal is moved.
- The comments include initial attempts to reproduce the issue, confirmation that the problem affects Ctrl + Tab (not Shift + Tab), and suggestions to investigate context keys using developer tools. The user provided detailed steps and context key diffs to help diagnose the problem, which was acknowledged by maintainers and assigned to the appropriate owner for further investigation.
- Number of comments this week: 9
-
When 'Run Python File', it use 'conda run' instead of 'python': This issue reports a bug where the "Run Python File" command in VS Code uses the
conda runcommand with the--live-streamoption instead of directly invokingpython, causing the terminal output to refresh unexpectedly. The user observes that this behavior occurs when the "Python Environments" extension is enabled, and disabling this extension restores the expected behavior of running Python files normally.- The discussion identifies the "Python Environments" extension as the cause of the issue, with users confirming that disabling it resolves the problem. Comments also explore the rationale behind using
conda runto ensure the correct environment is activated, and attempts to reproduce the terminal refresh behavior with manual commands yield mixed results, indicating the issue may be specific to the extension’s interaction with the terminal. - Number of comments this week: 9
- The discussion identifies the "Python Environments" extension as the cause of the issue, with users confirming that disabling it resolves the problem. Comments also explore the rationale behind using
-
Copilot Chat: No models/providers shown in VS Code Insiders + WSL (UNKNOWN vendor errors): This issue reports that the GitHub Copilot and Copilot Chat extensions fail to display any models or providers in the VS Code Insiders edition when connected to a WSL remote environment, despite successful authentication and model metadata fetching. The developer console logs repeatedly show errors indicating that the chat model providers are recognized as "UNKNOWN vendor" for all model types, effectively blocking the use of Copilot Chat in this setup.
- Multiple users confirmed experiencing the same problem specifically with VS Code Insiders and WSL, noting that the issue started recently. Some found that opening a new VS Code window temporarily resolved the problem, while others tried reinstalling extensions and removing WSL versions without success. It was clarified that the pre-release version of Copilot Chat is required for Insiders, and the latest update released about 12 hours ago reportedly fixed the issue for some users.
- Number of comments this week: 8
-
Copilot agent says it's changing files, but files don't change: This issue describes a bug where the Copilot agent in VS Code reports that it is changing files and completing tasks, but the files remain unchanged despite these claims. Users have difficulty reproducing the problem consistently, but it appears to occur especially when using remote containers, and the issue persists across different AI models and VS Code versions, with some users noting it works in the Insider build but not the stable release.
- Multiple users confirm the problem where Copilot indicates file edits without actual changes, sharing experiences across stable and Insider VS Code versions, different AI models, and environments; some report the issue only occurs with remote container setups, others note UI elements like the new chat button become unresponsive, and attempts to follow debugging instructions fail due to outdated guidance.
- Number of comments this week: 8
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request asking for the ability to display markdown generated by code cells in the notebook outline, similar to how JupyterLab handles dynamic titles rendered in the output of code cells. The requester highlights that this functionality would allow for dynamic and programmatically generated outline entries, improving the usability of the notebook outline view 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 open a new window as expected, but instead hijacks and replaces the existing remote connection window. Specifically, when connected remotely to one server, clicking such a link to open a different remote server causes the current session to disconnect and be replaced by the new one, rather than opening a separate window for the new connection.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set to "process," causing the terminal process to fail to start. 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 does not occur in web browsers like Firefox, indicating a rendering or font support issue specific to VS Code on Fedora 39 with version 1.87.2.
2.3 Open Issues
This section lists, groups, and then summarizes issues that were created within the last week in the repository.
Issues Opened This Week: 510
Summarized Issues:
- Copilot Agent File Editing Failures: Multiple issues report that the GitHub Copilot agent in VS Code claims to edit files or complete tasks successfully but makes no actual changes to the files, causing confusion and workflow disruption. This problem occurs across different platforms including Windows and Linux, and affects various file types such as Jupyter notebooks and Markdown files, with some reports of files becoming blank or corrupted after agent operations.
- Copilot Extension Unresponsiveness and Performance Issues: Several reports describe the Copilot extension or agent becoming unresponsive, slow, or freezing VS Code, sometimes requiring restarts or causing long delays. These issues affect multiple OSes including Windows, Linux, and macOS, and involve symptoms like UI freezing, long startup times, and failure to respond to user input or commands.
- Authentication and Sign-In Problems: Multiple issues report difficulties with GitHub or Microsoft authentication in VS Code, including hanging sign-in processes, redirect loops, invalid token errors, and failures with two-factor authentication methods. These problems prevent users from accessing Copilot features or syncing settings, and occur on Windows and Linux systems.
- Copilot Chat and Agent Mode Bugs: Numerous issues describe bugs in the Copilot Chat extension and agent mode, including failure to apply edits, repeated loops editing the same files, inability to read terminal output correctly, and problems with mode switching or chat history. These bugs cause incomplete or incorrect code changes, UI glitches, and require frequent restarts or workarounds.
- Code Completion and Suggestion Issues: Several reports highlight problems with Copilot and VS Code code completions, including suggestions that interfere with manual editing, incorrect or irrelevant completions, inability to dismiss suggestions, and completions that cause syntax errors or are placed incorrectly. These issues degrade the coding experience and cause frustration.
- Terminal and Integrated Terminal Problems: Multiple issues describe bugs with the VS Code integrated terminal, including command navigation breaking with zsh prompts, terminal freezing or not starting automatically, incorrect or missing terminal output, and problems with running multi-line commands or detecting command completion. These issues affect workflows involving terminal usage and agent interactions.
- File and Workspace Management Bugs: Several issues report problems with file and workspace operations, such as inability to create, rename, or delete files and folders from the Explorer, unexpected creation of .vscode folders, issues with worktree management, and problems with file visibility or path handling in WSL environments. These bugs disrupt project organization and file handling.
- Extension Installation and Update Failures: Users report issues with installing or updating VS Code extensions, including signature verification failures, stuck update downloads, and extensions disabling themselves unexpectedly. These problems prevent users from maintaining or using extensions properly.
- UI and Accessibility Issues: Various bugs affect the VS Code user interface and accessibility, such as invisible cursors in certain themes, inconsistent toggle captions, screen reader navigation problems, overlapping folder visuals in Explorer, and missing scrollbars in input boxes. These issues reduce usability and accessibility for some users.
- Code Formatting and Diff View Problems: Some issues describe problems with code formatting features, such as Copilot making unwanted formatting changes, diff views not remembering word wrap settings, and inline suggestions not wrapping lines properly. These bugs affect code readability and editing convenience.
- Chat History and Context Management Limitations: Users report that chat history in Copilot Chat is not persisted across sessions or machines, that forced context prevents removing files from chat, and that chat search is slow or non-functional. These limitations hinder effective use of chat-based coding assistance.
- Model and API Integration Issues: Several issues describe problems with AI model integration, including models not loading, switching back to embedded models unexpectedly, failure to add or select certain models, and errors with API keys or token exhaustion. These issues impact the availability and reliability of AI features.
- Agent Mode Task and Tool Management Bugs: Reports include agent mode failing to complete tasks fully, duplicate tool entries appearing, agent loops editing the same file repeatedly, and issues with virtual tool activation and notifications. These bugs cause inefficiencies and confusion in automated coding workflows.
- Crash and Memory Leak Issues: Several users report crashes, out-of-memory errors, and resource leaks in VS Code, often triggered by large files, long chat sessions, or extension operations, leading to loss of work and degraded performance.
- Feature Requests for Usability Enhancements: Users request features such as detaching Copilot Chat into a separate window, toggling minimap visibility with keys, drag-and-drop reordering in the Outline panel, persistent chat history, and improved task lists in chat to enhance workflow and user experience.
- Miscellaneous Bugs: Other issues include problems with specific language support, incorrect error reporting, broken sanity tests, and problems with extension host crashes or unexpected behavior in specific scenarios.
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: 583
Summarized Issues:
- Extension Unresponsiveness and No Response Issues: Multiple reports describe the VS Code GitHub Copilot extension and related AI features becoming unresponsive, failing to return responses, or hanging indefinitely during operations. Users experience messages like "Sorry, no response was returned," with issues occurring across various versions (notably 0.28.5 and 0.29.1) and platforms including Windows 10, macOS, and Linux, severely impacting usability and workflow continuity.
- issues/252707, issues/252741, issues/252763, issues/254493, issues/255407, issues/255816, issues/255868, issues/255876, issues/256013, issues/256456, issues/256950, issues/257015, issues/257017, issues/257018, issues/257019, issues/257020, issues/257021, issues/257022, issues/257026, issues/257027, issues/257028, issues/257029, issues/257403, issues/257405, issues/257602, issues/257623, issues/257664, issues/257714, issues/257741, issues/257873, issues/257990
- Performance Degradation and Crashes: Users report severe performance problems including VS Code freezing, becoming very slow, crashing with out-of-memory errors, and high CPU or memory usage during normal operations or when using Copilot. These issues affect multiple platforms and VS Code versions, with some reports of repeated worker process terminations due to JavaScript heap memory limits and persistent lag during editing or terminal use.
- Network and Firewall Related Failures: Numerous issues describe network errors such as HTTP/2 protocol errors, connection resets, and access denied errors that prevent Copilot and related extensions from functioning properly. These errors often suggest firewall or network connection problems, though some reports indicate the issues persist despite verified healthy network conditions, causing request failures and inability to fetch models or complete operations.
- Model Availability and Quota Limit Issues: Many users report problems with model availability, including empty or missing model pickers, inability to select or switch models, and unexpected quota limit messages despite having active subscriptions or budgets. These issues cause forced downgrades to less capable models, repeated premium request limit warnings, and confusion about subscription status, severely limiting AI functionality.
- Code Generation and Editing Failures: Several issues describe Copilot and related AI extensions falsely reporting successful code changes without actually modifying files, overwriting user code unexpectedly, hallucinating incorrect links or code, or failing to apply requested edits. These problems cause significant disruption, loss of work, and frustration due to unreliable AI behavior and lack of recovery options.
- Terminal and Agent Mode Command Execution Issues: Users report problems with the Copilot agent and terminal integration, including creation of multiple unnecessary terminals, failure to reuse terminals, incorrect working directory assumptions, and commands hanging or failing to complete properly. These issues cause workflow interruptions, infinite loops, and require manual restarts to recover.
- Chat and Conversation Context Problems: Several reports highlight issues with chat features, including inability to create or switch chats, loss of conversation context after a number of exchanges, missing or non-functional UI elements like close buttons, and problems with editing or copying chat history. These bugs degrade the chat experience and hinder effective AI interaction.
- Extension Installation, Update, and Configuration Issues: Users face problems with extension installation, updates not applying, settings not being respected, and configuration files not updating as expected. These issues cause confusion and prevent users from properly managing their development environment.
- Accessibility and UI/UX Problems: Some issues report accessibility bugs such as VoiceOver cursor desynchronization on macOS, confusing or missing UI elements, poor discoverability of features, and inconsistent theme or color rendering. These problems affect usability for users relying on assistive technologies or seeking a polished interface.
- Code Completion and IntelliSense Issues: Reports include broken or degraded IntelliSense and syntax highlighting, autocomplete failures, and aggressive or irrelevant code completions that disrupt coding flow. These issues reduce developer productivity and cause frustration.
- Subscription, Licensing, and Payment Recognition Problems: Multiple users report that despite having active subscriptions or having paid for premium features, the system fails to recognize their status, incorrectly prompts for upgrades, or limits access to paid features, causing confusion and dissatisfaction.
- Buggy or Confusing AI Content Filtering: The Responsible AI Service frequently filters legitimate prompts or responses, causing users to receive messages instructing them to rephrase prompts or indicating that responses were blocked. This over-filtering disrupts normal usage and frustrates users.
- Feature Requests and Usability Improvements: Users request enhancements such as drag-and-drop support in SCM, inline test progress display, better model provider selection, persistent chat history, global AI disable toggles, and improved UI customization to enhance workflow and user experience.
- Miscellaneous Bugs and Environment Issues: Other problems include issues with environment variable loading, terminal prompt problems, file tree display failures, and extension signature verification errors, which affect specific workflows or platforms.
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.55 (Moderate possibility, repeated impatience, escalating urgency, unclear communication)
- This GitHub conversation involves a user expressing frustration and urgency about not receiving timely answers, with multiple brief and somewhat impatient comments directed at the community. The tone is increasingly demanding and anxious, while other participants respond with confusion or do not engage meaningfully, leading to a lack of resolution and growing tension. The repeated calls for attention and unclear communication contribute to a strained interaction.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment and accusing another party of dishonesty and sabotage, using emotionally charged language without any responses or further discussion.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive expressions)
- This GitHub conversation involves a single user expressing intense frustration and anger towards the software and its processes, using aggressive and offensive language. The tone is highly emotional and confrontational, triggered by difficulties encountered during setup and usage. There are no responses or interactions from other users, so the conversation remains one-sided with escalating negativity.
-
WFT, I am paying customer multiple times!!
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, strong emotional outburst)
- This GitHub conversation involves a single user expressing intense frustration and dissatisfaction with the product's performance, using strong language and emotional outbursts. The tone is highly agitated and accusatory, with no responses or interactions from other users to moderate or escalate the discussion. The primary trigger of tension is the user's repeated failures and perceived poor service despite being a paying customer.
-
Weather data not loading on mobile`
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, spam content)
- This GitHub conversation involves a single user posting a spam comment shortly after the issue was created, showing a dismissive and unconstructive tone. There is no engagement from other users, and the interaction is minimal with no resolution or further discussion. The presence of spam indicates a potential for disruptive behavior if the conversation continues.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment and accusing another party of dishonesty and sabotage, using emotionally charged language without any responses or further discussion.
-
VSCode Copilot bug disables to work!
- Toxicity Score: 0.65 (Rapid escalation, aggressive language)
- This GitHub conversation involves a user expressing frustration about an unresolved issue, with a response that conveys impatience and dismissiveness, leading to a tense interaction. The tone shifts from a user seeking help to a more confrontational reply, indicating a potential escalation in negativity.
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: 30
Key Open Pull Requests
1. add basic regex auto-reply support: This pull request introduces basic regex-based auto-reply support to the VSCode Copilot extension, addressing issue #16430 and laying the groundwork for future enhancements such as handling multiple prompts, foreground terminal support, delayed prompts, and improved option determination through LLM interaction.
- URL: pull/257691
- Merged: No
- Associated Commits: 530f9, 9a8b6, 26578, ad86a, bb7eb, 7993d, 97515, a8e21, b3c0f, 64324, e61a2, 6caaf, c7ef7, 1725d, 7a614, 98e45
2. Remove stale decoration when running watch activities: This pull request aims to remove the "stale" decoration that appears when manually running "npm run compile" in the terminal during watch activities, addressing the issue reported in microsoft/vscode#166864.
- URL: pull/257482
- Merged: No
3. Auto-select workspace TypeScript SDK in trusted workspaces: This pull request proposes modifying the TypeScript extension's version manager to automatically select and apply the workspace's TypeScript SDK in trusted workspaces without requiring explicit user opt-in, thereby eliminating redundant prompts and reducing friction for users in environments with frequently changing TypeScript SDK versions.
- URL: pull/257471
- Merged: No
Other Open Pull Requests
- Logging and Tracking Enhancements: This topic includes pull requests that add logging functionality for copy and paste actions and implement progress indicators in chat sessions to improve user experience during asynchronous operations. These changes enhance visibility into user actions and system processes without altering core functionalities.
[pull/257428, pull/257883]
- Grammar and Documentation Fixes: Several pull requests focus on fixing grammar, clarifying text in editor options, and correcting JSDoc comments to improve code clarity and documentation quality. These improvements make the codebase more understandable and maintainable.
[pull/256981, pull/257930, pull/257892, pull/257970]
- Chat and Session UI Improvements: This group of pull requests implements UI changes such as hiding checkpoint-related elements when a chat session is locked to a coding agent, preventing restoration of empty files on session restart, and refining chat response stream clearing with warnings. These updates streamline the chat interface and improve session handling.
[pull/257901, pull/257149, pull/257271]
- Language Server and Snippet Handling: Pull requests here remove Python REPL-specific elements from LSP completion to support multiple languages and fix Emmet snippets.json files to correctly support comments, eliminating erroneous syntax errors. These changes generalize language support and improve snippet file handling.
[pull/257744, pull/257878]
- OAuth and Authentication Fixes: This topic covers fixes to the MCP OAuth implementation by enabling dynamic client authentication methods, improving compatibility with servers requiring client_secret authentication. These changes enhance OAuth client_secret handling and registration processes.
[pull/257276, pull/257283]
- Code Editing and Text Manipulation Enhancements: Pull requests modify line-based actions like reverse, sort, and delete duplicate lines to apply to the entire document when a single line is selected, improving usability. Additionally, they address dynamic variable issues during request edits and propose editor integration for notebooks.
[pull/257975, pull/257281, pull/257911]
- Feature Proposals and Implementations: This includes work-in-progress implementations of the cot API with streaming, a prototype for LLM-based terminal auto approval, and a feature to refetch experimental values every 60 minutes to keep them updated. These pull requests introduce new capabilities and experimental features.
[pull/257170, pull/257053, pull/257149]
- Build and Workflow Improvements: A pull request proposes parallelizing the unzip step in the product build workflow for Darwin universal builds to improve efficiency. This change aims to optimize the build process.
[pull/257593]
- UI Usability Enhancements: This pull request modifies the debug toolbar to allow free dragging within the application window, improving usability by expanding the drag range and handling window events smoothly.
[pull/257970]
- Extension Development Resources: A pull request adds a complete "Hello World" extension demonstrating essential development patterns, serving as a learning resource and template for new VS Code extensions.
[pull/257754]
- Issue Reporter and Tooling Enhancements: This pull request introduces a dropdown feature in the issue reporter to enable previewing, improving the issue reporting experience.
[pull/257304]
- Codebase Modernization: A pull request proposes migrating the codebase to use AsyncIterableProducer, aiming to modernize asynchronous iteration patterns.
[pull/257043]
- Image Handling Fixes: This pull request ensures images generated from tool calls are properly resized and adds error handling to improve robustness.
[pull/257785]
- Copilot and Agent Mode Features: This pull request implements a copilot token flag specifically for agent mode and adds an account tag, enhancing agent-related functionality.
[pull/257892]
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: 191
Key Closed Pull Requests
1. Add default extension ( i.e odyssey ) which saves files on cmd + s or ctrl+s: This pull request proposes adding a default extension named "Odyssey" that enables saving files using the keyboard shortcuts cmd + s or ctrl + s.
- URL: pull/257817
- Merged: No
- Associated Commits: 6560a, 59f98, 18411, 84990, d04f3, 118f9, 2ca71, abe4a, 7ffa0, 19e0f, 6e116, 91fa9, 8affe, 39d90, 4c604, 09360, d197f, 848b8, d5159, 35d2b, bba3c, 56264, 88601, 0c198, fe5b2, ed563
2. add bg terminal output polling and cancellation option: This pull request introduces background terminal output polling along with an option to cancel the polling, enhancing terminal command handling and user control in the Visual Studio Code environment.
- URL: pull/256613
- Merged: 2025-07-21T17:23:01Z
- Associated Commits: 9c6bd, e81b5, 72d43, f644d, 95fbe, 681be, 34f3f, 93737, b4e12, 2cae8, 191e3, 0c244, 0c692, 93b01, 72a91, 41f79, 7b231, a18d9, f5a52, 49be5
3. fix remaining run task and task output issues: This pull request fixes the remaining issues related to running tasks and their output in the Visual Studio Code project, addressing the problems reported in issues #256555 and #256156.
- URL: pull/257306
- Merged: 2025-07-22T19:36:01Z
- Associated Commits: a35e2, 0addd, 7dd3a, 7f158, 508d4, 3c25e, 8d87d, 44db6, 4a870, 338ea, be30b, 0f4cc, 5b21c, 42175, 8a93a, 9ab3d, 7cef7
Other Closed Pull Requests
- Chat feature enhancements: Multiple pull requests introduce and improve chat-related features in Visual Studio Code, including a new chat sessions view with UI improvements, a coding agent chat prototype with direct model access and streaming demos, and accessibility enhancements for chat elicitation requests. Additional updates include reshaping the chat session API for better session identification and updating chat input placeholders to support extensions and commands in agent mode.
- Worktree and branch management improvements: Several pull requests enhance the create worktree feature by adding the ability to create new branches, improving error handling, enabling cancellation with the escape key, and automatically selecting the main repository context. These changes streamline the worktree creation process and improve user experience.
- Task and terminal functionality updates: Pull requests focus on improving task creation and execution by moving create and run task functionality to the core, adding output polling, and enhancing error handling. Terminal-related updates include fixing idle prompt hiding in chat elicitation requests and ensuring the LLM returns responses to prevent indefinite waiting during background terminal executions.
- UI and visualization improvements: Updates include rendering file changes at checkpoints with summaries of deletions and insertions, enhancing multi-file editor icons, adding support for separators in the action widget, and fixing hover behavior for "Modified Elsewhere" indicators in the Settings Editor. These changes improve the clarity and usability of the interface.
- Extension examples and integration: Two pull requests add simple "Hello World" extensions to the VS Code built-in extensions, demonstrating basic extension structure, command registration, activation, TypeScript compilation, and testing. Another pull request integrates the IChatPullRequestContent interface into a remote agent job action component to enhance functionality.
- Project and dependency updates: Updates include bumping the Electron version to 37.2.3 with related fixes and Node.js build updates, adding Chrome debugging configurations and chrome-remote-interface support (not merged), and managing device permissions through package identity. These changes maintain and extend project dependencies and capabilities.
- Code cleanup and refactoring: Pull requests remove redundant telemetry and unused services, eliminate obsolete interfaces and related compile errors, and clean up naming and structure in the chat session API. These efforts improve code maintainability and reduce technical debt.
- MCP server and trust model improvements: A pull request implements an on-by-default MCP autorun feature that automatically starts new or changed MCP servers upon chat requests, reworks the trust model to require user approval for workspace-level servers, groups server prompts to reduce notification overload, and refreshes tools in response to server definition changes.
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 |
|---|---|---|---|---|
| meganrogge | 151 | 13 | 27 | 163 |
| Tyriar | 119 | 18 | 63 | 133 |
| Copilot | 215 | 39 | 0 | 15 |
| bpasero | 122 | 1 | 46 | 34 |
| roblourens | 23 | 4 | 19 | 109 |
| lszomoru | 77 | 14 | 5 | 57 |
| justschen | 66 | 15 | 9 | 61 |
| connor4312 | 28 | 6 | 8 | 102 |
| mjbvz | 55 | 12 | 7 | 42 |
| sandy081 | 42 | 15 | 13 | 45 |