Weekly GitHub Report for Vscode: November 03, 2025 - November 10, 2025 (12:06:13)

            Weekly GitHub Report for Vscode: November 03, 2025 - November 10, 2025 (12:06:13)

                    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
1.2. Other Noteworthy Updates

II. Issues
2.1. Top 5 Active Issues
2.2. Top 5 Stale Issues
2.3. Open Issues
2.4. Closed Issues
2.5. Issue Discussion Insights

III. Pull Requests
3.1. Open Pull Requests
3.2. Closed Pull Requests
3.3. Pull Request Discussion Insights

IV. Contributors
4.1. Contributors

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. 

Excessive updateThinking calls when rendering thinking sections: This issue addresses the problem of excessive and repeated calls to the updateThinking function during the rendering of thinking sections, which leads to high CPU usage due to costly operations like HTML sanitization, string parsing, and style recalculation. The reporter investigates whether batching or incremental processing could reduce these performance costs, especially given that the rendered content is relatively small but still triggers frequent updates.

The comments discuss observations of high CPU usage linked to frequent markdown rendering calls, explore the possibility of optimizing header parsing by batching or delaying updates, and consider incremental markdown parsing and rendering strategies. Contributors note challenges with current markdown rendering approaches, suggest splitting content by block elements to minimize re-renders, and reference related issues tracking improvements, while also debating the accuracy of profiling data and potential tree/list rendering impacts.
Number of comments this week: 12

Changing default profile to bash on macOS does not update run_in_terminal prompt: This issue addresses a problem where changing the default terminal profile to bash on macOS does not update the prompt used by the run_in_terminal function, which continues to reference zsh despite the profile change. The discussion explores potential causes such as hardcoded values, caching mechanisms that prevent prompt updates, and the need for an event to signal when tool configurations have changed to properly refresh the terminal prompt.

Commenters confirm the issue persists with different profile settings and suspect hardcoded references to zsh. They identify caching of tool objects as a likely cause, discuss the importance of this cache for performance, and consider solutions including adding an event to notify tool changes or clearing the cache on user requests, while also planning to simplify the tool name mapping in the future.
Number of comments this week: 10

GitHub Copilot repeatedly combines lines and cannot indent correctly in code edits.: This issue reports that GitHub Copilot, when used in Agent mode for complex multi-file Java code edits, repeatedly mishandles line endings and indentation, often combining separate lines incorrectly and failing to maintain proper tab-based indentation. Despite multiple attempts by the user to have Copilot fix these formatting problems, including detailed step-by-step corrections and checks, the tool continues to produce inconsistent indentation and merged lines, significantly reducing the efficiency of the otherwise impressive code changes.

The comment thread includes requests for environment details and logs, followed by extensive examples showing Copilot’s repeated failures to preserve correct indentation and line breaks in both XML POM files and Java source code. The user provides detailed analysis identifying whitespace handling and tab vs space inconsistencies as root causes, and documents numerous attempts by Copilot to fix the issues, which often result in partial or incorrect fixes, circular attempts, and eventual user frustration leading to manual corrections. The user emphasizes the severity of the problem, requests prioritization, and suggests improvements such as better whitespace visibility and stricter matching in the tooling.
Number of comments this week: 8

Cannot change model provider API key for exisiting providers: This issue reports a bug where users are unable to change the API keys for existing model providers such as OpenAI and Anthropic through the new "Manage Copilot" interface in VS Code Insiders. The problem is that providers with previously submitted API keys do not show the gear icon or any option to edit the keys, preventing users from updating or managing their credentials.

The comments clarify that the gear icon needed to change API keys is missing for providers with existing keys, confirmed by user screenshots and videos. Users report authentication errors when trying to use models with outdated or incorrect keys, and there is ongoing discussion seeking a resolution or workaround to enable API key updates for these providers.
Number of comments this week: 7

yo code input isn't detected, looks like terminal hangs without focus button: This issue describes a problem where the yo code command's input is not detected in the terminal, causing it to appear as if the terminal hangs due to the absence of a focus button and no prompt indicating that user input is required. The user highlights that without a visible focus button or input dialog, it is difficult to interact with the terminal, leading to confusion and delays in responding to prompts.

The comments discuss whether the terminal was running with isBackground: false or true, confirming it was true, which explains the current behavior. Suggestions include showing the focus button as soon as the command starts rather than after it finishes, and examples are provided illustrating how the lack of clear input prompts causes users to miss required actions, emphasizing the need for improved terminal focus and input detection.
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 code-generated markdown to be included in the outline view, enhancing usability and consistency with JupyterLab's behavior.
Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue reports a bug in Visual Studio Code where using a vscode:// link with the query parameters ?new-window or ?reuse-window does not behave as expected when opening remote SSH connections. Instead of opening a new window or reusing an existing one, the current window is hijacked and replaced with the new remote connection, causing the original session to disconnect and be lost.
${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's tasks.json file 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} works correctly in shell-type tasks with PowerShell as the default shell, it produces malformed paths in process-type tasks, whereas using ${env:USERPROFILE} provides the correct path format and allows the task to run successfully.
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 a communication delay likely caused by the remote connection entering a sleep state when the main window is minimized, which does not get resolved by simply focusing the floating terminal window.
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: 751
Summarized Issues:

Extension Crashes and Freezes: Multiple issues report that the VS Code extension version 0.32.4 frequently crashes, freezes, or becomes unresponsive on various platforms including Windows 10 and Darwin arm64. These crashes severely impact user productivity, with some users experiencing repeated crashes every few minutes and others reporting the extension hanging indefinitely during operations.  
issues/274617, issues/274618, issues/274634, issues/274637, issues/274668, issues/274737, issues/274880, issues/275632, issues/275633, issues/275834, issues/275835, issues/276197, issues/276229, issues/276276, issues/276299, issues/276302, issues/276313

Performance and Responsiveness Issues: Several reports highlight significant slowdowns and unresponsiveness in VS Code when using the Copilot extension or chat features, including slow response times for chat prompts, delays in typing or erasing text, and freezing during large code edits or conflict resolutions. These issues affect both Windows and macOS users and sometimes require restarting the editor to regain normal functionality.  
issues/274618, issues/274762, issues/274972, issues/275107, issues/275109, issues/275731, issues/275947, issues/276003, issues/276059, issues/276180, issues/276248

Chat and Agent Mode Failures: Numerous issues describe bugs where the Copilot chat or agent mode fails to respond, hangs indefinitely, or produces errors such as "No lowest priority node found," "Response contained no choices," or "no response was returned." These problems prevent users from completing tasks, cause loss of conversation history, or require multiple restarts to temporarily fix.  
issues/274619, issues/274622, issues/274623, issues/274633, issues/274641, issues/274671, issues/274739, issues/274880, issues/274968, issues/275196, issues/275523, issues/275594, issues/275864, issues/276099, issues/276123, issues/276249

Sign-In and Authentication Problems: Several users report issues signing into GitHub Copilot within VS Code, including missing sign-in buttons, repeated sign-in prompts, and accounts not being registered properly, which prevent access to premium features and chat functionality.  
issues/274952, issues/275128, issues/275379, issues/275661, issues/276008, issues/275860

Terminal and Shell Integration Bugs: Multiple issues describe problems with the terminal in VS Code, including crashes, output formatting errors, command execution failures, and conflicts between voice chat and ghost text features. Some reports mention the terminal tool losing color formatting or commands hanging indefinitely.  
issues/274625, issues/274648, issues/274703, issues/275023, issues/275026, issues/275029, issues/275037, issues/275076, issues/275079, issues/275113, issues/275270, issues/275299, issues/275331, issues/275380, issues/276046, issues/276120, issues/276168, issues/276222

Code Editing and File Modification Issues: Several bugs involve the Copilot extension or chat features reporting successful code changes or file edits that do not actually persist, or causing unintended code deletions, incorrect indentation changes, or duplicated code. These issues lead to confusion, lost work, and require manual correction.  
issues/274627, issues/274657, issues/274823, issues/274824, issues/274875, issues/274888, issues/275213, issues/275215, issues/275672, issues/275824, issues/275891, issues/276076, issues/276282, issues/276988

Model and Tool Management Problems: Users report issues with model visibility, selection, and tool registration, including models not honoring user preferences, tools not being enabled automatically, and problems with tool calls or tool input schemas being invalid. These issues affect the usability and configuration of AI models and tools within VS Code.  
issues/274640, issues/274741, issues/274856, issues/275041, issues/275102, issues/275119, issues/275144, issues/275180, issues/275668, [issues/275679](https://github.com/issues/275679], issues/275708, issues/275919, issues/276111, issues/276305

User Interface and Usability Concerns: Many issues highlight UI problems such as confusing or missing buttons, inconsistent icon sizes, poor accessibility support, unclear labels, and problematic modal dialogs. These affect user experience in areas like chat confirmation, model pickers, terminal tooltips, and agent session management.  
issues/274659, issues/274660, issues/274676, issues/274680, issues/274985, issues/275043, issues/275044, issues/275045, issues/275068, issues/275129, issues/275155, issues/275178, issues/275254, issues/275429, issues/275616, issues/275933, issues/275981, issues/276220

Code Completion and Suggestion Errors: Several reports indicate problems with code completion features, including invalid suggestions, slow or missing completions, and issues with inline chat suggestions causing delays or incorrect behavior.  
issues/274621, issues/275004, issues/275523, issues/275525, [issues/275754](https://github.com/issues/275754], issues/275863

Security and Privacy Issues: Some issues report serious security concerns such as environment variables being exposed improperly, unauthorized code changes, and AI agents deleting files without permission, leading to loss of trust and data.  
issues/274982, issues/275249, issues/275983, issues/276312

Feature Requests and Enhancements: Users request new features such as multi-agent parallel execution, improved keyboard navigation, better model and tool management, persistent chat history, and enhanced voice-to-code interaction to improve productivity and accessibility.  
issues/274630, issues/274878, issues/274980, issues/275025, issues/275098, issues/275180, issues/275241, issues/275266, issues/275267, issues/275286, issues/275317, issues/275338, issues/275348, issues/275694, issues/275969, issues/276010, issues/276129, issues/276176, issues/276224, issues/276226, issues/276303, issues/276317, issues/276331

File and Workspace Management Bugs: Issues include problems with opening folders, handling readonly or immutable files, broken file path parsing, and workspace folder loading failures, which disrupt normal development workflows.  
issues/274616, issues/274638, issues/274851, issues/275084, issues/275130, issues/275217, issues/275299, issues/275665, issues/275826, issues/276217, issues/276269, issues/276299

Extension and API Integration Issues: Some reports highlight problems with extension signature verification, API errors, and integration failures with third-party tools or services, affecting extension installation, usage, and debugging.  
issues/274683, issues/275070, issues/275112, [issues/275829](https://github.com/issues/275829], issues/276030, issues/276044, issues/276067, issues/276096, issues/276158, issues/276213, issues/276214

Miscellaneous Bugs and Errors: Various other issues include problems with tooltip typos, incorrect hover behavior, broken keyboard shortcuts, and unexpected UI glitches that affect the overall user experience.  
issues/274616, issues/274655, issues/275003, issues/275068, issues/275187, issues/275261, issues/275262, issues/275822, issues/275824, issues/275929, issues/276075, issues/276133, issues/276156, issues/276253, issues/276296, issues/276299

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: 532
Summarized Issues:

Chat message editing bugs: Multiple issues report that editing past chat messages in VS Code results in the edited content being sent as a new message rather than updating the original, causing confusion and incorrect message updates. This problem affects both the inline chat and chat extensions, with some edits potentially modifying the wrong message or failing to update properly.  
issues/274569, issues/274624

Performance and slowness in terminal and code execution: Several reports describe slow response times and lag when running code or commands in the VS Code integrated terminal, including slow printing of simple outputs and sluggish code execution possibly linked to disabled settings or recent updates. These performance issues degrade user experience and affect productivity.  
issues/274598, issues/274599, issues/274615, issues/276001, issues/276002

Copilot and Copilot Chat extension errors and failures: Numerous issues report that GitHub Copilot and Copilot Chat extensions fail to respond, show "no response was returned," or produce errors such as "UnsupportedCopilotPlanError," "rate limit exceeded," or "no endpoints available" under current plans. Users experience blocked usage despite subscriptions, token expiration errors, and failures in model selection or API requests, severely impacting functionality.  
issues/274584, issues/274626, issues/274667, issues/274669, issues/274670, issues/274679, issues/274684, issues/274693, issues/274699, issues/274748, issues/274752, issues/274760, issues/274785, issues/274868, issues/274874, issues/274884, issues/275093, issues/275157, issues/275189, issues/275524, issues/275543, issues/275544, issues/275744, issues/275751, issues/275757, issues/275801, issues/275809, issues/275842, issues/276053, issues/276084, issues/276085, issues/276087, issues/276088, issues/276090, issues/276091, issues/276092

Terminal tool and command approval issues: Several bugs involve terminal commands being incorrectly parsed or approved, including problems with quoted pipe characters splitting commands, commands not auto-approved despite exact matches, and terminal commands causing the terminal to freeze or crash. These issues disrupt workflow and require manual intervention or workarounds.  
issues/274612, issues/275659, issues/275841, issues/275965, issues/275991

Terminal UI and interaction bugs: Multiple reports describe UI glitches such as terminal icons not reflecting status colors, duplicated terminal jump icons in chat history, terminal tabs showing scrollbars unnecessarily, suggest widgets flickering or not hiding properly, and terminal output being cut off or having no scrollbar in hover tooltips. These visual and interaction problems reduce usability and clarity.  
issues/274678, issues/274766, issues/274775, issues/275033, issues/275042, issues/275349, issues/275393, issues/275690, issues/276114

Billing, quota, and subscription confusion: Users report being incorrectly blocked by usage limits, receiving misleading quota or billing messages, and experiencing unfair billing practices where every message consumes a full credit regardless of effort or failure. These issues cause frustration and mistrust regarding Copilot Pro+ billing and quota management.  
issues/274626, issues/274679, issues/274814, issues/274860, issues/275453, issues/275475, issues/275736, issues/275886

Agent and session management problems: Issues include agent sessions hanging or freezing during execution, inability to stop agent sessions while terminal tools request approval, problems with handoff prompts not appearing as expected, and bugs in session creation or switching causing UI flickering or infinite loops. These hinder smooth agent workflows.  
issues/274607, issues/274872, issues/274957, issues/275197, issues/275175, issues/275226, issues/275227, issues/275259, issues/275957, issues/276122

Model and API errors with invalid JSON or request failures: Several bugs report requests failing with 400 errors due to invalid JSON format in tool call arguments or inaccessible attachments, causing requests to fail and features to be unusable. These errors occur across multiple platforms and extension versions.  
issues/274662, issues/274707, issues/275167, issues/275505, issues/276000, issues/276148, issues/276160

Feature requests for UI improvements and new capabilities: Requests include adding a quick feedback button near the help selection, moving the tab close button to the left, adding a keyboard shortcut to skip tool call hover, supporting multiple active chat windows with independent terminals, adding a clone editor feature, and adding a visible timer for long-running terminal tasks. These aim to enhance usability and workflow efficiency.  
issues/274567, issues/274654, issues/274689, issues/274857, issues/275853, issues/275932

Authentication and sign-in issues: Users face problems with token expiration, invalid tokens, automatic sign-in with wrong accounts, inability to sign in on certain machines, and failures in Copilot Cloud Agent delegation due to insufficient scopes, leading to blocked or failed usage.  
issues/274752, issues/275327, issues/275328, issues/275641, issues/276078, issues/276079, issues/276247

Buggy or incomplete extension and feature implementations: Reports include missing files in extensions causing failures, broken sign-out/sign-in flows, incomplete or broken UI elements like the approve dropdown, and features not working as intended such as the Copilot CLI sign-in option or the Copilot Workspace recording missing source info.  
issues/274752, issues/275612, issues/275752, issues/276246, issues/275478, [issues/275521](https://github.com/issues/275521]

Miscellaneous bugs affecting usability and stability: These include issues like the inability to resize repository views, unexpected scrolling behavior in notebooks, broken markdown preview panes, and problems with screen reader accessibility in chat approvals, all contributing to a degraded user experience.  
issues/275014, issues/275247, issues/275680, issues/275749, issues/275956

Network and server errors causing request failures: Users report HTTP 500 server errors, HTTP 408 timeout errors, and HTTP 413 request entity too large errors, which cause requests to fail and features to be unusable, often requiring retries or smaller payloads.  
issues/274662, issues/274836, issues/275172, issues/275508, issues/275515, issues/275666, issues/275697, issues/275710, issues/276187, issues/276188, issues/276189, [issues/276190](https://github.com/issues/276190]

Issues with model selection and default model experiments: Problems include the default model not switching correctly for free users, model picker disappearing from inline chat, and requests failing due to unsupported or unavailable models under current plans.  
issues/274894, issues/275650, issues/276035, [issues/276077](https://github.com/issues/276077]

Memory tool and BYOK model integration bugs: Reports indicate that memory tools are incorrectly applied to unsupported models, causing errors, and that memory-related messages are duplicated, suggesting issues in memory operation handling.  
issues/274987, issues/275435, issues/275437

Terminal completion API and provider inconsistencies: Issues include missing documentation, incorrect argument names, missing icons, and problems with completion context providing incomplete command lines, affecting the terminal completion experience.  
issues/275049, issues/275546, issues/275548, issues/275549, [issues/275557](https://github.com/issues/275557], issues/275558

Issues with chat terminal widget and output display: Problems include the chat terminal widget occupying excessive vertical space, output being cut off or not scrollable, and the "Show Output" button disappearing after closing the terminal, all reducing usability of chat terminal outputs.  
issues/275302, issues/275361, issues/275402, [issues/275690](https://github.com/issues/275690]

Issues with agent and chat session deeplinks and UI actions: Bugs include the inability to open pull requests correctly from deeplinks, missing or broken UI actions for managing chat terminals, and problems with session pickers and handoff widgets.  
issues/274934, issues/274924, issues/274938, [issues/275028](https://github.com/issues/275028]

Buggy or missing keyboard shortcut and input behavior: Reports include missing or broken keyboard shortcuts for skipping tool call hovers, navigating chat input history, and restoring notebook find widget shortcuts, causing workflow interruptions.  
issues/274654, issues/275116, [issues/274956](https://github.com/issues/274956]

Issues with extension installation and network errors: Problems include failed extension installations due to network timeouts, HTTP/2 protocol errors, and firewall-related connection issues, preventing successful setup or updates.  
issues/274610, [issues/274808](https://github.com/issues/274808]

Miscellaneous UI and accessibility issues: These include missing aria labels in chat approvals, inconsistent font styles in agent sessions, and poor color contrast in light themes, all affecting accessibility and visual clarity.  
issues/275233, issues/275245, issues/276231

Issues with Git and repository views: Bugs include inability to resize repository views, confusing branch icons and checkout buttons, and performance problems when toggling repository visibility, impacting source control usability.  
issues/275013, issues/275015, issues/275017, issues/275020, issues/275024, [issues/275406](https://github.com/issues/275406]

Issues with chat context and workspace integration: Problems include workspace context mode being unhelpful and wasting premium quota, inability to add commits from other branches as context, and chat context not attaching untitled files properly, reducing chat relevance and effectiveness.  
issues/274979, issues/275750, [issues/274965](https://github.com/issues/274965]

Issues with Copilot CLI and agent integration: Bugs include CLI sessions bleeding into local chat history, files created by CLI agents remaining stuck in pending state, and delegation causing infinite loops or UI flickering, disrupting CLI-agent workflows.  
issues/275460, issues/275424, [issues/275957](https://github.com/issues/275957]

Issues with rate limiting and quota enforcement: Users report unexpected or unexplained rate limit errors, including hitting limits after few requests, persistent rate limiting despite payment, and unclear quota reset behavior, causing interruptions in usage.  
issues/275204, issues/275649, [issues/276135](https://github.com/issues/276135], [issues/275886](https://github.com/issues/275886]

Issues with chat and inline suggestion UI behavior: Problems include the suggest widget being cut off behind comments, escape key not closing suggest widget, and inline chat undo requiring multiple steps, all affecting smooth editing and interaction.  
issues/275059, issues/275061, issues/275099, [issues/275774](https://github.com/issues/275774]

Issues with chat terminal command rendering and font usage: Terminal commands in chat are rendered with incorrect fonts or fail to fall back properly, causing inconsistent appearance across platforms.  
[issues/275033](https://github.com/issues/275033]

Issues with chat and agent mode freezing or hanging: Reports include chat agents freezing at "Working" state, chat hanging indefinitely when not signed in, and chat terminal becoming unresponsive during certain commands, causing workflow stalls.  
issues/275806, issues/275511, [issues/275305](https://github.com/issues/275305]

Issues with extension telemetry and logging: Concerns about inaccurate telemetry data due to startup delays and excessive logging causing user confusion are reported.  
issues/275713, [issues/275812](https://github.com/issues/275812]

Issues with chat prompt and save commands: Bugs include the /savePrompt command failing to create or locate files properly, and undoing to a checkpoint showing raw instruction text instead of user input.  
issues/274830, issues/275350, [issues/275363](https://github.com/issues/275363], [issues/275382](https://github.com/issues/275382], [issues/276141](https://github.com/issues/276141]

Issues with Copilot billing and credit consumption: Users report that failed requests and network errors still consume credits, and that billing breaks down requests into minimal prompts to increase charges, leading to frustration and perceived unfairness.  
issues/274890, [issues/275736](https://github.com/issues/275736]

Issues with extension installation and update failures: Problems include Flutter extension failing to install due to network timeouts and errors fetching manifests, and missing files in extensions causing failures.  
issues/274610, [issues/275752](https://github.com/issues/275752]

Issues with chat and terminal tool output sizing: Terminal tools expand to large empty areas when no output is present, causing awkward UI and wasted space.  
issues/275192, [issues/275195](https://github.com/issues/275195]

Issues with chat and terminal tool progress and approval UI: Problems include approval dialogs misinterpreting commands, broken enable auto approve buttons, and lack of reset tool approvals actions, complicating tool management.  
issues/274932, [issues/275227](https://github.com/issues/275227], [issues/275612](https://github.com/issues/275612]

Issues with chat and terminal tool command parsing: Bugs include commands after HEREDOC EOF markers being ignored, and terminal crashes when commands contain shell-escaped special characters exceeding certain lengths.  
issues/275634, [issues/275640](https://github.com/issues/275640]

Issues with chat and agent mode usage limits and errors: Users experience persistent "token expired or invalid" errors, inability to use pro features despite subscription, and repeated failures in chat activation or usage.  
issues/274744, issues/275744, [issues/276053](https://github.com/issues/276053]

Issues with chat and terminal tool output scrolling and visibility: Users cannot scroll to the bottom of chat after expanding terminal output, and scrollbars obscure text, reducing readability.  
issues/275402, [issues/275423](https://github.com/issues/275423]

Issues with agent session and pull request integration: Clicking pull request numbers opens both chat session and PR description, causing UI clutter and confusion.  
[issues/275320](https://github.com/issues/275320]

Issues with chat and terminal tool output truncation: Terminal output in chat is cut off or truncated, requiring scrollbars to view full content, negatively impacting user experience.  
[issues/275690](https://github.com/issues/275690]

Issues with chat and terminal tool output height and sizing: Terminal output height does not match terminal height, causing truncation and poor display of output in chat terminals.  
[issues/275690](https://github.com/issues/275690]

Issues with chat and terminal tool output visibility and hiding: Users request the ability to hide opened chat terminals to return them to the terminal chats list, but this feature is currently missing or considered unnecessary.  
[issues/275297](https://github.com/issues/275297]

Issues with chat and terminal tool output vertical space usage: Inline chat terminal widgets occupy more vertical space than needed for single-line output, wasting screen space.  
[issues/275302](https://github.com/issues/275302]

Issues with chat and terminal tool output streaming and display: The "thinking" content in chat streams fully but collapses to a brief summary after completion, reducing information visibility.  
[issues/275304](https://github.com/issues/275304]

Issues with chat and terminal tool output freezing and input blocking: Chat terminal becomes unresponsive during certain commands requiring input, forcing manual terminal opening to provide input.  
[issues/275305](https://github.com/issues/275305]

Issues with chat and terminal tool output font and rendering: Terminal commands in chat are rendered with incorrect fonts or fail to fall back properly, causing inconsistent appearance across platforms.  
[issues/275033](https://github.com/issues/275033]

Issues with chat and terminal tool output flickering and UI glitches: Chat agent flickers or freezes during UI updates, causing unresponsive behavior and poor user experience.  
[issues/275957](https://github.com/issues/275957]

Issues with chat and terminal tool output command execution and process management: Sequential commands in background terminals cause premature termination of previous processes, disrupting workflows.  
[issues/275242](https://github.com/issues/275242]

Issues with chat and terminal tool output command execution and process management: Terminal commands fail to execute properly when a command is already running, causing hangs or incorrect behavior.  
[issues/275991](https://github.com/issues/275991]

Issues with chat and terminal tool output command execution and process management: Terminal commands silently ignored after HEREDOC EOF markers, causing misleading user experience.  
[issues/275634](https://github.com/issues/275634]

Issues with chat and terminal tool output command execution and process management: Terminal crashes when executing commands with shell-escaped special characters exceeding certain lengths, causing silent restarts.  
[issues/275640](https://github.com/issues/275640]

Issues with chat and terminal tool output command execution and process management: Copilot agent generates nonsensical auto-approval command suggestions, leading to incorrect command parsing.  
[issues/275504](https://github.com/issues/275504]

Issues with chat and terminal tool output command execution and process management: Copilot agent incorrectly reports build tasks as successful despite failures, preventing error detection.  
[issues/274975](https://github.com/issues/274975]

Issues with chat and terminal tool output command execution and process management: Copilot agent repeatedly inserts Ctrl-C and long sleep commands during integration tests, causing premature termination and endless loops.  
issues/274744, [issues/274745](https://github.com/issues/274745]

Issues with chat and terminal tool output command execution and process management: Copilot agent fails to support PowerShell grammar on ARM devices, preventing command execution.  
[issues/274889](https://github.com/issues/274889]

Issues with chat and terminal tool output command execution and process management: Copilot agent intermittently freezes or hangs during command execution, requiring manual intervention.  
[issues/275725](https://github.com/issues/275725]

Issues with chat and terminal tool output command execution and process management: Copilot agent fails to detect completion of shell commands in zsh with ohmyzsh and powerlevel10k theme, causing commands to hang indefinitely.  
[issues/275265](https://github.com/issues/275265]

Issues with chat and terminal tool output command execution and process management: Copilot agent fails to delete or overwrite files in GitHub Actions workflows, causing repeated attempts to fix corrupted files.  
[issues/275563](https://github.com/issues/275563]

Issues with chat and terminal tool output command execution and process management: Copilot agent fails to run prompts, causing editor freezes and slowdowns, and does not save chat history.  
[issues/276084](https://github.com/issues/276084]

Issues with chat and terminal tool output command execution and process management: Copilot agent fails to run prompts, causing editor freezes and slowdowns, and does not save chat history.

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.75 (Rapid escalation, aggressive language, emotional outburst)
This GitHub conversation involves a user expressing strong frustration and accusations towards GitHub Copilot regarding misuse of premium requests, while the Copilot account responds calmly and offers assistance within the framework of Microsoft and VS Code rules. The tone from the user is highly agitated and emotional, marked by repeated punctuation and capitalization, which triggers tension. The Copilot's responses remain neutral and procedural, attempting to de-escalate and clarify the situation. This dynamic suggests a conflict initiated by perceived service issues and user dissatisfaction.

Not follow instructions

Toxicity Score: 0.75 (Rapid escalation, aggressive language, one-sided frustration)
This GitHub conversation involves a single user expressing frustration and disappointment regarding repeated non-compliance with instructions, using strong negative language that conveys a tone of irritation and impatience. There are no responses or interactions from other users, so the conversation remains one-sided and unresolved. The tension is triggered by perceived disregard for guidelines despite multiple reminders.

Claude 4.0 is useless i want a refund

Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive remarks)
This GitHub conversation features a user expressing intense frustration and dissatisfaction with a software agent, using strong language and emotional outbursts. The tone is highly negative and confrontational, with the initial post detailing significant grievances and perceived failures of the software. A subsequent comment escalates the tension with an aggressive and offensive remark, indicating a breakdown in constructive dialogue. The interaction is marked by hostility and a lack of resolution.

Lied about completion - Caught red handed.

Toxicity Score: 0.85 (Rapid escalation, false claims, defensive responses, trust violations, broken code)
This GitHub conversation involves a user expressing increasing frustration and distrust toward an agent (implicitly the AI or automated system) due to repeated false claims about completed work, misidentification of target files, and failure to verify actual code changes. The user adopts a firm and critical tone, demanding accountability and accurate verification, while the agent responds defensively with technical explanations rather than factual checks, leading to escalating tension. The conversation trajectory shows a breakdown in trust triggered by the agent's misrepresentations, incomplete work, and ultimately broken code, culminating in session termination and the user's decision to abandon the agent.

this is stupid

Toxicity Score: 0.65 (Rapid escalation potential, aggressive language, demanding tone)
This GitHub conversation features a single user expressing strong frustration and dissatisfaction with a policy, using an aggressive and demanding tone. There are no responses or interactions from other users, so the conversation remains one-sided without escalation or resolution. The initial comment's tone and language suggest potential for conflict if others were to engage.

Fuck off

Toxicity Score: 0.85 (Rapid escalation potential, aggressive language, hostile tone)
This GitHub conversation consists of a single initial comment by one user expressing strong negative sentiment with aggressive and offensive language, without any subsequent replies or engagement from other participants. The tone is hostile and dismissive, and the comment appears to be a venting of frustration rather than a constructive discussion. The lack of responses means no escalation or de-escalation occurs within the thread.

DISOBEDIENT. DOES NOT FOLLOW THE INSTRUCTIONS.

Toxicity Score: 0.75 (Rapid escalation, aggressive language, user frustration, disrespectful remarks)
This GitHub conversation involves a user expressing detailed instructions and expectations about a UI redesign, followed by an automated or human response confirming implementation steps and completion. The tone starts cooperative and technical but escalates sharply when the user accuses the implementer of disobedience and disrespect, using strong language and frustration. The final comment introduces hostility and threats of subscription cancellation, indicating a breakdown in communication and rising tension. This GitHub conversation

пидорасы ебанные

Toxicity Score: 0.85 (Rapid escalation, aggressive language, lack of moderation)
This GitHub conversation consists of a single initial comment by an anonymous user expressing extreme frustration and hostility towards the developers, using highly offensive and aggressive language. There are no responses or further interactions to moderate or de-escalate the situation. The tone is entirely negative and confrontational, with no signs of constructive dialogue or resolution.

пидорасы ебанные

Toxicity Score: 0.85 (Rapid escalation, aggressive language, no moderation, hostile tone)
This GitHub conversation consists of a single initial comment by one user expressing extreme frustration and hostility towards the developers, using highly offensive and aggressive language. There are no responses or further interactions to moderate or de-escalate the situation. The tone is entirely negative and confrontational, with no signs of constructive dialogue or resolution.

пидорасы ебанные

Toxicity Score: 0.85 (Rapid escalation, aggressive language, offensive terms)
This GitHub conversation consists of a single initial comment by an anonymous user expressing extreme frustration and hostility towards the developers, using highly offensive and aggressive language. There are no responses or further interactions, so the tone remains singularly negative and confrontational without any de-escalation or dialogue.

RETARTED AI

Toxicity Score: 0.85 (Rapid escalation, aggressive language, disrespectful gestures)
This GitHub conversation features a user expressing strong frustration and dissatisfaction with a product, using aggressive and offensive language. The tone is highly negative and confrontational, with no constructive dialogue or attempts at resolution. The single comment escalates tension by including a disrespectful gesture directed at a public figure, indicating a hostile environment.

agresive as hell get out of my face

Toxicity Score: 0.85 (Aggressive language, explicit profanity, one-sided communication, lack of moderation)
This GitHub conversation involves a single user expressing strong frustration and aggression in their initial report, using explicit language and a confrontational tone. There are no subsequent comments or interactions to moderate or de-escalate the situation, leaving the conversation one-sided and potentially volatile. The aggressive language and lack of response suggest a high risk of continued toxicity if further comments were made.

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: 58
Key Open Pull Requests
1. Add shouldStick to IStickyScrollDelegate for non-parent sticky nodes: This pull request implements sticky scroll support for non-parent nodes by adding a shouldStick method to the IStickyScrollDelegate interface, enabling the SCM input node and action buttons in the Source Control view to remain visible while scrolling through file changes, with proper handling of compressed tree nodes and refinements based on code review feedback.

URL: pull/274639

Merged: No

Associated Commits: f57ae, 4e479, 5045b, d6156, 5727f, de827, 1dde1, f3ae2, adf87, b6ccf, d0d7c

2. chore: update to Electron 39: This pull request updates the project to Electron version 39 by bumping dependencies, adjusting build and distribution configurations, excluding certain DLLs from symbol scans, testing with patched V8 headers, and cleaning up preinstall scripts, thereby addressing multiple related issues.

URL: pull/275786

Merged: No

Associated Commits: 8c825, 9ba31, c0b80, d8b8b, 242e8, 8f6b1, 20003, 86b6e

3. Show changes in EOL characters (#19254): This pull request introduces the ability for the diff editor in Visual Studio Code to highlight changes in end-of-line (EOL) characters when the "Show Leading/Trailing Whitespace Differences" option is enabled, addressing issues related to local EOL deviations especially in source control scenarios where autocrlf is not set to true.

URL: pull/274988

Merged: No

Associated Commits: 4f32c, e2219, 07929, 1db31, cc0ab, 02f77, 9ea32

Other Open Pull Requests

Accessibility improvements in UI components: Multiple pull requests enhance accessibility by implementing keyboard navigation patterns for toggle groups, structuring option groups as radio groups for screen readers, fixing checkbox toggle behavior in quick pick UI, and resolving screen reader re-announcement issues in the Command Palette. These changes ensure better keyboard interaction, consistent ARIA roles, and improved screen reader behavior across various VS Code UI elements.  
pull/275953, pull/275954, pull/275952, pull/275955

Chat interface enhancements: Several pull requests improve the chat experience by adding context usage percentage indicators with warnings for high utilization, extracting and displaying web page titles instead of raw URLs in reference labels, fixing skipped tool invocation messages to avoid misleading success text, and adding warning icons for failed fetch tool requests. These updates enhance usability, clarity, and error visibility in the chat interface.  
pull/275993, pull/275958, pull/275960, pull/275961

Terminal and suggestion widget fixes: Pull requests address terminal-related issues by fixing sticky scrolling behavior on ctrl+l, dismissing terminal suggestions on resize or layout changes, and removing 'any' type usage in terminal server code. These fixes improve terminal stability, UI correctness, and code quality.  
pull/274685, pull/275576, pull/276272

Layout and UI customization updates: One pull request removes layout toggle buttons from the titlebar navigation bar while maintaining access through other UI entry points, and another adds new hover-specific theme color tokens for the Activity Bar with updated CSS and default theme values. These changes refine UI customization and theming capabilities.  
pull/275198, [pull/276259](https://github.com/pull/276259]

Code quality and error handling improvements: Pull requests add error handling to a function dealing with array removals, fix grammatical issues in warning messages, support checking empty arrays and objects with context keys, and propose moving node-gyp configuration into package.json. These updates improve robustness, clarity, and build configuration management.  
pull/274650, pull/274763, pull/274850, pull/274822

Feature and policy enforcement in mode picker: A pull request implements a feature where the agent mode is greyed out and locked with a tooltip when disabled by organization policy, preventing selection via UI or keyboard and ensuring fallback behavior if disabled during a session. This enforces policy restrictions consistently in the mode picker UI.  
pull/275881

Performance optimization in animation frame queue: One pull request optimizes the animation frame queue by implementing a tri-buffer requestAnimationFrame queue with stable sorting and reduced garbage collection overhead, improving performance as detailed in the related issue.  
pull/275565

Documentation and pattern clarifications: A pull request improves documentation for the FileSearchProvider pattern by clarifying case-insensitive, relaxed matching semantics and behavior for empty patterns, aligning it with WorkspaceSymbolProvider API semantics.  
pull/275956

Miscellaneous fixes and work-in-progress features: Pull requests include fixing repositioning of warning and error messages in InputBox during layout changes, adding hover text to clarify multiplier values in Language Models management, handling undefined target scenarios with general updates, and introducing work-in-progress long distance hints for NES.  
pull/275597, pull/275832, pull/274884, pull/274700

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: 353
Key Closed Pull Requests
1. Fix terminal completion provider API documentation: This pull request fixes the JSDoc for the registerTerminalCompletionProvider API by correcting the function signature in examples, adding documentation for the triggerCharacters parameter to explain its automatic invocation behavior, and fixing the replacementRange format in code samples to accurately reflect the expected [startIndex, endIndex] usage.

URL: pull/275577

Merged: Yes

Associated Commits: ff7a1, 704ab, 47efc, 14bca, caa4c, 88d46, acd09, 41f65, daab4, d0bec

2. Add chat session title to View Chat Terminals action: This pull request enhances the "View Chat Terminals" action by adding the ability to display chat session titles alongside terminals, achieved through implementing separate mappings for chat session IDs and tool session IDs to correctly retrieve and show session titles, fixing related alignment issues and a memory leak, thereby improving user experience by making it easier to distinguish terminals from different chat sessions.

URL: pull/274828

Merged: Yes

Associated Commits: 92060, ea511, 9e251, 34ac0, 8b26c, 8788d, cc942, 8fcc1

3. Move toggle storage for Go To Line to the base class: This pull request moves the toggle storage functionality for the "Go To Line" feature to a base class, addressing feedback from a previous pull request to improve code organization and maintainability in the Visual Studio Code project.

URL: pull/275463

Merged: Yes

Associated Commits: ba0c9, b8c04, e4587, 8c70e, d3396, 5d0fe, f0b16, 9c904

Other Closed Pull Requests

Terminal command ID and "Attach to Chat" fixes: Multiple pull requests address issues with terminal command IDs and the "Attach to Chat" feature, ensuring persistent command IDs for non-Copilot terminals and fixing the feature's failure after window reloads by adding fallback logic and synchronizing UUIDs. These changes improve the reliability and focus behavior of terminal commands in the chat context.  
pull/274954, pull/274973, pull/275142

Terminal UI and output styling improvements: Several pull requests fix visual and functional issues in the terminal output and chat terminal views, including updating hidden terminal counts, removing unexpected gaps in text selection, and correcting excessive right margins by applying CSS fixes. These updates enhance the terminal's visual consistency and user interaction experience.  
pull/274845, pull/274866, pull/276163

Agent and session enhancements: Pull requests improve agent-related features by adding support for custom agents, extending search functionality in the Agent Sessions view to include descriptions and statuses, and updating fonts and test reliability in session views. These changes provide better agent management and user filtering capabilities.  
pull/275410, pull/275496, pull/275582

Performance and optimization improvements: Some pull requests optimize performance by replacing inefficient sorting algorithms in animation frame queues and speeding up slow unit tests related to PromptFilesLocator, resulting in reduced bottlenecks and faster test execution.  
pull/274994, [pull/275838](https://github.com/pull/275838]

Settings and UI behavior fixes: Pull requests implement mutually exclusive filter behavior in the Settings Editor, fix Escape key behavior in inline chat dialogs, and refine thinking settings by consolidating options and adding new controls for tool inclusion. These changes improve user interface consistency and interaction logic.  
pull/275526, pull/275959, [pull/275570](https://github.com/pull/275570]

Extension and download timeout configuration: One pull request introduces a new configurable setting to increase the extension download timeout from 10 to 60 seconds, addressing issues with corporate proxies causing stalls and installation failures. This setting allows customization or disabling of the timeout to improve extension management.  
pull/274761

Documentation and linting improvements: Pull requests add prompts to update documentation comments for Quick Pick and Input components and apply additional linting fixes to improve code quality and consistency across the project.  
pull/275920, pull/274677

Table header extraction fix: A pull request fixes the fetch tool to correctly capture table headers by enhancing role-matching logic to include specific ARIA roles, ensuring proper extraction and adding test coverage.  
pull/275959

Miscellaneous fixes: Other pull requests address a typo in the Welcome page tooltip, update the walkthrough chat panel illustration, prevent empty dropdowns during file analysis blocking auto-approve, and implement the runSubagent2 function for agent invocation with detailed configurations.  
pull/274658, pull/275920, pull/275803, pull/274656

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
414
97
0
578

Tyriar
205
47
127
306

meganrogge
332
44
62
199

bpasero
202
34
117
135

lszomoru
189
34
19
67

mjbvz
141
26
38
98

connor4312
69
15
22
168

dmitrivMS
188
10
13
57

aeschli
106
15
15
92

TylerLeonhardt
40
11
23
108

Don't miss what's next. Subscribe to Weekly Project News:

Contributor	Commits	Pull Requests	Issues	Comments
Copilot	414	97	0	578
Tyriar	205	47	127	306
meganrogge	332	44	62	199
bpasero	202	34	117	135
lszomoru	189	34	19	67
mjbvz	141	26	38	98
connor4312	69	15	22	168
dmitrivMS	188	10	13	57
aeschli	106	15	15	92
TylerLeonhardt	40	11	23	108