Weekly GitHub Report for Vscode: August 18, 2025 - August 25, 2025 (12:00:26)
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.
-
Test rich HTML screen reader content: This issue is about testing a newly introduced rich HTML screen reader content feature in the editor, which aims to improve screen reader alignment by rendering content with variable fonts similarly to how it appears in the editor. The goal is to verify that enabling this feature allows screen readers to correctly read and track editor content, addressing limitations of the legacy and previous implementations.
- The comments include requests for testing by experts, initial positive feedback, and reports of issues with screen readers not refreshing content changes unless lines are added or removed. Subsequent discussion points to a related fix pending deployment in Insider builds, with ongoing verification and some remaining problems reported in the latest versions.
- Number of comments this week: 8
-
Give time for file saves before refreshing git: This issue requests a feature to introduce a delay before refreshing the Git repository view to allow time for files to be saved, as the current refresh action may occur before focus-out triggered saves complete. The user suggests a timeout of around 500ms after clicking the refresh button to ensure that the displayed diffs accurately reflect the saved file state.
- The discussion clarifies that saving files typically triggers automatic refreshes, but the user relies on focus-out saves rather than manual saves, causing a timing issue when manually refreshing. Suggestions include using the built-in
files.autoSavewith delay settings or pressing Ctrl+S, while the user proposes a new setting to trigger saves when the cursor enters the sidebar to better synchronize saves and refreshes without increasing save frequency unnecessarily. - Number of comments this week: 8
- The discussion clarifies that saving files typically triggers automatic refreshes, but the user relies on focus-out saves rather than manual saves, causing a timing issue when manually refreshing. Suggestions include using the built-in
-
Keyboard Trap exists on New Tools button inside of Chat: This issue reports a keyboard trap bug occurring on the "New Tools" button within the chat feature of VS Code, where users are unable to navigate away using keyboard shortcuts, effectively getting stuck. The problem appears intermittently, with some users unable to reproduce it consistently, and it has been confirmed by the Enterprise Disability Answer Desk as well.
- The comments reveal multiple users experiencing the keyboard trap, with requests for clarification on which button is affected and attempts to reproduce the issue. A video demonstration was shared to illustrate the problem, and the discussion includes suggestions to capture the bug using screencast mode for further investigation.
- Number of comments this week: 7
-
sometimes the stream breaks, it needs a restart option: This issue reports a bug where the GitHub Copilot extension's inline completion stream breaks due to network-related fetch errors, specifically a "getaddrinfo EAI_AGAIN" error, causing the completion service to stop working until the user restarts their PC. The user requests a restart option within the extension to recover from this state without needing a full system reboot, as the problem persists across multiple VS Code versions and appears related to the plugin rather than the editor itself.
- The comments clarify that the error originates from inline completions triggered during typing and confirm that the extension effectively crashes and requires a restart of the PC to resume functionality. There is discussion about whether network issues like proxies or firewalls might be causing the repeated fetch errors, and no existing issue was found tracking this problem before.
- Number of comments this week: 7
-
Perf: showing Chat view on startup is slow: This issue addresses a significant performance regression caused by opening the secondary sidebar by default in workspaces, which adds 200-300ms to startup time due to the expensive rendering of the chat view. The discussion focuses on the inefficiencies in rendering the welcome content multiple times, with attempts to cache or simplify the rendering logic to reduce unnecessary re-renders and improve startup performance.
- The comments reveal that the welcome content is rendered repeatedly, causing excessive style recalculations and slowdowns. Various contributors discuss caching strategies and the complexity of the current rendering logic, with some attempted fixes being reverted and calls for a cleaner, more maintainable approach to managing the welcome view’s state and rendering behavior.
- 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 within 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 markdown to be included in the outline view, enhancing usability and aligning the behavior with that of JupyterLab.
- 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 opening a remote SSH connection to a new server via such a link, the current remote session disconnects and is replaced by the new one, rather than creating or reusing 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," 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, if the main VS Code window is minimized. The characters only appear after the main window is restored, 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 copied into Visual Studio 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 bug specific to 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: 489
Summarized Issues:
- Copilot Chat Agent Mode Failures: Multiple issues report that the Copilot Chat Agent mode frequently fails to modify files, produces nonsensical or empty responses, or gets stuck in infinite loops, rendering it unusable or causing unexpected behavior such as repeated file changes or failure to apply edits. Users also experience problems with the agent mode behaving like Ask mode, failing to apply code changes, or prematurely signaling success without completing tasks.
- Extension Version 0.30.x Stability and Functionality Issues: Numerous reports indicate that the VS Code extension version 0.30.x (especially 0.30.1 and 0.30.3) frequently becomes unresponsive, fails to generate code or answers, crashes, or does not load properly on Windows 10 and other platforms. Users also report problems with the extension freezing, failing to edit files, or producing empty or incorrect files despite indicating success.
- Authentication and Subscription Problems: Several issues describe users being unable to sign in or authenticate with GitHub Copilot in VS Code, including repeated login failures, subscription validation errors despite active payments, and continuous prompts to log in. These problems prevent access to Copilot features and cause significant disruption.
- Performance and Responsiveness Issues in VS Code and Copilot: Users report performance degradation such as slow editor responsiveness, freezing, high CPU usage, and delays in typing or switching tabs, often linked to Copilot or chat features. Some issues describe the editor becoming unresponsive after certain actions or during chat usage, with CPU spikes and long delays.
- File and Code Modification Failures: Multiple reports indicate that Copilot or the extension claims to have updated or modified code files but fails to actually apply changes, resulting in no visible updates despite success messages. This includes issues with file creation, editing, and deletion, sometimes causing data loss or corrupted codebases.
- Extension Signature Verification Failures: Several issues report that the GitHub Copilot extension and other extensions fail signature verification on macOS and Linux systems, preventing proper installation or functioning of the extensions.
- Chat Feature UI and Interaction Bugs: Users experience UI glitches such as chat input misalignment, inability to close inline chat, keyboard navigation traps, duplicated chat entries, and disappearing chat requests after sign-in. These issues degrade the chat experience and hinder usability.
- Git and Source Control Issues: Problems include failure to switch branches, source control panel not refreshing, discarded changes not updating working sets, and git push failures, causing workflow interruptions and confusion.
- Terminal and Shell Integration Problems: Issues include terminal freezing, inability to terminate processes, environment variables not updating, input method failures, and commands running despite cancellation, leading to poor terminal experience and potential data loss.
- Model and AI Behavior Issues: Reports include models ignoring instructions, producing repetitive or incorrect outputs, failing to apply edits, and generating irrelevant or broken code, leading to user frustration and reduced trust in AI assistance.
- Feature Requests for Usability and Workflow Improvements: Users request enhancements such as persistent filename hints, outline sorting by type, sound notifications, chat session saving and exporting, prompt queuing, improved extension management, better workspace switching, and more flexible model configuration options.
- Miscellaneous UI and UX Issues: Problems include cramped button layouts, inconsistent styling, misplaced UI elements, missing or confusing labels, and issues with keyboard shortcuts or focus management, all impacting user experience negatively.
- Crashes and Data Loss: Several reports describe VS Code or the Copilot extension crashing unexpectedly, sometimes causing loss of unsaved work, corrupted codebases, or requiring restarts to recover functionality.
- Extension and API Compatibility Issues: Some issues report incompatibilities with VS Code versions, API proposals, or extension APIs, causing errors or preventing extensions from functioning correctly.
- Search and Navigation Problems: Users report issues with search functionality hanging, incorrect ranking of search results, search highlights persisting after closing, and problems with navigation commands resetting cursor positions unexpectedly.
- Miscellaneous Bugs and Requests: Various other issues include problems with markdown preview, color themes, keyboard shortcuts, workspace management, and requests for new features or improvements not covered above.
- issues/262438, issues/262480, issues/262640, issues/262733, issues/262735, issues/262737, issues/262738, issues/262739, issues/262741, issues/262742, issues/262749, issues/262757, issues/262760, issues/262763, issues/262767, issues/262769, issues/262773, issues/262783, issues/262790, issues/262793, issues/262799, issues/262801, issues/262804, issues/262812, issues/262817, issues/262822, issues/262823, issues/262829, issues/262832, issues/262840, issues/262843, issues/262846, issues/262847, issues/262850, issues/262853, issues/262855, issues/262856, issues/262857, issues/262859, issues/262861, issues/262865, issues/262868, issues/262870, issues/262871, issues/262872, issues/262873, issues/262876, issues/262880, issues/262886, issues/262887, issues/262890, issues/262893, issues/262897, issues/262899, issues/262904, issues/262906, issues/262907, issues/262909, issues/262912, issues/262914, issues/262916, issues/262920, issues/262922, issues/262933, issues/262934, issues/262935, issues/262942, issues/262943, issues/262945, issues/262950, issues/262953, issues/262954, issues/262955, issues/262957, issues/262960, issues/262966, issues/262970, issues/262973, issues/262974, issues/262977, issues/262978, issues/262981, issues/262983, issues/262988, issues/262989, issues/262990, issues/262993, issues/262994, issues/263000, issues/263001, issues/263003, issues/263005, issues/263006, issues/263007, issues/263009, issues/263011, issues/263013, issues/263015, issues/263017, issues/263018, issues/263019, issues/263022, issues/263023, issues/263024, issues/263025, issues/263027, issues/263028, issues/263035, issues/263036, issues/263037, issues/263039, issues/263040, issues/263041, issues/263042, issues/263043, issues/263044, issues/263045, issues/263046, issues/263047, issues/263048, issues/263056, issues/263057, issues/263060, issues/263061, issues/263062, issues/263063, issues/263064, issues/263065, issues/263067, issues/263068, issues/263069, issues/263072, issues/263075, issues/263076, issues/263078, issues/263081, issues/263082, issues/263083, issues/263088, issues/263089, issues/263091, issues/263092, issues/263096, issues/263098, issues/263099, issues/263100, issues/263101, issues/263103, issues/263105, issues/263106, issues/263107, issues/263108
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: 678
Summarized Issues:
- Copilot Extension Failures and Performance Issues: Numerous reports describe the GitHub Copilot extension in VS Code failing to function properly, including being unresponsive, freezing, crashing, or producing incorrect or no code suggestions. Users experience issues such as failure to apply code changes, slow or no responses, quota and subscription recognition errors, and extension hangs across various OS and VS Code versions, severely impacting development workflows.
- issues/257799, issues/258705, issues/258707, issues/258746, issues/258927, issues/258945, issues/258948, issues/258987, issues/259015, issues/259119, issues/259291, issues/259293, issues/259403, issues/259530, issues/259675, issues/259931, issues/260242, issues/260289, issues/260516, issues/260528, issues/261264, issues/261307, issues/261309, issues/261329, issues/261332, issues/261353, issues/261790, issues/261791, issues/261894, issues/261903, issues/262299, issues/262426, issues/262427, issues/262428, issues/262448, issues/262528, issues/262533, issues/262536, issues/262556, issues/262557, issues/262864, issues/262867, issues/262891, issues/263029, issues/263030, issues/263031, issues/263032, issues/263033, issues/263034, issues/263058, issues/263070, issues/263071, issues/263073, issues/263074, issues/263104
- Chat and Agent Mode UI/UX and Functionality Problems: Multiple issues report problems with the chat sessions view, chat share icons, chat session renaming, chat session title updates, and confusing or missing UI elements such as pause buttons, tooltips, and context menus. Users also face problems with chat freezing, inability to close embedded chat, and chat sessions unexpectedly clearing or not loading properly, which degrade the user experience and workflow continuity.
- issues/258536, issues/258562, issues/258575, issues/258920, issues/258919, issues/259285, issues/259344, issues/259353, issues/259966, issues/260122, issues/260221, issues/260227, issues/260435, issues/261168, issues/261426, issues/261884, issues/262133, issues/262494, issues/262502, issues/262561, issues/262645, issues/262713, issues/262715, issues/262818, issues/262819
- Subscription, Quota, and Billing Confusion: Several users report issues with subscription recognition, quota limits, and billing messages, including receiving prompts to upgrade despite having active Pro subscriptions, premature quota exhaustion, and incorrect quota reset dates. These problems cause users to lose access to features or be incorrectly charged, leading to frustration and workflow disruption.
- Network and API Request Failures: Many issues describe network-related errors such as net::ERR_NETWORK_CHANGED, net::ERR_CONNECTION_CLOSED, 400 Bad Request errors, 408 Request Timeout, 413 Request Entity Too Large, and server error 500 responses. These errors cause requests to fail, extensions to become unresponsive, or features to stop working, often linked to firewall, proxy, or API key problems.
- issues/257851, issues/258792, issues/259266, issues/260834, issues/260965, issues/261155, issues/261191, issues/261197, issues/261244, issues/261426, issues/261689, issues/261690, issues/262106, issues/262176, issues/262189, issues/262190, issues/262209, issues/262211, issues/262244, issues/262553, issues/262566, issues/262581, issues/262582, issues/262697, issues/262710, issues/262917, issues/263055
- Terminal and Command Execution Issues: Users report problems with terminal input freezing, commands hanging or not running, terminal tool auto-approve failures, and commands being executed repeatedly or incorrectly. Some issues involve the integrated terminal crashing or not accepting input, and others describe Copilot or agent mode failing to run or properly handle terminal commands.
- Model and Tool Selection, Configuration, and Recognition Problems: Several issues describe problems with model selection menus missing or not showing expected models, tools not being recognized or applied correctly, API keys not being saved or forgotten, and tool usage limits causing request failures. These issues affect the ability to select or use AI models and tools properly within the extension.
- Performance and Responsiveness Problems in VS Code: Users report slow responsiveness, freezing, high CPU or memory usage, and crashes in VS Code itself, sometimes linked to extensions like Copilot or Gemini. These issues include slow loading, lag during editing, and system resource exhaustion causing instability.
- Code Editing and Formatting Bugs: Several issues describe problems with code duplication, incorrect indentation, deletion of code or functions without permission, hallucinated or broken code suggestions, and formatting errors that disrupt the coding experience. These bugs cause loss of code, improper code structure, and user frustration.
- Subscription and Trial Activation Issues: Users report problems with starting or accessing free trials, being charged immediately without trial periods, and inability to enable paid licenses after trial completion or organizational license assignment, causing confusion and dissatisfaction.
- Workspace, File Explorer, and Git Integration Issues: Problems include worktree status bar items not updating after deletion, explorer not revealing active files, symbolic link icons not refreshing, source control view not refreshing on branch change, and git push or commit failures. These issues hinder effective project navigation and version control workflows.
- issues/258582, issues/259786, issues/260956, issues/261392, issues/262514, [issues/262541](https://github.com/issues/262541], issues/262663, issues/262830
- Accessibility and Keyboard Navigation Concerns: Some issues highlight lack of keyboard focus support, inaccessible confirmation dialogs, and problems with screen reader announcements, which reduce usability for users relying on assistive technologies.
- Model and API Key Authentication Problems: Users report API keys not being saved or forgotten after some time, invalid authorization headers, and authentication errors causing request failures, which prevent proper use of AI models and features.
- Feature Requests and Usability Enhancements: Requests include adding chat session renaming, context menu actions, side-by-side diff views, persistent code folding, Mermaid diagram support, drag-and-drop folder ordering, and improved workspace trust inheritance, aiming to improve user experience and workflow efficiency.
- Miscellaneous UI and Rendering Bugs: Issues include poor text contrast in Markdown preview, broken hover tooltips, broken borders around warnings, and problems with inline suggestions or ghost text, which affect visual clarity and interaction quality.
- Extension Installation and Signature Verification Failures: Some users report extensions failing signature verification or being unable to install or activate due to missing modules or incompatible API proposals, preventing proper extension usage.
- Code Loss and Data Corruption Reports: Several users report unexpected deletion or loss of code, files appearing empty, or files reverting to older versions, causing significant disruption and data loss.
- Model-Specific Bugs and Behavior: Issues specific to models like Gemini, Claude Sonnet 4, GPT-5, and GPT-5 mini include failures to respond, incorrect usage of premium requests, freezing, and unexpected behavior during code generation or chat interactions.
- Workspace and Session Management Issues: Problems include new chat creation not resetting conversations, session restoration issues, and unexpected session clearing or loss of chat history, which disrupt continuity and user workflow.
- Security and Privacy Concerns: Some issues mention risks related to terminal auto-approve features, prompt injection, and the need for sandboxed command execution to improve security in terminal workflows.
- Miscellaneous Bugs and Requests: Various other issues include problems with keyboard shortcuts, file saving behavior, extension telemetry, and requests for new features or clarifications on existing functionality.
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.
-
this is completely unacceptable, this is a complete waste of time, and this need to be fixed
- Toxicity Score: 0.55 (Moderate possibility, frustration expressed, apology given, accountability demanded, escalating tension)
- This GitHub conversation involves a user expressing strong dissatisfaction and distrust towards the product and its development team, accusing them of deceptive practices. Another participant acknowledges the frustration, apologizes sincerely, and commits to addressing the issues transparently and effectively. A third user attempts to clarify the situation by suggesting the problem may be related to model quality rather than a direct bug, which triggers further frustration from the original user who demands accountability and responsibility. The tone shifts from accusatory and frustrated to apologetic and explanatory, with tension primarily arising from perceived dishonesty and unmet expectations.
-
Unacceptable - last straw using Claude Sonnet 4
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, confrontational tone)
- This GitHub conversation involves a user expressing strong frustration and anger towards another's approach, using aggressive and profane language to criticize perceived laziness in programming. The tone is highly confrontational and dismissive, with no subsequent comments to moderate or de-escalate the tension. This GitHub conversation
-
Support creating a new chat session/editor for Coding Agent
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation features a single comment from an anonymous user expressing frustration and suspicion in a disjointed and accusatory manner, which introduces a negative tone without any constructive engagement or response from others.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, strong negative sentiment)
- This GitHub conversation features a single user expressing strong frustration and dissatisfaction with a software tool, using highly negative and aggressive language to describe their experience. The tone is hostile and emotionally charged, with no responses or attempts at resolution present. The lack of engagement from others leaves the conversation one-sided and potentially volatile if further comments are added.
-
Retard keep creating new script not using editing existed script
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms)
- This GitHub conversation features a single user expressing strong frustration and using offensive language directed at others for not following instructions, with a tone that is confrontational and disrespectful; no other participants or responses are present to moderate or escalate the discussion.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, sarcasm)
- This GitHub conversation involves two anonymous users expressing strong dissatisfaction and frustration regarding the issue, using sarcastic and dismissive tones. The initial comment conveys disbelief and irritation, while the follow-up comment escalates the negativity by accusing an automated system of unfairly closing issues, implying a lack of responsiveness or fairness. The tension is triggered by perceived inadequate handling of the problem and the frustration with the system's response.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, emotional outburst)
- This GitHub conversation features a single user expressing strong frustration and disappointment towards the system and its developers, using harsh and emotionally charged language. The tone is highly negative and accusatory, with the user venting about perceived incompetence and inefficacy. There are no other participants or responses to moderate or escalate the discussion.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, profanity)
- This GitHub conversation consists of a single initial comment by a user expressing strong frustration and dissatisfaction with another contributor's work, using aggressive and profane language. There are no responses or further interactions recorded, so the tone remains one-sided and highly negative without any attempts at resolution or clarification.
-
- Toxicity Score: 0.75 (Explicit language, hostile tone, lack of constructive dialogue)
- This GitHub conversation consists solely of an initial issue title containing explicit language, with no further comments or interactions, indicating a potentially hostile or frustrated tone from the outset.
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: 51
Key Open Pull Requests
1. Using an inline decorations computer: This pull request introduces the use of an inline decorations computer to enhance rendering by managing font size, line height, and positioning of inline elements such as sticky scroll and ghost text within the editor, along with various refinements and bug fixes related to decoration rendering and accessibility.
- URL: pull/262717
- Merged: No
- Associated Commits: c54ab, a9806, 8a712, f4e5a, 8afcd, 6c110, 5ee48, 38dfb, d0685, f7ba2, f7d47, cf367, e3296, 91d4b, f7837, 25492, aaaad, 6395e, 549e9, 95f77, ce134, 9dec3, 952f8, 9f7b3, c6d8a, 6ab9c, 20d17, 54e89, e75e7, c7ce4, 13e7c, 5adde, 4ee17, b4b62, 4888a, 61dba, aae1f, 35b21, 295a5, 1e596, cdf87, 6ead1, 3414d, f06a2, 1e5a7, 1d64c, ed5fb, 5b066, b5991, 39256, b0b28, 9f5d1, 6f38e, 62d90, 9f044, 131cc, d1aec, ad4af, 71e1d, 1a44a, c5190, 904ec, 8a14e, 6a1d6, f2d01, 85989, 4ee90, 2b715, d37de, fc878, ba40a, 52056, dd305, 14a0f, 47d97, 891d4, 563ab, 3e914, b7c77, a72a0, 9c2ab, c2787, 52013, 97773, aebb4, 258e9, e66ae, 46c53, ea282, 50ec1, 244f8, 08511, 810ad, 33c3d, 2e751, fd68a, 6409b, 9764d, e7ee6, 30467, 5fbfa, fcd36, 65075, fb640, 0b24c, e59e8, 8c2e0, 6cbc9, 11754, 82e9b, 8a009, 4b2d3, 2b0bc, cf006, 5c662, d5443, 4425c, d6bfa, 07652, 2c677, 7f00f, ab923, 7e79a, d836d, 7a564, aa406, 686d4, 00a97, 7852d, 80f8f, 30609, 69048, 375f3, d188c, 02df0, 85934, 16156, 9ec92, 1840c, 0e1b5, 2ce71, 77403, 77c8c, f1996, 1e0e1, 75831, f4b05, 70e1d, 1d5fa, 19a81, 126c1, 74622, 71d8d, 5e3ed, 17b19, 71b44, b5ab2, ad495, 0b616, b257a, 39181, c59b9, d48a2, edd97, 944bc, ae06c, 17c0a, a2d6c, f73db, 5f6ad, 5ad6e, eda00, fc7d7, 13210, 486be, e16b5, 327dc, b9cc8, 9d58a, ff1f0, 148c8, 299b1, a41b8, 0acbd, cb5a2, 64dc6, 62c71, 602b6, 26006, 58df4, 87bfa, 236cf, 6fd96, 1e424, 6e2bf, ba098, ef376, de396, b12e2, 7e68f, 2906d, cbb6a, c1f60, f9952, d9db8, dd8ac, da4c3, befd4, 02a00, 0485a, 88a85, c7eeb, 8b386, 30a25, 48718, c0b14, 89e82, e7f3b, e309b, cd129, c59a5, 2991e, d186c, c4ecb, 6d3ac, ddb24, 7f3ff, e6e12, f2268, f9c90, f3133, a7438, 3c9bc, 39bf8, 07032, f2e07, 9787b, 2d76e, 8a71e, 1dffd, 4ecd6, 256c9, 170b8, 402b3, 85a4c, fd2c4, c67eb, f9f9b, b2e60, f5279
2. rewrite polling function: This pull request aims to rewrite the polling function in the project, including multiple commits that address fixing issues, adding conditions, improving tests, and merging updates from the main branch, while still requiring completion and thorough testing of all code paths.
- URL: pull/262947
- Merged: No
- Associated Commits: 60c49, 785b0, 76dc9, 12750, 8359f, 8b8c4, 01ad5, fd8bc, 47ca9, b8dcf, 649c1, eba5e, ffe1b, ab2ff, df5fe
3. Empty state chat history: This pull request introduces a new feature that adds chat history to the empty state view under the setting chat.emptyState.history.enabled, along with various UI improvements and fixes, addressing issue #251187 in the VSCode repository.
- URL: pull/262430
- Merged: No
Other Open Pull Requests
- Copilot Chat Session Enhancements: Multiple pull requests improve the Copilot chat experience by adding real-time monitoring of running sessions and progress tracking for local chat sessions within the Copilot status dashboard. These changes unify Copilot-related information in a streamlined UI and provide consistent visual feedback on active chats.
pull/262221, pull/262985, pull/262869
- Git Worktree and Branch Management Fixes: Several pull requests address issues related to Git worktrees and branch handling, including fixing detached head problems by creating tracking branches, improving error handling when worktrees are in use, and modifying checkout actions to offer branch creation or cancellation options. These fixes enhance user experience and resolve specific Git workflow issues.
pull/262400, pull/262414, pull/262656
- Terminal and Scroll Behavior Fixes: Pull requests target terminal usability by fixing sticky scroll flash issues in pagers through debounce logic and improving scroll speed consistency between the editor and SCM commit diff views by applying user scroll sensitivity settings. These changes improve visual stability and user interaction smoothness.
pull/262436, pull/262348, [pull/262669](https://github.com/pull/262669]
- Configuration and Policy Management Improvements: Updates include adding a
--dump-configurationflag to export full configuration states as JSON for debugging and migration, and implementing a native JSON-based policy management system for Linux that complies with the XDG Base Directory specification. These enhancements provide better configuration transparency and cross-platform policy support.
pull/262173, pull/262708
- Git Path and Completion Fixes: Fixes address issues with Git branch name normalization on Windows by adding a new
Branchcompletion item kind and correcting path handling for branches containing slashes. Additionally, thegit.ignoredRepositoriessetting is improved to correctly ignore repositories with trailing slashes or backslashes by normalizing paths.
pull/262316, pull/262712
- Build Process and Tooling Enhancements: Pull requests improve the build process by refining validation instructions, enhancing Visual Studio detection with clearer error messages for custom install paths, and cleaning up the tool picker feature by adding tools within toolSets and remembering enablement states. These changes streamline development workflows and tooling usability.
pull/262638, pull/262879, [pull/262999](https://github.com/pull/262999]
- Task and Command Path Handling Fixes: A pull request fixes the handling of absolute paths in the
"command"field for tasks of type"process"by ensuring absolute paths are respected before executable lookup, preventing invalid command path concatenations. This improves task execution reliability.
pull/262547
- Miscellaneous Fixes and Features: Other updates include fixing the
removeReferenceItemhotkey functionality by iterating over current selections, adding a new configuration optionmaximumItemLengthfor editor inlay hints to truncate long hints, and improving selection behavior and line break computation in code undo operations. These contribute to overall usability and feature polish.
pull/263004, pull/262740, pull/262648
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: 250
Key Closed Pull Requests
1. Update LICENSE.2015txt: This pull request is about updating the LICENSE.2015txt file, although it was not merged and contains a variety of unrelated commits including features and fixes such as support for custom JavaScript switch-case indentation and improvements to inline decorations.
- URL: pull/262162
- Merged: No
- Associated Commits: a91e6, 97a5f, 00d77, c9209, 2e0fc, 8ac26, 5bd3d, 4020d, 2a919, c594d, 31090, 3bc3c, 8d983, d8ea0, ef520, 9ee03, 814ea, bb430, 2bef1, 06b58, dfda5, 924d7, 4cdae, 9b74f, 6306b, 9559a, 92c30, 29fa0, 37066, fc10c, 4ccc2, 2174d, 35b2d, c2a5c, ac721, a4262, 8eddf, 115ba, f6b52, fcac4, e739a, 97bd3, 1db10, fce85, d7201, 71ac7, 5ba45, 588ec, 96e03, 57e8c, aee2a, 36a79, e8d35, 7fada, 3699b, 1b5b9, 94a4a, 6d87d, bfe7f, 06e23, 37a00, f5e4c, e3803, a969b, e3cf0, 722cd, ab1b9, aebff, b785c, c799d, 31188, da45c, adb7b, a68e5, a2eb5, 47cff, eaba9, 4d446, 118e6, 7610c, 3ce75, df4ff, 52348, a5d83, c8d16, 8961f, 27544, 566a4, d707b, 7caed, 48370, e1d37, abecf, ebf1b, cc263, 09d6f, 846e7, 87a0d, ab8fe, a74aa, 273f6, 434fe, 833bb, b7ffd, 0e71d, 5e399, 2f00c, 30858, b17f0, c2ee9, 71b1e, a0af0, d4f17, d7f1a, d2172, a4373, 3545d, 8e462, 25575, 9380c, 55a95, 15be9, ed965, 97ff3, e4795, 862fa, 8159b, 65792, 748e3, a27b3, e2207, 738b9, 34e23, e5673, bb655, f1b4b, 60230, a821b, 87ed9, 81215, cff1a, ff593, a4fb8, 8a3a6, c2c7a, bc042, 57e48, 0866a, 2a5b5, 9ce97, d427c, 0d57c, f672e, 4c84c, 909c1, 1600f, 58145, d6482, fe187, 0bccf, 3d0ae, 4b4cd, 7667c, f6ec9, f034b, 203a5, 4ef04, 61760, 19365, 45a25, 09e49, ec806, 79c86, 7344e, 7def6, e8cfe, e0b0b, 9b46b, 0e5c3, 0000f, 4a018, 60fe8, e55ac, 11b2f, e5165, 2a00f, fa68c, 31122, 3f5e7, dac52, ae56e, 57e5f, 73564, 05e66, d9069, 98f16, 959d0, ac972, 830e5, 8cfb2, 28f5c, 3a459, a0ecf, 38677, d24b8, 15006, 4f81a, 9cf80, f2e5a, 10e86, 943ef, 0111f, 39d64, 56ad0, ae715, 48842, 1c8f3, f2bfc, 20839, 5a6c2, 0ac5c, ac0f5, 9542c, d239b, b7186, 6e3d4, 88436, 207c5, 0cba8, 9a937
2. auto-reply to terminal confirmations: This pull request proposes an implementation for automatically replying to terminal confirmation prompts, addresses issue #258252, and includes cleanup of the buffer output polling code, although it has not yet been merged and still requires tests.
- URL: pull/261713
- Merged: No
- Associated Commits: b8bd9, edf6e, fb61d, 62888, f817c, f99e0, 49eb1, 19e4f, 8a2b2, c2735, 55a12, e29d7, 010a1, 047d3, ae8f8, a9296, 7c6e0, 49ec1, 850c5, efa59
3. Wait for agent loop to finish in automation: This pull request introduces a mechanism for automation to wait until the chat loop reaches a terminal state by adding a blockOnResponse flag to workbench.action.chat.open and enhances error handling by adding a code field to IChatResponseErrorDetails to precisely identify errors encountered during the chat process.
- URL: pull/262370
- Merged: 2025-08-20T17:13:48Z
- Associated Commits: 7ec1a, b1425, 382ec, 44dc3, c3e52, bb7f6, e9a6a, d8d16, 4840e, fc5a7, bf4c9, deeb9, a9baa, c9ad9, 0f62e, a5a95, 14590, a419d, 7b1d7, d91b2
Other Closed Pull Requests
- Chat feature settings and enhancements: Multiple pull requests focus on improving the chat feature by adjusting settings related to hiding or disabling options, supporting extension functionality, and refining behavior for better alignment. These changes also include making the secondary sidebar visible by default and enabling programmatic model switching for automation scenarios.
[pull/262482, pull/261998, pull/262420, pull/262420]
- Chat history and UI improvements: A hierarchical tree view replaces the previous flat list for chat history, enabling collapsible nodes and better integration with VS Code’s tree view patterns. Additional improvements include revising the AI actions submenu and renaming chat context menu options for clarity and usability.
[pull/262214, pull/262902, pull/261547, pull/262902]
- Telemetry enhancements: Several pull requests add detailed telemetry fields to track user interactions with AI suggestions, chat mode changes, and terminal commands, while removing deprecated fields and replacing configurable command reporting with a hardcoded allow list for privacy and maintainability.
[pull/262930, pull/261705, pull/262311, pull/261705]
- Terminal and task monitoring improvements: Updates include integrating bufferOutputPolling into terminal output monitoring, adding an opt-in terminal auto approve feature, improving task problem monitoring with telemetry and auto reply, and introducing a TaskProblemMonitor class for real-time error tracking.
[pull/262585, pull/262501, pull/261867, pull/262796]
- "Thinking" functionality and serialization: Pull requests consolidate and clean up the "thinking" feature code, move related filters and logic to the chat model, and fix serialization issues to improve maintainability and correctness.
[pull/262802, pull/262239]
- Window sizing and UI behavior fixes: A workspace-aware default window sizing feature is introduced to set larger default dimensions for workspace windows, while fixes address terminal sticky scroll keyboard focus trapping and improve modal/dialog automation support.
[pull/262266, pull/262785, pull/262785]
- Code quality and metadata updates: Enhancements include adding metadata to inlineChat.applyEdits, cleaning up code related to "thinking" functionality, and updating the suggest detail feature to use the label service for URI formatting.
[pull/262366, pull/262802, pull/262027]
- File operation detection in terminal commands: A non-intrusive system is implemented to detect file operations within terminal commands using regex heuristics, integrating with the chat editing service to track and report file changes without disrupting normal terminal usage.
[pull/260660]
- KaTeX extension regex fix: The KaTeX extension regex is fixed to prevent misinterpretation of PowerShell variables and similar code snippets as math expressions, improving markdown rendering accuracy.
[pull/261467]
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 |
|---|---|---|---|---|
| Tyriar | 296 | 36 | 163 | 249 |
| Copilot | 455 | 61 | 0 | 34 |
| meganrogge | 169 | 14 | 26 | 123 |
| bpasero | 123 | 29 | 56 | 123 |
| TylerLeonhardt | 80 | 16 | 31 | 143 |
| mjbvz | 118 | 27 | 34 | 67 |
| roblourens | 43 | 6 | 42 | 154 |
| connor4312 | 45 | 8 | 22 | 155 |
| justschen | 79 | 16 | 9 | 87 |
| lramos15 | 29 | 3 | 13 | 108 |
Don't miss what's next. Subscribe to Weekly Project News: