Weekly GitHub Report for Vscode: November 17, 2025 - November 24, 2025 (12:06:35)
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.
-
Arrow key gets “stuck” after switching Wayland workspaces using Super + Arrow keys (Fedora 43, GNOME): This issue describes a problem where, after switching GNOME workspaces on Fedora 43 using Super + Arrow keys under Wayland, VS Code behaves as if the arrow key is continuously pressed, causing the cursor to move endlessly until the key is pressed again. The problem is isolated to VS Code (and some other Electron-based apps) and appears related to how the Mutter window manager handles key events on Wayland, with workarounds including downgrading Mutter or launching VS Code with specific Wayland/Ozone flags.
- Multiple users confirm the issue occurs on Fedora 43 and Arch Linux with GNOME on Wayland, affecting VS Code and other Electron apps but not native GTK apps or browsers. The problem is linked to Mutter 49.1.1, with a temporary fix being to downgrade Mutter or run VS Code with Wayland-specific flags. A related Mutter bug has been identified and a fix merged, suggesting an upcoming update may resolve the issue.
- Number of comments this week: 13
-
Issue running subagent tool: This issue describes a problem where the #runSubagent tool in the Copilot Chat extension for VS Code intermittently stops working, requiring a reload of VS Code to function again. The user reports that the tool appears disabled despite being enabled in the tool picker, and certain models like Chat GPT 5.1-Codex-Mini never work with the subagent, indicating inconsistent tool availability and support across models.
- The comments include requests for logs and clarifications about whether the tool shows as disabled, with the user providing detailed logs and screenshots confirming the tool is enabled but still failing. Other users confirm similar issues, noting model compatibility problems and the need to toggle the tool off and on or reload VS Code to restore functionality, while maintainers request additional diagnostic logs to investigate the tool's behavior in requests.
- Number of comments this week: 8
-
"Edit, refactor and generate code" is duplicative and does not give additional meanings: This issue addresses the redundancy and lack of clarity in the placeholder text "Edit, refactor, and generate code" used in the inline chat feature, suggesting that "edit" and "refactor" are too similar and proposing a cleaner, more precise placeholder. The discussion focuses on how to best phrase the placeholder to reflect the context of code selection or cursor location, with suggestions to dynamically change the placeholder based on whether code is selected or not.
- The comments explore various alternative placeholder texts, debating the inclusion of phrases like "in this file" and whether the placeholder should dynamically change depending on the presence of a code selection. Participants agree that the UI context implies the file scope, and they consider options such as "Modify selected code" and "Generate" to improve clarity and reduce redundancy.
- Number of comments this week: 7
-
Pressing
F5doesn't capture the active file for${file}immediately sometimes resulting in launching the wrong file: This issue describes a problem where pressingF5in VS Code does not immediately capture the active file for the${file}variable, sometimes causing the debugger to launch the wrong Dart file that lacks amainfunction. The user experiences this specifically when working with the Dart SDK, and the problem appears to stem from a delay between pressingF5and when VS Code resolves the debug configuration, leading to an incorrect file being substituted.- The comments discuss attempts to reproduce the issue and explore possible causes, including delays caused by tasks like
preLaunchTaskor extension activation events, but no such tasks or conflicting extensions were found. It is suggested that VS Code should capture the active file immediately upon pressingF5to avoid this timing issue, and a clarification on the issue title was proposed to better reflect the problem. - Number of comments this week: 7
- The comments discuss attempts to reproduce the issue and explore possible causes, including delays caused by tasks like
-
Gemini 3 Pro: Stream terminated: This issue reports that the Gemini 3 Pro feature in GitHub Copilot is frequently failing with a "Stream terminated" server error, causing interruptions and making the tool effectively unusable for some users. The problem appears linked to unexpected tool calls or missing tool definitions, and it may be exacerbated when processing large amounts of code or using older versions of VSCode.
- The comments discuss possible causes such as undefined tools triggering unexpected calls, share multiple request IDs showing the error, and note that updating VSCode may help but does not fully resolve the issue; users express frustration as the problem persists and renders Gemini 3 Pro unreliable.
- Number of comments this week: 7
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 outlines to include dynamically generated content from code cells, improving usability by reflecting changes made through code rather than only static markdown cells.
- 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 rather than opening alongside it in a separate window.
${userHome}in a task command creates bad paths: This issue describes a problem where using the${userHome}variable in a task command within VS Code'stasks.jsonfile generates incorrect file paths when the task type is set to "process," causing the terminal process to fail to start due to invalid executable paths. The reporter notes that while${userHome}works correctly when the task type is "shell" with PowerShell as the default shell, it produces malformed paths in the "process" type, and that using${env:USERPROFILE}is a viable workaround that results in properly formatted paths.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where the terminal in a floating window does not echo typed characters in real time when connected to a remote environment, such as WSL or SSH, if the main VS Code window is minimized. The characters only appear after restoring the main window, indicating that the remote connection may enter a sleep state when the main window is minimized, preventing immediate terminal updates despite the terminal not being truly frozen.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is pasted into Visual Studio 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: 581
Summarized Issues:
- JSON Format Errors in Tool Calls: Multiple issues report recurring 400 errors caused by invalid JSON format in tool call arguments, affecting various VS Code extensions and models. These errors prevent successful requests and responses, leading to failures in tool usage and user frustration.
- No Response / Unresponsive Extension: Numerous reports describe the VS Code extension (mostly version 0.33.1 and 0.33.2) failing to return any response or becoming unresponsive during use. Users experience repeated "Sorry, no response was returned" messages, inability to get code completions, or the extension ignoring inputs, severely impacting productivity.
- Performance and Freezing Issues: Several issues describe severe performance degradation, freezing, or hanging of VS Code or its extensions, including slow startup, unresponsive UI, freezing during Git commits, and excessive memory or CPU usage. These problems affect various platforms and VS Code versions, causing workflow interruptions and user frustration.
- Chat and Agent UI Bugs: Multiple issues report problems with the chat interface and agent sessions, including missing or irrelevant buttons, incorrect or missing chat history, inability to manage or select models, confusing UI elements, and inconsistent session behavior. These issues cause confusion and reduce usability of the chat and agent features.
- Model Selection and Availability Issues: Users report problems with model selection, including inability to select or see models despite having subscriptions, models not loading or being unavailable, and confusing or missing model information in the UI. These issues hinder users from effectively using AI features.
- Agent and CLI Session Bugs: Several issues describe bugs in agent and CLI sessions, such as sessions not continuing in the background, lost file changes, inability to stop running commands, and problems with delegation or session management. These bugs disrupt workflows involving background or delegated tasks.
- Copilot Chat and Extension Crashes: Multiple reports indicate crashes or freezes caused by the GitHub Copilot Chat extension, including crashes on startup, crashes triggered by file modifications, and extension host crashes on remote machines. These crashes cause loss of work and require restarts or disabling extensions.
- issues/278333, issues/278928, issues/278970, issues/278617, [issues/278715](https://github.com/issues/278715]
- Terminal and Shell Integration Issues: Several issues describe problems with the integrated terminal, such as endless spinning on queries, focus stealing, native crashes on macOS, and errors when running commands in specific shells or environments. These issues affect terminal usability and integration with VS Code features.
- issues/277730, issues/277961, issues/278571, issues/278517, [issues/278746](https://github.com/issues/278746]
- Model Hallucination and Incorrect Output: Some issues report AI models hallucinating or producing incorrect, nonsensical, or incomplete outputs, including fabricated code lines, repeated loops, and truncated responses. These problems reduce trust and effectiveness of AI assistance.
- issues/277862, issues/278252, issues/278425, issues/278713, issues/278578, issues/278827, [issues/278510](https://github.com/issues/278510]
- Subscription, Billing, and Access Problems: Users report issues related to subscription status, billing errors, inability to access paid features or models despite having subscriptions, and confusion over usage limits or payment prompts. These issues cause frustration and limit feature access.
- issues/277797, issues/278095, issues/278459, issues/278721, issues/278977, [issues/278953](https://github.com/issues/278953]
- UI and Design Problems: Several issues highlight UI inconsistencies, confusing or missing controls, poor visual hierarchy, and design regressions in dropdowns, buttons, icons, and chat scrollbars. These problems degrade user experience and accessibility.
- issues/277746, issues/278433, issues/278437, issues/278504, issues/278799, [issues/278851](https://github.com/issues/278851], issues/278862
- Workspace, File, and Git Integration Issues: Multiple reports describe problems with workspace context, file handling, Git integration, and worktree support, including missing branch indicators, incorrect diff views, and issues with multiple repositories or worktrees. These issues complicate source control and project management.
- Model and Feature Requests: Some issues propose new features or improvements, such as structured workflows, RTL text support, AI-guided prompt creation, better model information display, and improved session management to enhance usability and developer productivity.
- Authentication and Authorization Failures: Several issues report OAuth and authentication problems, including invalid redirect URIs, repeated permission requests, and 401 unauthorized errors during tool or server usage, causing failures in accessing services or completing workflows.
- Extension Installation and Update Failures: Some users experience problems updating or installing extensions, including signature verification failures, missing files, or unexpected uninstallations, which disrupt extension usage and require manual intervention.
- issues/277936, issues/278329, [issues/278957](https://github.com/issues/278957]
- Accessibility and Keyboard Navigation Issues: A few issues highlight accessibility problems such as non-focusable buttons, improper keyboard navigation, and screen reader incompatibilities, impacting users relying on assistive technologies.
- Miscellaneous Bugs and Errors: Various other bugs include crashes on file save dialogs, incorrect syntax highlighting, broken inline completions, and problems with specific language support or debugging features, affecting diverse aspects of the VS Code experience.
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: 355
Summarized Issues:
- GitHub Copilot and Language Model Failures: Multiple issues report that GitHub Copilot and related language models frequently fail to respond properly, returning errors such as "Sorry, no response was returned," 400 Bad Request, or timeout errors. These failures affect various models including GPT-5, Gemini 3 Pro, Claude Sonnet 4.5, and Codex, causing incomplete answers, request rejections, and unusable chat sessions across different platforms and VS Code versions.
- issues/277663, issues/277688, issues/277691, issues/277724, issues/277732, issues/277733, issues/277734, issues/277739, issues/277740, issues/277742, issues/277744, issues/277747, issues/277748, issues/277772, issues/277803, issues/277804, issues/277805, issues/277813, issues/277833, issues/277939, issues/277952, issues/278001, issues/278005, issues/278078, issues/278084, issues/278085, issues/278094, issues/278205, issues/278259, issues/278265, issues/278279, issues/278289, issues/278290, issues/278292, issues/278309, issues/278313, issues/278326, issues/278336, issues/278363, issues/278368, issues/278384, issues/278401, issues/278439, issues/278440, issues/278441, issues/278448, issues/278546, issues/278552, issues/278570, issues/278572, issues/278573, issues/278574, issues/278576, issues/278579, issues/278584, issues/278619, issues/278621, issues/278632, issues/278633, issues/278664, issues/278666, issues/278674, issues/278718, issues/278722, issues/278754, issues/278756, issues/278760, issues/278764, issues/278772, issues/278773, issues/278775, issues/278789, issues/278823, issues/278834, issues/278848, issues/278864, issues/278876, issues/278937, issues/278950
- Terminal and Integrated Console Issues: Several issues describe bugs in the VS Code integrated terminal including freezing, hanging commands, duplicated lines on resize, and crashes triggered by terminal commands like Clear Console. Problems also include terminal tabs not hiding correctly, terminal panel not closing automatically, and terminal input focus or interaction failures.
- Rate Limiting and Token Usage Problems: Users report unexpected and strict rate limiting despite paid subscriptions or low usage, causing interruptions and inability to use Copilot features. Complaints include lack of transparency about limits, rapid token usage, and persistent rate limit errors even after waiting.
- Model Selection and Compatibility Issues: Several issues highlight problems with selecting or using specific AI models in VS Code, including Azure OpenAI models lacking chatCompletion support, Mistral AI model requests, Gemini 3 Pro and Gemini 2.5 Pro failing with 400 errors, and incompatibility of Vultr LLMs due to schema mismatches. Users also report inability to select models or errors indicating "language model unavailable."
- VS Code Crashes and Freezes: Multiple reports describe VS Code crashing or freezing on startup or during use, including segmentation faults on macOS Apple Silicon, crashes triggered by terminal commands, and freezes caused by GitHub Copilot integration tests or agent mode operations.
- Source Control and SCM Graph Bugs: Issues include the Source Control Graph not expanding nodes properly, missing branch and tag information on hover, and missing or removed buttons like Refresh and "Open in Git Graph," complicating user workflows.
- Chat History and Session Management Problems: Users report loss of chat history, duplicate chat entries, and issues with chat session lifecycle such as automatic disappearance of background chats and problems with archiving or restoring chat context.
- Performance and Responsiveness Issues: Several reports describe slow operation, freezing, or unresponsiveness in VS Code or its extensions, including slow inline suggestions, long summarization times, and delays in hover tooltips or UI updates.
- Extension Installation and Signature Verification Failures: Users encounter signature verification failures when installing popular extensions like Python, PHP, and GitHub Copilot on Linux x64, preventing successful extension installation.
- Workspace and Project Handling Bugs: Issues include VS Code failing to load multiple directories in workspace file search, freezing when running C# tests due to project conflicts, and code actions not working in multi-project .NET 8 workspaces.
- UI and UX Improvement Requests: Requests include better sorting and filtering of default formatter settings, improved hover tooltips showing relative file paths, color differentiation in debug console for warnings/errors, and split button UI enhancements for clarity.
- Release and Milestone Management: Detailed documentation and checklists exist for preparing, testing, and releasing major VS Code milestones such as October 2025 Recovery 1 and 2, covering version bumps, candidate reviews, multi-platform builds, and sanity testing.
- Authentication and Account Issues: Problems include persistent sign-in prompts, failure to pass default GitHub account to policy diagnostics, and MCP server continuing to run after sign-out, disrupting expected authentication flows.
- Miscellaneous Bugs and Requests: Other issues cover a wide range of topics such as inability to save files in Docker containers due to storage errors, missing compare option for unsaved files, incorrect CRON expression evaluation, and requests for UI font customization and middle-click paste support in terminals.
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 has lost all context and ability to assist
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, user frustration, direct insults)
- This GitHub conversation begins with a user providing detailed system information and reporting an issue, followed by a support member responding politely and requesting clearer information or re-uploaded files to assist. The tone shifts abruptly when another user expresses frustration with aggressive language directed at the support team, escalating tension. A third user joins, echoing the frustration and criticizing the software update and support quality, reinforcing the negative sentiment and conflict.
-
No sabes ni documentar lo básico.
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, profanity, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and dissatisfaction with the product, using aggressive and profane language. There are no responses or further interactions, so the tone remains unchallenged and the tension is solely triggered by the user's negative sentiment and harsh wording.
-
- Toxicity Score: 0.55 (Moderate possibility, Defensive responses, Curt tone, Frustration, Miscommunication)
- This GitHub conversation involves multiple users expressing frustration and dismissiveness regarding the handling of an issue related to hallucinations in a tool. The initial user conveys distress and disappointment, while subsequent commenters respond with a mix of defensive and curt tones, suggesting alternative approaches or deflecting responsibility. Tension arises from perceived miscommunication and unwillingness to engage constructively, with some comments exhibiting impatience and dismissiveness.
-
- Toxicity Score: 0.65 (Rapid escalation, confrontational tone, accusatory language)
- This GitHub conversation involves a single user expressing strong frustration and dissatisfaction with the support received, using accusatory and emotionally charged language. The tone is confrontational and dismissive, with no responses or engagement from other participants, which may contribute to the user's escalating negativity. The lack of interaction and the user's perception of being ignored appear to be the main triggers of tension.
-
i paid a hundred bucks to get rate limitted ?
- Toxicity Score: 0.65 (Rapid escalation, sarcastic language, provocative references)
- This GitHub conversation begins with the original poster expressing frustration about an unexpected limitation despite payment, followed by a comment that introduces sarcasm and a dismissive tone, referencing a public figure in a provocative manner. The interaction shows early signs of tension due to perceived lack of transparency and dissatisfaction, with the tone shifting towards sarcasm and potential disrespect.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, hostile tone, lack of moderation)
- This GitHub conversation consists of a single initial comment by a user expressing extreme frustration and anger in an aggressive and hostile tone, using strong language and capitalization to emphasize their dissatisfaction. No other participants have contributed, so there is no dialogue or resolution. The tension is triggered by the user's negative experience with the software, leading to a highly emotional outburst.
-
locate-shell-integration-path unrecognised option
- Toxicity Score: 0.65 (Rapid escalation, accusatory language, defensive responses)
- This GitHub conversation involves multiple users including the original poster and contributors such as @bpasero and @rzhao271. The tone shifts from neutral and informative to increasingly defensive and accusatory, with one user blaming the original poster for following problematic advice, which triggers tension. The discussion escalates as users dispute responsibility and the relevance of the issue, culminating in a call to stop creating duplicate reports.
-
- Toxicity Score: 0.55 (Moderate possibility, frustration, accusatory tone, perceived dismissiveness)
- This GitHub conversation involves a user expressing frustration and disappointment towards the handling of an issue by the maintainers, criticizing the closure of a related ticket and the lack of effective solutions. The tone is increasingly negative and accusatory, with the user feeling ignored and dissatisfied with the responses. The tension is triggered by perceived inaction and dismissiveness from the maintainers, leading to a confrontational sentiment.
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: 63
Key Open Pull Requests
1. add streaming for the terminal inlined in chat: This pull request introduces streaming capabilities for the terminal embedded inline within the chat interface, enhancing real-time terminal rendering and interaction.
- URL: pull/278888
- Merged: No
- Associated Commits: 14e4e, 2e244, 1e913, b3a58, 130d8, 6ec21, 8bd0b, d93fa, ef9ea, 20101, 3a84c, 928d3, 8beee, 11893, db19c, 0dcf9, 0d260, 49c7d, fea49
2. Refactor watermark entry management and improve styling: This pull request aims to simplify the management of watermark entries in the editor and improve the layout styling by adjusting structure and CSS for better alignment and spacing, including adding a toggle action for watermark visibility and removing unused styles and certain watermark entries.
- URL: pull/278758
- Merged: No
- Associated Commits: da623, f71db, f0d94, 7190f, eb3e3, 57d0f, c37ee, 7361c, 3aebb, d1e1b, 4776b, 52f8a
3. chore: enable BinSkim on Linux: This pull request enables BinSkim scanning on Linux build agents while removing the unused BinSkim configuration from the macOS build template to streamline the build process.
- URL: pull/278183
- Merged: No
Other Open Pull Requests
- Versioning and Pipeline Improvements: This topic covers adopting a new versioning format for non-stable builds along with related pipeline fixes and simplifications by exposing prerelease as an environment variable. The changes include cleanup and adjustments to support this new versioning approach.
[pull/278366]
- Streaming Partial Tool Data: Pull requests in this area introduce support for streaming partial tool data by enabling each tool to handle its own messaging during data streaming. Progress messages are updated dynamically as partial invocation data is received and processed.
[pull/278640]
- Workspace Symbol Search Fixes: These pull requests fix issues where workspace symbol search results disappeared when queries contained special characters by normalizing queries and updating fuzzy matching logic. This ensures compatibility with language servers like rust-analyzer that use special characters as query modifiers.
[pull/277922]
- ChatService Disposal and Memory Leak Fixes: This topic includes fixes to the disposal process in ChatService by correcting the onDidDispose method to ensure proper cleanup of disposable resources and prevent memory leaks.
[pull/278917, pull/278245]
- Terminal Confirmation Prompt Fix: This pull request fixes an issue where the "Continue waiting for
<command>?" prompt in the terminal did not hide properly when exceptions occurred by correcting state comparison logic and adding test coverage for prompt hiding in all scenarios.
[pull/278391]
- GitHub Custom Agents and Subagent Enhancements: These pull requests add support for GitHub Custom Agents with cleanup, caching fixes, and agent usage adjustments, and propose enhancements to list and execute agents as subagents by incorporating XML, tool variables, and an infer attribute.
[pull/278251, pull/278624]
- Chat History and Sessions View Caching: This topic covers the removal of chat history from the agent sessions view and the implementation of a caching mechanism for chat sessions that serializes and deserializes local sessions to workspace storage for instant UI feedback. The caching mirrors the existing agent sessions cache pattern adapted for per-provider architecture.
[pull/278958, pull/278901]
- Codicons and UI Updates: Pull requests here update the project to use codicons from the npm package, including related commits for codicon updates, environment service initialization, and lint error fixes.
[pull/278593]
- McpServerMetadata Icons Support: This pull request adds support for icons in the McpServerMetadata interface by introducing an
iconsarray property with fields likesrc,mimeType,sizes, andtheme. It extends the validation schema and merges extension-provided icons while prioritizing server-provided icons during initialization.
[pull/278167]
- Integrated Browser Feature: This pull request introduces a work-in-progress integrated browser feature including initial implementation, code cleanup, refactoring, and structural organization.
[pull/278677]
- Agent HQ UI Transformation: This pull request transforms the command center into an "Agent HQ" with a center-locked overlay modal, reactive session tracking, updated UI elements, and intuitive controls for managing agent sessions.
[pull/278894]
- Chat Setup Retry Limits: This pull request adds retry limits to chat setup, sign-in, and installation processes by introducing a retryCount parameter capped at three attempts to prevent infinite retry loops.
[pull/277791]
- Merge Editor Button Label Fix: This pull request fixes mis-labeled "Accept all..." buttons in the merge editor by swapping incoming and current labels to reduce confusion as reported in issue #251975.
[pull/278396]
- WSL Build Task Diagnosis: This pull request attempts to diagnose and resolve the issue causing the WSL build task to fail in the project.
[pull/278495]
- AI-Generated Chat Session Titles: This pull request introduces AI-generated chat session titles with a new secondary title bar, removes a planned arrow back button, and adjusts title formatting based on activity bar position and view count.
[pull/278874]
- Editor Cursor Highlight Setting: This pull request adds a new boolean editor setting
editor.cursorSurroundingLinesHighlightOnSelectionthat preserves the current line highlight during text selection, fixing the issue where the highlight disappeared on selection.
[pull/278886]
- Gulp Files TypeScript Conversion: This pull request converts gulp files to TypeScript by adding proper types, making necessary casts, and including small cleanups while minimizing runtime changes.
[pull/278893]
- macOS PR Build Fixes for Broken Symlinks: This pull request fixes macOS pull request build failures caused by GitHub Actions'
hashFiles()erroring on broken symlinks by adding cleanup steps, verifying cache key files, and adding debug output in the workflow.
[pull/278963]
- ChatWidgetService Adoption: This pull request adopts the
ChatWidgetService.openSessionmethod in various components to streamline session handling and simplify the codebase by removing unnecessary dependencies onIChatWidgetService.
[pull/278973]
- Standardizing Learnings Sections: This pull request standardizes Learnings sections across multiple agent instruction files by reformatting content and adding best practice notes in a consistent format for clarity and contextual relevance.
[pull/278245]
- Global Search Bug Fixes: These pull requests fix bugs in the global search feature by correcting dismissal of other files and adding missing foreground color to search match results for improved readability and contrast.
[pull/278328, pull/278371]
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: 258
Key Closed Pull Requests
1. stream content to inline chat terminal: This pull request implements streaming of terminal command output to an inline chat terminal by managing a rolling buffer that incrementally appends VT data, applies efficient snapshot diffs to update the view, and provides helper functions to control rendering and replay of streamed content while addressing issues like prompt overlap and scrollbar visibility.
- URL: pull/278219
- Merged: No
- Associated Commits: 2e585, 7586f, e14f1, 70520, b9bd6, 15201, b45bf, aa7a5, b3f38, b2d71, ec493, e2023, cc346, 58039, d5c66, 8bf36, 8e9b1, 1bce5, 0ab49, 27558, 259bf, a7ef2, 0ac87, fe103, cbb7d, e38cd, 58eb2, 30786, 8ccbc, cebf1, 5299e, 0fc02, a6d99, 539a5, 74d93, fe9a4, e3b1f, be813, cec1a, 47c0a, a92e2, 03e54, 008bc, 2ce23, cb5c4, adaa6, 8b216, 31021
2. render xterm instead of html for the chat terminal output: This pull request updates the chat terminal output in the VSCode project to render using xterm.js instead of HTML, improving terminal rendering and fixing issue #276946.
- URL: pull/278684
- Merged: Yes
- Associated Commits: 0a1d2, aaec5, 45b4b, 536d3, e0ddb, cf6f1, 1a6bd, 7c64b, 14292, 88ae0, c3736, 4dc64, 16783, 97c9a, 95741, 58473, 7b2d6, 5c756, aa2f8, 84bce, 149a6, 013dd, 73282, 865f6
3. Manage ChatModels with ref-counting, allow running in bg: This pull request implements reference counting to manage ChatModels and enables them to continue running in the background, improving resource management and functionality as part of addressing issue #277318.
- URL: pull/278476
- Merged: Yes
- Associated Commits: e2d0d, 66929, 74715, 7aa13, cf3fe, dddaf, 5ff2f, c552c, fc085, 1beaf, 31fdc, e748a, 279dd, 5aff2, 9f2c7, 72ce3, 85966
Other Closed Pull Requests
- Command decorations in chat terminal: Multiple pull requests enhance command decorations in Visual Studio Code's chat terminal by improving placement, accessibility, and integration while fixing related CSS and bug issues. These changes consolidate the implementation and polish hover content calculation to improve the overall user experience.
- Agent mode UI and delegation improvements: Updates to the UI keep the Agent mode option visible but disabled with a lock icon and tooltip when managed by group policy, preventing user selection. Additionally, handoff actions are enhanced by showing all "continue on" delegation targets in a dropdown, allowing users to choose between local, cloud, or background agents.
- Local and remote terminal profile handling: Improvements focus on better differentiation and handling of local versus remote terminal profiles, especially for macOS to Linux and development container scenarios. This ensures more accurate tracking and creation of terminal profiles in Visual Studio Code.
- Tree view UI refinements: Several pull requests simplify tree views by hiding twisties and removing indentation when nodes have flat hierarchies or no children, and by reducing excessive spacing between the twistie and checkbox. These changes improve the UI layout and address specific issues related to tree view display.
- EligibleForAutoApproval feature enhancements: The
eligibleForAutoApprovalfeature is introduced and refined with policy configurations, edge case fixes, user disclaimers, UI improvements, and smart auto-suggest functionality for tool reference names. These updates help control and manage automatic approval eligibility within VS Code.- pull/277943, [pull/278254](https://github.com/pull/278254]
- Keyboard shortcuts and telemetry improvements: Registration of keyboard shortcuts and actions is moved to a contrib file, with added telemetry events for focus and toggle output actions. Attempts to convert these actions to use
Action2were made but ultimately not implemented.
- Live progress tracking and state caching: Live progress tracking for local chat session descriptions is implemented using progress observables, providing real-time updates. State caching is optimized and memory leaks are prevented through improved listener management.
- Chat model and input state management: The chat model disposal process is refactored to enable model reuse and introduces a new
ChatModelStorefor better management. Input state is centralized into a unifiedinputStateon the model to allow consistent state transfer across chat panels, editors, and sessions.- pull/278683, [pull/278896](https://github.com/pull/278896]
- Chat context provider API and session filtering: Changes to the chat context provider API include implementing workspace chat context, while session filtering is enhanced with comprehensive test coverage to exclude sessions based on provider types and handle dynamic updates.
- pull/278135, [pull/278026](https://github.com/pull/278026]
- Terminal command execution timeout: A timeout is implemented to prevent the chat agent from hanging indefinitely when executing terminal commands by considering a command finished if expected sequences do not occur within one second.
- [pull/278165](https://github.com/pull/278165]
- Git migrate changes refactor: The Git migrate changes functionality is reworked by adding an extension API, removing the staged option, and cleaning up code and commands to improve the migration process.
- [pull/278426](https://github.com/pull/278426]
- Performance improvements in base directory: A micro-performance improvement prompt analyzes and optimizes Map usage for has/get and has/delete operations in the src/vs/base directory, including performance measurement, reporting, and user-directed application of changes.
- [pull/278411](https://github.com/pull/278411]
- Toolset updates and organization: The
launchandshelltoolsets are replaced with theexecutetoolset, with a compatibility layer added betweenshellandexecute. Terminal tools are moved to thereadcategory, and a minor fix preventsrunTestsfrom appearing at the top level.- [pull/278628](https://github.com/pull/278628]
- UI improvements for untitled prompt files: A delegate button is added to untitled prompt files to enhance the user interface for handling these files.
- [pull/278811](https://github.com/pull/278811]
- Hover functionality refactor in SCM graph: Hover code for history items in the source control management graph is extracted into a separate file, with enhanced tooltips and fixes for compilation errors and feedback to improve code organization and user experience.
- [pull/278778](https://github.com/pull/278778]
- Editor default formatter dropdown sorting: The sorting logic for the "Editor: Default Formatter" dropdown is improved to prioritize extensions that contribute actual formatting providers, ensuring popular formatters appear first and non-formatters like Copilot Chat appear later without breaking backward compatibility.
- [pull/277828](https://github.com/pull/277828]
- Task running detection fix: Task running detection is fixed by replacing
getActiveTaskswithgetBusyTasksto more accurately detect busy tasks, adding a wait of up to one second before creating the output monitor to prevent premature idle detection on slow machines.- [pull/277866](https://github.com/pull/277866]
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 | 522 | 107 | 0 | 648 |
| meganrogge | 417 | 18 | 71 | 260 |
| Tyriar | 171 | 9 | 104 | 329 |
| bpasero | 227 | 48 | 110 | 153 |
| mjbvz | 181 | 13 | 36 | 69 |
| roblourens | 82 | 14 | 46 | 152 |
| lszomoru | 184 | 16 | 18 | 70 |
| connor4312 | 90 | 19 | 24 | 97 |
| aeschli | 89 | 15 | 17 | 95 |
| jrieken | 79 | 7 | 34 | 82 |
Don't miss what's next. Subscribe to Weekly Project News: