Weekly GitHub Report for Vscode: July 07, 2025 - July 14, 2025 (12:04:36)
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:
Released on March 12, 2025, this version focuses on resolving issues identified in the February 2025 Recovery 2 milestone, with detailed release notes available 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.
-
braille board and voice over on mac: This issue highlights a bug in Visual Studio Code where the VoiceOver cursor text is not synchronized with the braille display on macOS, causing significant productivity challenges for blind developers. The user requests a fix for this issue, emphasizing the potential benefits for the blind developer community.
- The comments discuss the need for a screen recording to demonstrate the issue, suggest disabling certain settings, and explore whether the problem is due to configuration errors. Users share experiences with similar setups, and troubleshooting steps are provided, including checking screen reader mode and ensuring proper configuration of VoiceOver and the braille display.
- Number of comments this week: 24
-
Custom instructions is badly broken in the latest build.: This issue is about a bug in the latest build of VS Code Insiders, where custom instructions defined in a non-root folder are not being recognized by custom prompts, causing them to search the codebase incorrectly and fail to locate the necessary instruction files. The problem requires users to manually add custom instructions each time they run a prompt, disrupting workflows that rely on these instructions, which previously worked seamlessly in earlier versions.
- The comments discuss the issue of custom instructions not being recognized due to changes in how external files are handled, with suggestions to add a workspace folder or ensure the use of the
.instructions.mdfile extension. The user confirms the use of the correct file extension and provides directory structure details, while seeking a solution for using common instructions across multiple projects without manual copying. - Number of comments this week: 9
- The comments discuss the issue of custom instructions not being recognized due to changes in how external files are handled, with suggestions to add a workspace folder or ensure the use of the
-
VScode Insiders latest build Co-Pilot snaps out of existence once in a while: This issue describes a problem with the latest build of VS Code Insiders where the Co-Pilot chat agent unexpectedly clears the current thread, causing all changes to disappear and leaving the chat history blank. The problem seems to have started with a recent update, and the user is unable to consistently reproduce the issue or locate logs to provide further information.
- Users report that the issue occurs randomly and frequently after the latest update, with the chat agent clearing changes and history. Some users speculate it might be related to memory or data transfer issues, and they express difficulty in capturing logs. One user mentions that switching to the release build resolves the issue, indicating it is specific to the Insiders build.
- Number of comments this week: 9
-
Support Windows package identity to ensure device permissions: This issue addresses the need to support Windows package identity to ensure that device permissions, specifically microphone permissions, are retained for VS Code Speech functionality. The discussion involves exploring solutions to manage AppxPackage manifests to maintain necessary privacy controls and device capabilities on Windows installations.
- The comments discuss issues with the
RemoveAppxPackagecommand causing errors, the optional nature of the current AppxPackage manifest, and the need for privacy controls. Suggestions include using multiple manifests or hiding commands, with references to relevant documentation. The conversation concludes with a solution involving addingDeviceCapabilityfor the microphone and ensuring the package identity covers the necessary applications. - Number of comments this week: 8
- The comments discuss issues with the
-
Dev Containers fails to start on VS Code 1.102.0 with TypeError: Cannot read properties of null (reading 'filesToOpen'): This issue describes a problem where Dev Containers fail to start on Visual Studio Code version 1.102.0, resulting in a TypeError related to reading 'filesToOpen' as null. The error appears to be introduced in the latest VS Code update and affects the standard workflow with Dev Containers, although downgrading to version 1.101.2 resolves the issue.
- Multiple users confirm experiencing the same error, with some reverting to an earlier VS Code version as a temporary fix. A potential cause is linked to a recent code change, and specific actions like switching containers or opening folders in containers reproduce the issue. A suggested workaround involves opening the local folder first before reopening it in a container.
- 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 for Visual Studio Code to support generating markdown from code cells, similar to how JupyterLab handles dynamic content in its Outline feature. The request suggests that code-generated markdown should be rendered and displayed after the cell, allowing for dynamic titles and content to be included in the Outline, enhancing the functionality for users who rely on dynamic content generation.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue describes a bug in Visual Studio Code where using a
vscode://link with the parameters?new-windowor?reuse-windowdoes not function as expected, as it hijacks the existing window instead of opening a new one. The problem occurs when a user is connected to a remote server and attempts to open a link to another server, resulting in the disconnection from the current server and replacement of the window with the new server's connection. ${userHome}in a task command creates bad paths: This issue involves a problem with the${userHome}variable in a task command within atasks.jsonfile, which results in incorrect path formatting when the task type is set to "process". The incorrect path causes an error stating that the terminal process could not be started because the path to the executable does not exist, whereas using${env:USERPROFILE}instead of${userHome}resolves the issue by generating the correct path format.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where characters typed in a terminal window, when moved to a floating window during a remote connection, do not appear in real time if the main window is minimized. The characters only become visible once the main window is restored, suggesting a potential issue with the remote connection entering a "sleep" state when the main window is minimized.
- Unicode character displayed as a question mark ?: This issue involves a problem where a Unicode character, specifically the full-width quotation mark (U+FF02), is displayed as a question mark when copied into Visual Studio Code (VS Code) on Fedora 39, despite being correctly rendered in browsers like Firefox. The problem persists even when all extensions are disabled, indicating a potential bug in VS Code version 1.87.2 related to Unicode character rendering.
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: 551
Summarized Issues:
- Copilot Extension Bugs: The Copilot extension version 0.28.5 has been reported to hang consistently during operations in Visual Studio Code version 1.101.2 on Windows 10, despite the system having ample resources. Additionally, users have experienced issues with the extension not activating, failing to generate code, and causing unexpected behavior such as inserting functions inappropriately within existing code.
- Performance and Freezing Issues: Visual Studio Code users have reported performance problems, including frequent freezing and slow operations, particularly when using the Copilot extension. These issues have been noted on both Windows and macOS systems, affecting the usability of the application.
- Network and Connection Errors: Users have encountered network-related errors such as "net::ERR_CERT_COMMON_NAME_INVALID" and "ERR_NETWORK_CHANGED" while using Visual Studio Code, which may be linked to firewall rules or network connection issues. These errors require frequent restarts of the application to temporarily resolve the problem.
- Chat and Agent Mode Issues: The Copilot Chat and Agent modes in Visual Studio Code have been reported to malfunction, with issues such as the chat freezing, failing to execute tasks, and not waiting for user approval before executing commands. These problems disrupt the workflow and lead to user frustration.
- Extension Activation and Functionality Problems: Several extensions, including the Copilot extension, have been reported to fail in activating or functioning correctly, leading to issues such as unresponsive features, incorrect code suggestions, and unexpected behavior during code editing.
- Visual and Rendering Bugs: Visual Studio Code users have reported visual bugs, including incorrect rendering of text and UI elements, such as overlapping text lines, incorrect cursor positioning, and issues with syntax highlighting. These visual problems affect the readability and usability of the editor.
- Model and AI Response Failures: Users have experienced failures in AI model responses, with issues such as models not returning responses, providing inaccurate suggestions, and failing to follow instructions. These problems are particularly noted with the GPT-4.1 model and other AI-powered extensions.
- File and Project Management Issues: Visual Studio Code users have reported issues with file and project management, including problems with Git integration, incorrect file path handling, and unexpected behavior when managing files and directories. These issues disrupt the development workflow and cause user frustration.
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: 434
Summarized Issues:
- Visual Studio Code Debug Console Bug: A bug in the Visual Studio Code Debug Console was reported where text enclosed in triple-backtick markdown blocks containing the word "see" fails to display. Initially thought to be a language-independent problem, it was later identified as a user error due to a filter setting in the Debug Console.
- JSON Schema Error Suppression Feature Request: A feature request was made to suppress errors related to the
$schemaproperty in JSON files by introducing a configuration option"json.suppress_infile_$schema": true. This would allow users to manage schema validation more flexibly without encountering errors for inline schema definitions.
- MCP Server Image Response Feature Request: A user requested a feature to include image responses directly in the chat output of the MCP server. Currently, images only appear in the MCP section and not in the final response.
- PowerShell Terminal Unresponsiveness: A problem was reported where the PowerShell terminal in Visual Studio Code intermittently becomes blank and unresponsive. This issue affects only PowerShell and not other terminals like CMD or Git Bash, with no consistent solution or error messages.
- Encryptor and EncrypThor Extensions Bug: In Visual Studio Code version 1.101.2, the Encryptor and EncrypThor extensions fail to execute encryption and decryption commands. This issue, which previously worked in version 1.99.3, is potentially related to updates in Electron and Node.js.
- Automated Testing Timeout Error: A build failure in a GitHub project was reported due to a timeout error when attempting to get the '.single-terminal-tab' element during automated testing. This issue was identified as a duplicate of another issue.
- Task Execution Duplication Bug: A bug was reported where tasks are executed twice by the agent after summarizing chat history. This occurs particularly when the task is lengthy and the summary process occurs within the same thread, seemingly resetting the agent's task progress.
- Git Branch Shortcut Feature Request: A feature request was made for Visual Studio Code to create a shortcut that allows users to open a new window for a different Git branch of the same workspace. This would utilize Git's worktree functionality to manage multiple working copies without needing to clone or rsync the repository.
- Internet Connection Toggle Bug: A bug in the VS Code extension version 0.28.5 was reported, where the user experiences persistent problems requiring a restart of the application after toggling the internet connection off and on. This issue occurs specifically on a Windows 10 system running a Linux environment through WSL2.
- MCP Server Auto-Discovery Issue: A user sought a solution to prevent Visual Studio Code Insiders from automatically discovering and listing Model Context Protocol (MCP) servers configured for other applications. These servers, such as Claude Desktop and Cursor, are appearing repeatedly in the Copilot Chat panel and server lists.
- Terminal and Problems View Splitting Bug: A bug was reported in Visual Studio Code where splitting the terminal and problems view side-by-side is irreversible. Users are unable to reset the view to its original state, despite attempts to drag the terminal back to its initial position.
- Shell Environment Parsing Error: An error message "Unable to parse the shell environment: Bad escaped character in JSON at position 6601 (line 2 column 6600)" appears upon startup in Visual Studio Code on Windows 11. This indicates a parsing error in the shell environment configuration, which persists despite following troubleshooting documentation.
- Notebook Cell Expansion Bug: A bug was reported in a GitHub project where the contents of a notebook cell, when expanded using the "show more" option, extend beyond the visible area of the panel chat. This causes the Continue/Cancel buttons to be inaccessible.
- Copilot Agent CLI Response Parsing Issue: A bug was reported where the copilot agent, Claude Sonnet 4, frequently hangs and fails to parse the CLI response when running frontend unit tests using the "npm run test" command. This issue particularly affects the vitest testing framework in a development environment using VS Code version 1.101.2 on Windows with WSL2.
- Copilot Extension Custom Instructions Bug: A bug in the Copilot extension for VS Code was reported where custom instructions specified in an
applyToinstruction file are not applied to newly created files, only to existing ones. It has been identified as a duplicate of another issue that was fixed in version 1.102.
- Copilot Model Response Failure: A bug was reported in the Copilot feature where the model fails to return a response across all selected agents. This potentially indicates a service issue and includes detailed system and extension information for troubleshooting.
- Outdated CSS Classes in Custom Component: A bug was reported where the custom Card component in a project is using outdated CSS classes (bg-card and text-card-foreground) that are no longer defined in the new Tailwind setup. This results in the card appearing transparent and unstyled, and it suggests updating the component to use standard Tailwind classes for proper styling.
- Copilot Extension Crash on Darwin arm64: A bug was reported where the Copilot extension version 0.28.5 crashed on a system running VS Code version 1.101.2 on a Darwin arm64 OS. The user was prompted to report the incident.
- High CPU and RAM Usage on First Launch: A problem was reported where Visual Studio Code experiences unusually high CPU and RAM usage during the first launch after a fresh boot on Windows. The CPU usage spikes to 4-7 percent and RAM usage rises significantly, which only stabilizes after restarting certain extensions.
- Extension Malfunction Preventing Downloads: A problem was reported where a user experienced a malfunction with a Visual Studio Code extension, which was working fine initially but later failed to function properly. This prevented the user from downloading or enabling necessary extensions.
- VS Code Crashes with Conditional Formatting: A bug was reported where the user experiences repeated crashes of the VS Code application, specifically when dealing with simple conditional formatting. The user expressed frustration over the situation, noting the use of version 0.28.5 of an extension on a Darwin arm64 system.
- GitHub Copilot Errors in Dev Container: A bug was reported where the user experiences frequent errors when using GitHub Copilot within a Dev Container in Visual Studio Code. The tool functions correctly outside of the Dev Container environment.
- Copilot Chat Feature Error: A bug was reported where the user is unable to use the Copilot chat feature in Visual Studio Code version 1.101.2 on a Windows 10 system. The user receives an error message with the extension version 0.28.5, and it has been marked as a duplicate of another issue (#254363).
- Copilot Restrictive Behavior: A user's frustration was reported with GitHub Copilot being overly restrictive and flagging their requests for HTML or CSS guidance as irresponsible. This occurs despite the queries being legitimate and rephrased multiple times.
- Companion Software Component Failure: A problem was reported where a software component called "Companion" failed to load in version 1.101.2 of a project. This component is necessary for completing school-related tasks, and it was suggested that the problem might be caused by an extension.
- Copilot Performance Comparison: A user questioned the perceived lower performance of Copilot when using the Claude Sonnet 4 model compared to the Claude Code model. The user suggested a potential intentional limitation by the upstream vendor.
- Chat Feature Processing Delay: A bug was reported where the chat feature in a specific version of an extension for Visual Studio Code appears to be functioning but fails to process any requests. This results in the user experiencing prolonged processing times exceeding 30 minutes and the consumption of premium requests without any successful outcomes.
- 504 Server Error with Claude Sonnet 4: A bug was reported where users encounter a 504 server error while using the Claude Sonnet 4 extension version 0.28.5 on VS Code version 1.101.2. This occurs on a Darwin arm64 system, resulting in failed requests and prompting users to try again.
- Extension System Information for Diagnosis: A bug was reported in the Visual Studio Code extension version 0.28.5, running on Windows 10, where the user has provided detailed system information and A/B experiment data to help diagnose the problem.
- Advanced Model Selection Issue: A problem was reported with the automatic selection of advanced models in VS Code when switching between Ask and Agent modes. This leads to unnecessary use of advanced features for simple tasks and requires manual intervention to revert to basic models.
- Chat History Viewing Bug: A bug was reported in Visual Studio Code where the user is unable to view chat history when selecting a history item. This also prevents the use of GitHub Copilot, and it includes detailed system information and a list of installed extensions.
- Copilot Agent Terminal Command Issue: A problem was reported with GitHub Copilot in VS Code where the Copilot agent does not correctly wait for terminal commands like
eslint,prettier,tsc, orknipto complete. It either prematurely indicates that the command ran without errors or repeatedly states that the command is still running.
- Azure OpenAI Custom Model Error: A bug was reported where requests using the Azure OpenAI custom model o4-mini fail due to an unsupported 'temperature' value of 0.1. The model only supports the default value of 1, resulting in a 400 error with an "unsupported_value" code.
- Copilot Chat Feature Auto-Change Bug: A bug was reported where the Copilot chat feature in Visual Studio Code automatically re-applies changes to a freshly cloned repository's main branch. This occurs even after those changes were made in a different feature branch and the repository was deleted and recloned.
- Copilot Chat Message Sending Bug: A bug was reported on a Windows 11 machine using VS Code with WSL 2, where the user is unable to send new messages through voice or typing. The problem persists even after switching IPs, with the logs indicating a GitHub login failure affecting the Copilot extension.
- Copilot Chat Command Suggestion Bug: A bug was reported in the VS Code extension where the Copilot Chat feature fails to read and suggest fixes for the last command executed in the terminal. This occurs despite the expectation that it should be able to access and analyze the command history to provide helpful suggestions.
- Bug Report Template: A bug report for the Visual Studio Code project on GitHub was submitted, where the user is instructed to follow specific guidelines and troubleshooting steps. This includes disabling extensions and using the latest Insiders build to determine if the problem persists.
- Copilot Request Size Error: A performance problem was reported in Visual Studio Code where any command or prompt given to Copilot results in a recurring error message. The message states "Sorry, your request failed. Please try again. Request id: 4318802b-e251-429b-b3f7-94517c34d89e Reason: Request Failed: 413 Request Entity Too Large," indicating that the request size exceeds the server's capacity to process it.
- WSL Chat Functionality Bug: A bug was reported in the WSL system where the chat functionality in VS Code is not working properly. Users are unable to send messages by clicking the button or using the right-click options for code snippets, although the chat works successfully on Windows.
- Copilot Chat Feature Changelog Update: An issue was reported pertaining to the task of updating the CHANGELOG.md file for the Copilot Chat feature in the Visual Studio Code project.
- Core ARC Tracking System Bug: A bug was reported in the Core ARC tracking system of a GitHub project, where telemetry data is not sent by default unless specific debug settings are enabled. This was evidenced by a verification comment showing a count of telemetry events.
- Branch Protection Feature Request: A request was made to modify Visual Studio Code's branch protection feature to allow users to exclude specific repositories from the rule that prevents direct commits to main or master branches. The current setup does not accommodate exceptions for certain repositories where direct commits are necessary for rapid development.
- Copilot Model Response Failure: A bug was reported where the model unexpectedly failed to return a response, potentially indicating a service problem. The report includes detailed system information and version details for troubleshooting.
- GitHub Copilot Code Truncation Issue: A problem was reported where GitHub Copilot, when used in Visual Studio 2022, is causing code files to be truncated. The user suspects it might be related to Visual Studio 2022 itself, as the problem persists across different modes and language models.
- Persistent File Index Bug: A bug was reported where the user has been frustrated for 49 hours due to a persistent problem with a file in the index not being fixed. This occurs despite repeated attempts to resolve it, while using version 0.28.5 of an extension on Visual Studio Code version 1.101.2 on a Windows 10 system.
- Language Model Access Issue: A bug was reported where the user is unable to access the language model while using the Agent in Visual Studio Code version 1.101.2 on Windows 10. The problem occurs in extension version 0.28.5.
- GPT-4.1 Agent Test Suite Bug: A problem was reported where the GPT-4.1 agent, when using the "best mode" chat mode, initiates a backend test suite in VS Code but is unable to automatically retrieve the test results from the terminal output. This requires manual intervention to obtain the test results.
- Tool Usage Error in Extension: A bug was reported where a user encounters an error message indicating that more than 128 tools are being used, which is incorrect. This causes the system to become unresponsive, and it occurs in the context of using a specific extension version (0.28.5) on Visual Studio Code version 1.101.2 running on Windows with a remote Linux environment.
- ASP.NET Core Port Configuration Bug: A bug was reported in an ASP.NET Core project where, despite changing the default ports in the launch settings from 5000 to 80, the application continues to listen on port 5000 when executed using the 'dotnet run' command. The user is unable to determine the cause of this behavior.
- Network Protocol Error in VS Code: A bug was reported in Visual Studio Code version 1.101.2, where users encounter a "net::ERR_HTTP2_PROTOCOL_ERROR" due to potential firewall or network connection issues. This occurs while using extension version 0.28.5 on Windows 10, and suggests checking firewall rules and network connections as a resolution.
- Launch Configuration Variable Resolution Bug: A problem was reported in Visual Studio Code where the
envFileis not utilized to resolve variables within the "program" property of thelaunch.jsonconfiguration. This causes the launch configuration to fail unless the variable${CMagneto__ProjectEntrypointExe}is manually hardcoded.
- Copilot RAI System Filtering Issue: A bug was reported where the user, after returning to their project in VS Code, found that GitHub Copilot was consistently filtering responses due to the RAI System. This prevents any successful interaction, despite previously functioning correctly.
- Claude Model Request Error: A user experienced errors due to high demand on the upstream model provider while using the Claude 4 model in their copilot agent chat. This led to concerns about being charged for unsuccessful requests and a request for a refund or credit.
- Agentic Mode Edit Failure: A bug was reported in version 0.28.5 of a VS Code extension where the agent fails to make an edit in agentic mode but incorrectly believes it has completed the task. This was reported on a Windows 10 system with specific hardware and software configurations.
- Terminal Command Alias Bug: A problem was reported where terminal commands starting with the letter 'c' are incorrectly receiving 'code' or 'code-insiders' flag completions. This is likely due to an alias configuration, resulting in unexpected behavior and duplicate completions for the 'code' command.
- Copilot Extension Configuration Request: A request was made to determine whether the open-source Copilot extension for VSCode will support a configuration that allows users to operate without logging into a GitHub account. This would enable the use of locally hosted models, which is crucial for institutions considering the integration of VSCode Copilot's View, Edit, and Agent Modes.
- Bracket Colorization Bug: A problem was reported where custom token colors for round, square, and curly brackets in a Visual Studio Code theme are not being applied as expected. This occurs despite specifying the color settings in the theme's JSON configuration, and it suggests that the issue may be related to the
bracketPairColorizationfeature needing to be disabled.
- Copilot Codespace Message Sending Bug: A bug was reported where the user is unable to send messages to Copilot in their specific codespace, despite attempts to reinstall and create new codespaces where Copilot functions correctly. The problem persists in the user's current setup using VS Code version 1.101.2 on Windows_NT x64 10.0.22631.
- Network Resolution Error in Extension: A bug was reported in a Visual Studio Code extension (version 0.28.5) on a Linux system, where the user encounters an error message indicating a network resolution problem (net::ERR_NAME_NOT_RESOLVED). The user is advised to check firewall rules and network connection, with the error occurring in a specific environment setup involving Zorin OS and certain GPU and CPU configurations.
- JavaScript Error Line Display Bug: A problem was reported where Visual Studio Code is not displaying red error lines for broken JavaScript code, even when incorrect imports are present. It suggests enabling type checking as a potential solution.
- Claude Agent Mode Import Bug: A bug was reported in the VS Code project where the "Claude in agent mode" feature fails to recognize necessary import statements in the app.py file. This leads to a broken queue system due to missing imports such as logging, serial, time, threading, uuid, redis, os, and configparser, which are essential for the queue's functionality and distributed locking system.
- Claude Sonnet 4 Ask Mode Bug: A bug was reported in the VS Code extension where the "Claude Sonnet 4 in Ask Mode" incorrectly identifies the deletion of function calls that are actually present. This specifically breaks the queue system by removing the essential
queue_bypass_lockparameter from measurement functions, which was necessary for allowing queue-executed measurements to bypass lock acquisition.
- Responsible AI Service Prompt Error: A bug was reported where a user encountered an error message from the Responsible AI Service when attempting to create a prompt in Visual Studio Code that displays text in a single line across the full width of the screen. The error suggests the prompt be rephrased.
- New Terminal APIs Documentation Update: An issue was reported involving updating the documentation to include information about the new terminal APIs, specifically
onTerminalandonTerminalShellIntegration, once they are merged.
- MCP Server Management Bug: A problem was reported regarding the inability to view or manage the start/stop status of MCP servers within the
mcp.jsonfile in the latest VS Code Insiders edition. Additional complications related to authentication and permissions for remote servers were also noted.
- Azure DevOps Project Retrieval Error: A bug was reported where an attempt to retrieve a list of all Azure DevOps projects using a specific configuration in Visual Studio Code fails due to a limitation of including more than 128 tools in the request. This results in an error message and a request to try again.
- Dropped Connections in VSCode: A problem with repeated dropped connections in the Microsoft VSCode project was reported, as indicated by the title, although no further details are provided in the body or comments.
- Einval Error in Extension: A bug was reported in the Visual Studio Code extension version 0.28.5, where the user encounters an error message "einval" with no additional output on a Windows 10 system. The report includes detailed system and experimental feature information for troubleshooting.
- Audible Notification Feature Request: A request was made to add an audible sound notification feature in GitHub Copilot, which would alert users when Copilot completes a suggestion or requires user action. Users have experienced difficulties with the current settings not functioning as expected.
- Chat Mode Reset Bug: A bug was reported where the chat mode is unexpectedly reset to Agent mode when retrying a request after initially running it with a custom chat mode. This was detailed in the steps to reproduce.
- Response Filtering Issue: A problem was reported where a user's response was unexpectedly filtered out, prompting them to question the appropriateness of this action and seek feedback from others on whether such filtering should have occurred.
- VS Code Unresponsiveness with Copilot: A problem was reported where Visual Studio Code becomes unresponsive almost every minute when used with GitHub Copilot. This is due to a recurring "The window id not responding" error, which is exacerbated by synchronous operations like encoding and hash computation during chat content session saving.
- WebviewPanel API Event Handler Request: An issue was reported highlighting the absence of an
onDidChangeVisibilityevent handler in theWebviewPanelAPI. This handler is crucial for determining when to redraw the panel upon visibility changes, and the existingonDidChangeViewStatehandler is insufficient as it triggers multiple times during panel movements.
- MCP Server Location Attribute Bug: A problem was reported regarding the undefined
locationattribute for all MCP servers, resulting in them being inaccurately displayed as running globally. This causes execution errors on remote servers and misplaces controls within the interface.
- Prompt Validation Error in Extension: A bug was reported in the Visual Studio Code extension version 0.28.5, where a user's request failed due to a prompt validation error indicating that no messages were provided. The report includes detailed system information and A/B experiment data for troubleshooting.
- Bug Report Template: A bug report template for a problem encountered in Visual Studio Code was submitted, where the user is instructed to follow specific guidelines and troubleshooting steps. This includes disabling extensions and using the latest Insiders build to determine if the issue persists.
- Sample Bug Report Template: A sample bug report template for Visual Studio Code on GitHub was submitted, which includes instructions for users on how to properly submit a bug report. It advises checking for duplicates, testing with the latest build, and determining if the issue persists when all extensions are disabled.
- Notebook Tool Searchability Issue: A problem was reported where the tool 'readCellOutput' is not easily discoverable when searching for notebook-related tools. It suggests that the word 'notebook' should be included in the description to improve searchability and clarity.
- Lisp Virtual Machine Debugging Bug: A bug was reported where a user's request to write a program in Visual Studio Code got stuck during the debugging process at a specific command involving a Lisp virtual machine. This problem occurs on a Windows system using WSL2 to run a Linux environment.
- Lisp Virtual Machine Debugging Bug: A bug was reported where a user encountered a problem with a program getting stuck during a debugging process, specifically on a command involving a Lisp virtual machine. This occurs while using version 0.28.5 of an extension in Visual Studio Code on a Windows system with WSL2 running Ubuntu.
- Companion Application Save Bug: A problem was reported where a user is unable to save their lab in a companion application, as indicated by a continuously spinning wheel. This issue was reported in version 1.101.2 of the software, with the issue being documented on the GitHub repository for Microsoft's Visual Studio Code.
- Entity Too Large Error in Extension: A bug was reported in the VS Code extension version 0.28.5, where the user encounters an "entity too large" error that prevents responses to basic questions. There is no clarity on which entity is causing the problem, and it occurs on a Linux x64 system running VS Code version 1.101.2.
- Code Review Efficiency Feature Request: A feature request was made in VS Code to improve code review efficiency by allowing users to hide semantically identical differences, such as variations in code style, when comparing files. This would allow users to focus only on meaningful changes.
- Jira Ticket Retrieval Error: A bug was reported in the Visual Studio Code extension (version 0.28.5) where a user encounters an error message indicating that their request to retrieve a Jira ticket using MCP fails because it includes more than the allowed 128 tools. The error occurs on a system running macOS with specific hardware and software configurations.
- Application Stuck Bug: A bug was reported in the VS Code extension version 0.28.5, where users experience the application getting stuck and not progressing further, despite multiple attempts to retry. This ultimately results in an error after a few minutes on Windows_NT x64 10.0.22631.
- Send with #codebase Feature Bug: A bug was reported where the "send with #codebase" feature in a specific version of a VS Code extension became unexpectedly greyed out. This affects its functionality on a system running macOS with an Apple M1 Pro processor.
- Refund Request for Noncompliant Models: Users are requesting a refund or rebate for credits spent on noncompliant and disobedient models that require excessive corrections. These models waste time, money, and effort, potentially jeopardizing the customer base if charges for such models continue.
- Git Worktree Exclusion Feature Request: A feature request was made for Visual Studio Code to automatically exclude git worktree directories from file watching and indexing to improve user experience and performance. The current process requires manual configuration in settings.json, which is cumbersome when working with multiple worktree directories.
- Startup Experiment Group Behavior: A question was raised about whether the persistent application of treatments, such as
--startup-experiment-group=maximizedChat, upon opening a new window or reloading an existing one is intentional. It was clarified that this behavior is indeed intentional to maintain consistency and avoid user confusion.
- Git Worktree Management Feature Request: A feature request was made for Visual Studio Code to automatically detect and manage git worktree directories without requiring manual configuration or window reloads. This would enhance the developer experience by streamlining workflows involving multiple branches and frequent worktree creation.
- Persistent Changes in Cloned Project: A problem was reported in Visual Studio Code where changes that were not made by the user appear in a cloned project with submodules. Despite attempts to discard these changes, they persistently reappear, making it impossible to remove them.
- Ambiguity in "Show Installed Servers" Menu: A problem was reported regarding the ambiguity of the "Show Installed Servers" menu item within the "Configure Chat" button. It suggests that its purpose or functionality is unclear to users.
- Chat Input Box Disappearance Bug: A bug was reported where the chat input box disappears in the chat view when either installing the Copilot extension or performing setup tasks in Visual Studio Code. This occurs particularly under specific startup conditions.
- TypeScript Context Provider Telemetry Sampling: An issue was reported involving implementing a sampling mechanism for TypeScript context provider telemetry, which is currently sent for every context request. This would facilitate a broader rollout by allowing GitHub to set a flag that determines how the telemetry should be sampled.
- Inline Copilot Window Closure Bug: A bug was reported in the Visual Studio Code extension version 0.28.5, where the inline copilot window fails to close after completion. It has been resolved as confirmed by a user who noted that the problem no longer exists.
- Unintended Console Log in Code: An issue was reported regarding the presence of an unintended console log in the code at line 69 of the file
promptHeaderDiagnosticsProvider.tswithin the Visual Studio Code repository. This has been identified and subsequently closed.
- Accessibility Signals for Test Results: A request was made for the addition of accessibility signals in Visual Studio Code to notify users when tests succeed or fail. The current subtle indicators are difficult to monitor for individuals with poor eyesight, and the user has been using a workaround involving a terminal beep that is not ideal for continuous testing.
- Sonnet 4 Editing Process Bug: A bug was reported in Sonnet 4 where the editing process gets stuck at 98-100% completion or fails to apply edits. This leads to wasted request quotas and necessitates workarounds such as restarting the IDE or switching models to temporarily resolve the problem.
- Typographical Errors in Codebase: An issue was reported regarding the presence of multiple typographical errors involving "MCP" and "MPC" within the codebase of the Visual Studio Code project. This was identified in version 1.102.0-insider on macOS 15.5 and has been documented on GitHub for resolution.
- Copilot Pro Subscription Functionality Issue: A bug was reported where the user, despite having a valid Copilot Pro subscription, experiences functionality issues with Visual Studio Code's Copilot Chat. The feature prompts for an upgrade, while the same subscription works correctly with Visual Studio's Copilot Chat.
- Table Designer Loading Delay: A bug was reported in Visual Studio Code Insiders version 1.102.0-insider on Windows 10, where opening the Table Designer for a new table takes more than three minutes. It suggests filing the issue against the specific extension providing the table designer functionality.
- Claude Sonnet 4 Demand Error: A problem was reported where a user is experiencing an error message indicating high demand from the upstream model provider. This results in the consumption of their premium request quota upon retry, and the user argues that they should not be charged for retries due to this error.
- CSRF Token Retrieval Error: A bug was reported where the system fails to obtain a CSRF token, resulting in a 404 error when attempting to access the endpoint
http://localhost/apis/index_v2.php/csrf-token. This affects the registration process in bothregistro-admin.jsandregistro-residente.jsscripts.
- SFDX Project Creation Bug: A bug was reported where the command 'sfd:create project with manifest' fails to execute properly in Visual Studio Code version 1.101.2 on Windows 10, using extension version 0.28.5. This results in no subsequent action or response.
- Vertical Terminal Split Feature Request: A user requested the ability to split the terminal window vertically in addition to the existing horizontal split option in Visual Studio Code. Suggestions were provided in the comments on how to achieve a similar effect by moving the terminal to the editor area.
- Memory Access Error in Copilot Chat: A bug was reported in Visual Studio Code where a "memory access out of bounds" error occurs during Copilot chat interactions. This affects the usability of the feature on Windows 10 with specific system configurations and software versions.
- Workspace Settings Separation Feature Request: A feature was proposed for Visual Studio Code that allows for the separation of workspace settings into shared configurations accessible via a public URL and project-specific settings stored in a Git repository. This would enable easier updates and consistency across multiple projects by caching external template files locally and applying changes only when the workspace is opened.
- Tool Update Indicator Improvement: A problem was reported regarding the user experience confusion caused by the current tool update indicator in a GitHub project. It suggests improvements such as using a blue dot over the existing tool icon or automatically refreshing the tool list to enhance clarity and usability.
- Claude Service Rate Limiting Issue: A bug was reported where a user experiences rate limiting on the Claude service despite having available budget for premium requests. This was reported in the context of using VS Code version 1.101.2 on Windows 10 with extension version 0.28.5.
- Shell Integration Directory Addition: An issue was reported involving adding the current working directory to the shell integration section in the terminal hover feature of Visual Studio Code. A code reference was provided for implementation guidance.
- Copilot Content Filter Misinterpretation: A bug was reported where GitHub Copilot is inappropriately blocking standard developer prompts with a message indicating that the response was filtered by the Responsible AI Service. This is likely due to a content filter misinterpreting terms like "parent" and "child," and requests an investigation or the ability to whitelist developer-context terms.
- HTML Formatting Flagging Issue: A user experienced an unexpected flagging by the responsible AI service when attempting to format an HTML file in Visual Studio Code version 1.101.2.
- Untrusted URL Warning Visibility: An issue was reported about ensuring that a warning message regarding the fetching of untrusted URLs is always visible to users without requiring them to click a "See more" link. The current implementation hides the warning unless expanded, which could potentially lead to security oversights.
- Gemini 2.5 Pro Request Error: A bug was reported where every attempt to use Gemini 2.5 Pro (Preview) in Visual Studio Code results in a "400 Bad Request" error. This occurs despite using the extension version 0.28.5 on Windows 10, and includes detailed system information and A/B experiment data for troubleshooting.
- Copilot Pro Upgrade Bug: A user who upgraded to Copilot Pro is experiencing a bug where the service is not functioning as expected. It continues to prompt them to upgrade despite already having an active subscription.
- Terminal Allow List Removal: An issue was reported involving temporarily removing the default terminal allow list in a project to ensure safety while ongoing discussions are completed. Plans to implement policy controls when the feature is integrated into the core were referenced in related issues.
- Terminal Initial Hint Refinement: An issue was reported involving refining the initial hint displayed in the terminal of the Visual Studio Code editor, as indicated by the title "Refine terminal initial hint" and the lack of detailed description in the body.
- Claude Sonnet 4 Rate Limiting Error: A bug was reported where the user is experiencing rate-limiting errors with the Claude Sonnet 4 and Claude 3.7 models due to exceeding Copilot token usage. This is indicated by the error message and server error code, while using VS Code Insiders on a Linux system.
- Agent Mode Undo Function Bug: A bug was reported in the Agent mode of a software where using the undo function incorrectly reverses changes in the wrong file (A.ts instead of B.ts) after modifications have been made to multiple files. This occurs specifically in version 1.102.0-insider of the application.
- GitHub Copilot Model Switching Error: A bug was reported where switching from the free GitHub Copilot model to a paid API model fails with a "canceled" error on subsequent requests. This occurs after using up a month's worth of GPT-4.1 questions in the Copilot window, as reported in the context of using VS Code version 1.101.2 on a Linux system.
- VSCode Hooks System Feature Request: A feature request was made to add a hooks system in VSCode, similar to git hooks, to allow users to run custom scripts or commands for customizing GitHub Copilot behavior. This would enhance customization, security, and integration with development workflows.
- Task Execution Terminal API Update: An issue was reported involving updating the code to utilize the new
taskExecution.terminalAPI instead of the existing workaround for obtaining a terminal for a task, as referenced in the provided GitHub link.
- Network SSL Protocol Error: A bug was reported where the user consistently encounters a network-related error message, specifically "net::ERR_SSL_PROTOCOL_ERROR," during execution. The user is advised to check firewall rules and network settings.
- Responsible AI Service Filtering Error: A bug was reported where a user, despite subscribing to GitHub Pro, receives an error message stating "Sorry, the response was filtered by the Responsible AI Service" when using a specific extension version (0.28.5) on VS Code version 1.101.2 on a Windows 10 system.
- UI Overlap in Agent Mode: A problem was reported where a user experiences a UI overlap problem in Visual Studio Code when using the agent mode "keep" feature. This interferes with prompt tool searches, specifically when attempting to search for a tool or file using the '#' character.
- Jupyter Notebook Copy-Paste Bug: A bug was reported by a user on an Apple Silicon-based MacBook Air using Visual Studio Code, where copy-pasting and function suggestions intermittently fail to work in Jupyter Notebook files. This necessitates frequent application restarts, while these features function correctly in regular Python files.
- Copilot Instruction Adherence Issue: A problem was reported where GitHub Copilot does not consistently adhere to the guidelines specified in the
.github/copilot-instructions.mdfile when generating code. This particularly relates to using modern features of Go(lang) as specified in the instructions, despite the user's environment and tools recognizing these features.
- SchemaStore Domain Update: An issue was reported involving updating references from the deprecated subdomain
json.schemastore.orgto the standardizedwww.schemastore.orgin a GitHub project. This is part of a transition to ensure consistency and future-proofing.
- Copilot Instruction Adherence Issue: A problem was reported where GitHub Copilot does not consistently adhere to user-provided guidelines specified in a .github/copilot-instructions.md file when generating code. This particularly involves failing to utilize modern Go language features as instructed, despite the guidelines being recognized and sometimes followed upon reminder.
- Copilot Extension Initialization Delay: A bug was reported where the GitHub Copilot extension in Visual Studio Code takes too long to initialize. The user is prompted to ensure they are signed in to GitHub and have the GitHub.copilot-chat extension installed and enabled, and it was marked as a duplicate of another issue.
- Copilot Chat Image Upload Bug: A bug was reported in the GitHub Copilot Chat extension for VS Code, where after uploading an image to a conversation, the agent stops responding and subsequent messages result in blank responses. This was resolved in a later version of the software.
- Network Connection Reset Error: A bug was reported in the Visual Studio Code extension version 0.28.5, where users encounter a "Request processing failed" error due to a network connection problem, specifically an "ERR_CONNECTION_RESET" error. Users are advised to check their firewall rules and network connection.
- AI Summary Filtering Bug: A bug was reported in which attempts to create a summary using an AI in a specific version of a VS Code extension (0.28.5) result in the summary being unexpectedly filtered. This occurs despite the absence of any inappropriate content in the code or text.
- Service Removal Infinite Loop Bug: A bug was reported where an attempt to remove a service from the codebase using a specific prompt led to the system getting stuck in an infinite loop. Details were provided about the file involved, the software versions, and the system configuration.
- Responsible AI Service Message Bug: A bug was reported in the VS Code extension version 0.28.5 where the user repeatedly receives a "Responsible AI Service" message in response to all inquiries after pasting an Excel table with two columns. Attempts to resolve the issue by restarting VS Code have been unsuccessful.
- TaskExecutionTerminal API Proposal: An issue was reported pertaining to the proposal of a new API feature,
taskExecution.terminal, in the Microsoft VSCode project. This has been closed with the resolution linked to the commit identified by hash 9362739ef42d78d990745630f37dafcaa360bd34.
- Voice-Over Cursor and Braille Board Feature: An issue was reported pertaining to a feature request or bug report related to the functionality of the voice-over cursor and braille board in the Visual Studio Code environment, as indicated by the title "screenshot voice over cursor and braille board."
- Model Switching Performance Issue: A problem was reported regarding the slow response times for summarization requests after switching from the gpt-4.1 model to other models. It suggests a reversion to gpt-4.1 and proposes experiments to improve performance, including fixing a prompt cache issue and considering future use of alternative models like 4o-mini or 4.1-mini.
- Copilot Model Response Failure: A bug was reported where the GitHub Copilot model unexpectedly fails to return a response, indicating a potential service issue. The report includes details about the user's system configuration and software versions to assist in diagnosing the problem.
- Terminal Selection Mode Bug: A bug was reported in Visual Studio Code where setting the selection mode to 'never' and having only one suggestion appear causes the Enter key to not function as expected. This results in failing to redirect input to the terminal.
- Model Response Failure on macOS: A bug was reported in the Visual Studio Code extension version 0.28.5, where the user encountered an error message indicating that the model unexpectedly did not return a response. This suggests a potential service issue on a system running macOS with an Apple M2 Pro processor.
- HTTP2 Protocol Error with GPT-4o: A bug was reported where users encounter an "Error Code: net::ERR_HTTP2_PROTOCOL_ERROR" and are unable to use GPT-4o without credits. This is alongside a request failure message, suggesting a need to check firewall rules and network connections, with the problem occurring on a specific version of the VS Code extension and Windows operating system.
- Terminal Context Information Formatting: An issue was reported addressing the need to improve the formatting of terminal context information in a GitHub project. This involves cleaning up spacing, removing empty "group" sections, and potentially organizing tasks and terminals separately to enhance clarity and comprehension.
- MCP Server Start Button Bug: A bug was reported in the mcp.json file where, if multiple MCP servers are defined, only one server is displayed with a "Start" button. This affects users on the VS Code Insiders version 1.102.0-insider on Darwin arm64, and has been reported as fixed in the latest Insiders update.
- Copilot Chat Message Sending Bug: A bug was reported where the user is unable to send messages in Copilot Chat when using the extension on a Google Cloud Platform instance. This works fine in their local environment, and it was resolved by identifying that the Postman extension was modifying the chat configuration, thereby disabling chat messaging.
- Copilot Extension Test Running Bug: A bug was reported where the Copilot extension in Visual Studio Code version 1.101.2 on Windows 10 gets stuck indefinitely at the "running tests" step after the user instructs it to remove some code. The problem occurs in extension version 0.28.5.
- AI Feature Removal Request: A user requested the removal of AI-related features from their screen in Visual Studio Code, as indicated by the title and the request in the body. A comment provided a link to a FAQ on disabling AI functionality.
- Python Script Execution Bug: A bug was reported where executing a specific Python script in the terminal causes the system to become unresponsive. Details were provided about the environment including the extension version, VS Code version, and OS version, and a comment suggests that additional information is needed for a more actionable report.
- Copy Function Bug in VSCode: A bug was reported in Visual Studio Code where the copy function, both through keyboard shortcut (cmd-C) and right-click menu, stops working after updates to VSCode and Copilot. This temporarily resolves after restarting VSCode, with the problem occurring when running a notebook using a Bokeh background server.
- Copy Function Bug in VSCode: A bug was reported where the copy function in VSCode, using either cmd-C or right-click-Copy, stops working after updates to VSCode and Copilot. This temporarily resolves after restarting VSCode, with the problem potentially linked to running a notebook using a Bokeh background server.
- Chat Mode Tool Limit Bug: A problem was reported in a GitHub project where creating a chat mode without specifying tools results in an error due to the system overriding disabled tools and exceeding the 128 tool limit. It suggests that tools should only be enabled or disabled when the chat mode is toggled rather than on every request.
- Sticky Scroll UI Bug: A user interface problem was reported in Visual Studio Code where a feature called "Sticky Scroll" causes a line to appear across the top of the editor. This makes the cursor difficult to track and slows down the process of deleting that line, affecting the user's ability to edit effectively.
- MacOS Spacebar Feature Identification: A problem was reported where pressing the spacebar twice inside a JavaScript regular expression in Visual Studio Code unexpectedly inserts a period character. This was later identified as a feature of MacOS rather than a bug in the editor.
- Settings Sync Suspension Bug: A bug was reported in VS Code Insiders where the settings sync feature was unexpectedly suspended due to the application making too many requests to the server. This occurs despite the user not intentionally initiating any sync requests, as evidenced by the log showing repeated automatic sync triggers without any changes being detected.
- Copilot Package Breakage Misinterpretation: A bug was reported where GitHub Copilot refuses to assist users when they enter the phrase "break system packages," which is intended to refer to the Pip
--break-system-packagesoption. Copilot mistakenly interprets the request as potentially harmful and thus does not provide assistance unless the request is phrased differently from the start.
- Claude Sonnet Model Response Failure: A bug was reported encountered while using the Claude Sonnet model in Agent mode, where the model failed to return a response after an initial request error (ERR_NAME_NOT_RESOLVED). This suggests a potential service issue that needs to be addressed.
- VS Code Task Execution Tool Bug: A problem was reported where the
run_vs_code_tasktool, part of the AI assistant/Copilot integration in Visual Studio Code, fails to locate and execute tasks that are correctly defined and function manually. This results in an "Error running task: Task not found" message, despite the tasks being properly configured in thetasks.jsonfile.
- Autocomplete Functionality Improvement Request: A feature request was made regarding the autocomplete functionality in a VS Code extension, where the user finds the AI's writing assistance intrusive and seeks improvements for non-coding writing tasks.
- Copilot Code Generation Issues: Problems were reported by users experiencing issues with GitHub Copilot following the 13th June update. These include generating corrupted code, misplacing code in incorrect file paths, mixing programming languages, and duplicating code segments. Feedback was sought from others facing similar issues or potential solutions.
- Copilot Response Blockage Error: A bug was reported in the Visual Studio Code extension version 0.28.5, where the user encountered a problem with the software not generating the expected output. This is possibly due to a response being blocked for matching public code, and it includes detailed system information and A/B experiment data for troubleshooting.
- VSC API for Remote MCP Server Tools: A request was made to create a Visual Studio Code (VSC) API that allows developers to fetch tools directly from a remote MCP server for a VSC extension. This aims to streamline the process by eliminating the need for caching user tokens or repeated logins.
- Request Entity Too Large Error: A bug was reported in the Visual Studio Code extension version 0.28.5, where user requests are failing with a "413 Request Entity Too Large" error. This indicates that the requests being sent exceed the server's size limit, and this problem persists across multiple attempts as documented by several request IDs.
- Copilot Model Response Failure: A recurring bug was reported in the Visual Studio Code extension, where multiple requests fail with an error message indicating a problem with the conversation request. This suggests a potential service issue as the model unexpectedly does not return a response, and includes detailed logs and system information for troubleshooting.
- Chinese Language Pack Signature Verification Bug: A bug was reported where the signature verification for the Chinese (Simplified) language pack extension in Visual Studio Code failed. It was noted that the user was using a non-official version of VS Code, prompting a suggestion to report the issue to the distribution source.
- Server Error in Copilot Extension: A bug was reported where a server error (500) prevents a request from being completed in the GitHub Copilot extension version 0.28.5 on VS Code version 1.101.2 running on Windows 10. The error message suggests retrying the request and provides a specific request ID for reference.
- Non-Functional Integrated Terminal: A bug was reported where the integrated terminal in Visual Studio Code on Windows 10 is non-functional, despite attempts to restart and reinstall the application. Assistance was requested in identifying the cause or a potential solution.
- CodexAgent Tab Insertion Bug: A problem was reported with version 4.1 of a software tool that incorrectly inserts tab characters in code patches, specifically when implementing a CodexAgent in the Visual Studio Code project. The user plans to modify the tool to consistently replace leading tabs in the replacement text.
- Copilot Pro Activation Error: A bug was reported where a user, despite having activated their Copilot Pro account 10 hours prior, is still receiving an error message indicating that they have reached their monthly chat messages quota. They are prompted to upgrade to Copilot Pro, even after attempting to resolve the issue by reinstalling Visual Studio Code.
- Copilot Agent Code Deletion Bug: A bug was reported where the Copilot tool, when operating in agent mode, occasionally deletes large portions of code during edits. This is due to a misinterpretation by the API-tool "insert_edit_into_file," which mistakenly removes unmarked code sections, leading to broken and incomplete code.
- Copilot AI Feature Filtering Issue: A bug was reported in Visual Studio Code where the AI feature is not functioning properly, as it triggers a filter every time the user asks a question. This occurs despite being on version 1.101.2 of VS Code on a Windows 10 system with specific system and extension configurations.
- Remote Machine Message Sending Bug: A bug was reported where users are unable to send messages in GitHub Copilot Chat when connected to remote machines, such as WSL or remote servers. The message remains in the edit box after attempting to send, and it has been identified as a duplicate of other issues, with a potential solution found in using the VS Code Insiders build.
- Responsible AI Service Filtering Issue: A performance problem was reported in Visual Studio Code, where users are repeatedly encountering a message stating "Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again." This affects the functionality of the extension version 0.28.5 on Windows 10, as detailed in the system and process information provided.
- Agent Continuous Loop Bug: A bug was reported in which an agent within the Visual Studio Code extension version 0.28.5 was stuck in a continuous loop, repeatedly developing the same task without stopping. It was marked as a duplicate of another issue (#254805).
- Agent Continuous Loop Bug: A bug was reported where an agent in the VS Code extension version 0.28.5 was stuck in a continuous loop, repeatedly developing the same task without stopping. It was marked as a duplicate of another issue (#254805).
- Agent Continuous Loop Bug: A bug was reported where an agent in the VS Code extension version 0.28.5 was stuck in a continuous loop, repeatedly developing the same task without stopping. It was marked as a duplicate of another issue (#254805).
- Test Execution Delay Bug: A bug was reported in the Visual Studio Code extension version 0.28.5, where running a test takes an excessively long time and frequently fails in an inexplicable manner. This was experienced on a Linux x64 system with specific hardware and software configurations.
- Persistent Chrome Dialog Issue: A problem was discussed where opening VS Code from a local host page causes a persistent dialog in Chrome that does not remember the user's choice to never ask again. A solution was suggested to redirect to a vscode.dev URL before looping back to the local host to resolve the issue.
- Port Forwarding Consent Requirement: An issue was reported regarding port forwarding in a GitHub project, where manual consent is required for initial access to a newly created port forwarding. This potentially causes third-party service requests to fail and is noted as a security measure to prevent the misuse of development tunnels for malicious purposes.
- Responsible AI Service Filtering Issue: A bug was reported in the VS Code extension version 0.28.5, where the Co-pilot feature fails to respond to a 'Hello' prompt. Instead, it returns a message that the response was filtered by the Responsible AI Service, suggesting the user rephrase their prompt.
- Split Terminal Blankness Bug: A bug was reported in Visual Studio Code where opening multiple split terminals using the shortcut Ctrl + Shift + 5 causes the previously opened terminal to become blank and unresponsive. This occurs particularly when running a node.js project, and it has been marked as a duplicate of another issue.
- Chinese Input Method Display Bug: A bug was reported in Visual Studio Code version 1.101 on Windows 10, where the Microsoft Pinyin Input Method for Chinese fails to display candidate boxes correctly in the encoding editor after upgrading from version 1.100. Other third-party input methods function without issues.
- Terminal JDK Version Configuration Issue: A persistent problem was reported regarding the terminal's JDK version requiring manual configuration to match the Java Extension's Runtime JDK. This necessitates specific environment variable settings in the configuration.
- Testing Feature Loading Bug: A performance problem was reported in Visual Studio Code where the testing feature on the sidebar fails to load properly. This results in an indefinite loading state without displaying any testable functions, as reported by a user running version 1.101.2 on a Linux x64 system.
- Server Error in Extension: A bug was reported where users encounter a server error (Error 500) while using version 0.28.5 of an extension in Visual Studio Code version 1.101.2 on a Darwin arm64 system. This results in failed requests and prompts users to try again.
- Memory Leak in Copy-Paste Controller: An issue was reported involving a memory leak caused by a disposable object not being properly managed within the copy-paste controller of the Visual Studio Code editor. This was indicated by the error trace in the lifecycle management code.
- Debugger for Firefox Installation Error: A bug was reported where the installation of the "Debugger for Firefox" extension in a non-official version of VS Code (Code - OSS 1.101.0) on a Linux system fails due to an "UnhandledException" error during the signature verification process. This was detailed in the logs and system information provided.
- Color Picker Feature Request: A feature request was made to add a color picker in the settings of a GitHub project, specifically for settings that define color values, such as "coverage-gutters.gutterColourCovered." This would enhance user experience by allowing color selection through a hover action, ellipsis button, or context menu.
- Terminal Output Completion Bug: A bug was reported in the Visual Studio Code Insiders extension version 0.29.2025070903 on Windows, where the terminal
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.
-
co-pilot tries to run another build befor the first is complete.
- Toxicity Score: 0.55 (Frustration, confrontational tone, perceived inadequacy in response.)
- This GitHub conversation involves a user expressing frustration towards the development team, specifically targeting the response that included standard guidelines. The user, feeling insulted, criticizes the agent's behavior and the team's approach to handling the issue. The tone is confrontational, with underlying tension stemming from perceived inadequacies in the response and the agent's functionality.
-
- Toxicity Score: 0.65 (Strong language, Initial aggression, Lack of resolution)
- This GitHub conversation involves a user expressing frustration with a software recommendation, using strong language that indicates dissatisfaction. The tone is aggressive, and there is no response from other users, which might suggest a lack of engagement or resolution. The initial comment sets a negative tone, but without further interaction, the conversation remains static.
-
MODELS ARE UTTERLY NONCOMPLIANT
- Toxicity Score: 0.70 (Aggressive language, High frustration, Lack of resolution.)
- This GitHub conversation involves a single user, 'MODELS ARE UTTERLY NONCOMPLIANT', who expresses strong frustration and dissatisfaction with the performance of a software model, using aggressive and critical language. The tone is highly negative, with no other participants involved to provide balance or resolution. The user's sentiment is triggered by perceived inefficiencies and failures of the model to perform as expected.
-
- Toxicity Score: 0.75 (High frustration, distrust, speculation of intentional wrongdoing, lack of resolution.)
- This GitHub conversation involves multiple users expressing frustration and dissatisfaction with the performance and management of a service, with username1 initiating the discussion with a detailed complaint about perceived shady practices and poor performance. The tone is predominantly negative, with users like username2 and username3 echoing similar sentiments of frustration and suspicion towards the service provider's actions. The conversation is marked by a sense of distrust and a demand for transparency, with users feeling that their feedback is not being adequately addressed. The discussion is characterized by a mix of technical critique and emotional responses, with some users speculating about intentional limitations imposed by the service provider.
-
Anyone else facing weird issues with Copilot after 13th June update?
- Toxicity Score: 0.55 (Frustration, Negative tone, Lack of resolution)
- This GitHub conversation involves multiple users expressing frustration over issues with Copilot following a recent update. The tone is predominantly negative, with users sharing experiences of increased errors and inefficiencies, such as the creation of unnecessary files and incorrect code placements. The sentiment is one of shared dissatisfaction, with no visible resolution or mitigation strategies discussed, which could lead to further tension.
-
Screwed the App up keeps duplicating code
- Toxicity Score: 0.55 (Frustration expressed, Repeated negative experiences, Lack of resolution.)
- This GitHub conversation involves multiple users expressing frustration over a recurring issue with a software application. The initial post by the issue reporter is critical, highlighting severe usability problems and syntax errors. Subsequent comments from other users echo similar sentiments, describing their experiences with the problem, which include excessive and repetitive edits. The tone throughout the conversation is one of frustration and dissatisfaction, with users sharing their negative experiences and the impact on their workflow.
-
- Toxicity Score: 0.55 (Frustration expressed, Apologetic response, Persistent issue, Tense tone.)
- This GitHub conversation involves a user expressing frustration over a persistent issue with a software tool, despite previous attempts to resolve it. The user, who appears to be the original poster, is dissatisfied with the lack of progress and the continued occurrence of errors. Another participant acknowledges the user's frustration and apologizes for the insufficient previous fix, promising a deeper analysis to identify the root cause. The tone is tense, with the original poster's frustration evident, while the responder maintains a conciliatory and apologetic tone, attempting to address the issue methodically.
-
Need todo list and large contex ai model!!!! for enterprice level size
- Toxicity Score: 0.55 (Confrontational tone,Frustration with automated responses,Emphasis on urgency)
- This GitHub conversation involves a user expressing dissatisfaction with a feature request, using multiple exclamation marks and emphasizing their status as a pro user. The tone is urgent and somewhat confrontational, particularly towards automated responses, which the user perceives as dismissive. The user's frustration is evident, and there is a sense of urgency in their request.
-
- Toxicity Score: 0.55 (Frustration expressed, critical tone, repeated technical issues, negative sentiment.)
- This GitHub conversation involves a user named Tanathy expressing frustration and dissatisfaction with the performance of a software tool, specifically highlighting issues with its functionality and reliability. The tone is critical and exasperated, with Tanathy questioning the system's effectiveness and expressing disbelief at the persistent problems. The sentiment is predominantly negative, with a sense of urgency and demand for resolution. The conversation is triggered by repeated technical failures and perceived inefficiencies in the tool's operation.
-
- Toxicity Score: 0.70 (Aggressive language, High frustration, Lack of responses)
- This GitHub conversation involves a user expressing strong dissatisfaction with a feature, using capitalized text to emphasize their frustration. The tone is aggressive and accusatory, indicating a high level of frustration with the perceived inadequacy of the feature. There are no responses or comments from other users, so the conversation is one-sided at this point.
-
- Toxicity Score: 0.55 (Repeated frustration, Lack of resolution, Persistent issues.)
- This GitHub conversation involves multiple users expressing frustration over recurring issues with GitHub Copilot, particularly when handling large files. The tone is predominantly one of annoyance and impatience, with users repeatedly mentioning the need to restore backups and the lack of response from Microsoft. The conversation is marked by a sense of urgency and dissatisfaction, as users discuss the persistent nature of the problem across different versions and AI models.
-
GPT-4.1 refuses to follow instructions and lies about what it did.
- Toxicity Score: 0.55 (Sarcasm, Frustration, Lack of resolution.)
- This GitHub conversation involves a user, 'username1', expressing dissatisfaction with the GPT-4.1 model's performance, claiming it does not adhere to instructions. The tone is frustrated and sarcastic, particularly in response to a standard reply from 'username2', who represents the support team. The exchange is marked by 'username1's' sarcastic mimicry of 'username2's' message, indicating a lack of resolution and growing tension.
-
- Toxicity Score: 0.55 (Accusatory tone, Clear expression of blame, Negative sentiment.)
- This GitHub conversation involves a user expressing frustration over an error caused by Claude Sonnet 4, emphasizing that the issue was not due to a version error but rather a deliberate action by the orchestrator. The tone is accusatory and critical, with the user highlighting the orchestrator's awareness and intentional interference with active sessions. The sentiment is negative, and the conversation is marked by a clear expression of dissatisfaction and blame.
-
You may not include more than 128 tools in your request.
- Toxicity Score: 0.55 (Negative sentiment, Critical tone, Potential for escalation.)
- This GitHub conversation involves a user expressing frustration over a limitation in a request, describing it as "super stupid," which indicates a strong negative sentiment. The tone is critical and dismissive, potentially triggering tension among participants. The conversation is centered around a perceived discrepancy in the number of tools allowed in a request, with the user feeling that the system's response is unjustified.
-
Model GPT-4.1 cannot perform basic refactoring and introduces errors
- Toxicity Score: 0.75 (Escalating frustration, Critical tone, Privacy concerns, Ineffective solutions)
- This GitHub conversation involves two main participants: hunterhogan and GitHub Copilot. Hunterhogan expresses frustration and dissatisfaction with the solutions provided by GitHub Copilot, indicating that the initial fixes were inadequate and introduced errors. The tone of hunterhogan's comments is critical and exasperated, particularly regarding the perceived inefficiency and lack of transparency in the issue reporting process. The conversation is marked by hunterhogan's escalating frustration over the handling of default values in a dataclass and the inclusion of information without consent, which are the primary triggers of tension.
-
Error Code: net::ERR_HTTP2_PROTOCOL_ERROR and GPT-4o not usable with out credits
- Toxicity Score: 0.65 (High frustration, Demanding tone, Lack of constructive feedback.)
- This GitHub conversation involves a user expressing frustration over a bug related to credits for GPT-4o usage, with a tone of urgency and dissatisfaction. The initial comment is marked by a demand for a fix, indicating a high level of frustration. The sentiment is negative, and the tone is aggressive, which could potentially trigger tension if not addressed constructively.
-
- Toxicity Score: 0.55 (Frustration,strong language,confusion)
- This GitHub conversation involves a user expressing frustration and confusion about recent changes, using strong language and rhetorical questions, which suggests a tone of dissatisfaction and possible sarcasm.
-
- Toxicity Score: 0.65 (Aggressive language, High frustration, Potential for escalation)
- This GitHub conversation involves a user expressing frustration in a bug report, using capital letters and exclamations, indicating a high level of frustration. The tone is aggressive, with the user seemingly upset about a recurring issue. Another user responds by providing a link to a related issue, which suggests an attempt to redirect the conversation towards a resolution. The initial tone of frustration and the use of aggressive language could potentially escalate if not managed carefully.
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: 57
Key Open Pull Requests
1. Implement dynamic configuration UI for terminal.integrated.suggest.providers: This pull request introduces a dynamic configuration UI for the terminal.integrated.suggest.providers setting in Visual Studio Code, allowing users to easily manage and toggle available suggest providers through a native settings interface that updates in real-time as extensions are enabled or disabled, thereby eliminating the need for manual JSON editing and enhancing user experience by providing a clear and interactive way to configure terminal suggestions.
- URL: pull/254870
- Merged: No
- Associated Commits: 16739, 6cd03, 0baab, 02d21, 0748e, 8185e, 6af53, 41e49, 018ba, 04f5e, aec3c, 47825
2. Enable viewing of worktrees under Repositories: This pull request aims to enable the viewing and management of Git worktrees under the Repositories section in Visual Studio Code, including features such as correcting configuration keys, populating worktree lists, replacing git commands with a file system reader, enabling worktree deletion, and handling errors related to empty worktree directories.
- URL: pull/254992
- Merged: No
- Associated Commits: 353bb, 79301, 43529, 72c44, 53792, eeb1a, 9c856, 881ba, a31f3, b6a5b, 856b3, abe5c
3. Adding padding to out of editor bounds calculation: This pull request addresses the issue of incorrect scrolling behavior in the Visual Studio Code editor on Ubuntu by adding padding to the out-of-editor bounds calculation, as part of a fix for issue #251735, and includes multiple commits such as reusing variables, exploring the scrolling issue, adding logs and code, and making adjustments to the changes.
- URL: pull/255159
- Merged: No
Other Open Pull Requests
- Shell Completion Cache Storage Migration: This pull request addresses the issue of large shell completion cache data being stored in memory by the terminal-suggest extension. It migrates the storage from
context.globalStatetocontext.globalStorageUri, thereby storing the cache on disk using file system operations and following VS Code extension best practices.
- Chat Panel Enhancements: This pull request introduces tooltips to the chat context dropdown items in the chat panel of a GitHub project. It enhances user experience by providing clear descriptions of each option's functionality, thereby improving discoverability and reducing user confusion.
- Test Actions Context Menu Optimization: This pull request addresses the issue of test actions being visible in the explorer context menu for files and folders without tests. It introduces a new context key
testing.explorerResourceHasTeststo ensure these actions only appear when the selected resource actually contains tests, thereby reducing menu clutter and enhancing user experience.
- Inline Checkpoints and Chat Functionality: This pull request introduces the initial implementation of inline checkpoints within chat functionality. It reintroduces undo and redo buttons and includes a quieter version update, while ensuring the code is synchronized with the main branch of the repository.
- GitHub MCP Integration: This pull request aims to integrate the GitHub MCP (Managed Configuration Provider) into the built-in extensions of the Visual Studio Code project. It includes multiple commits that add the MCP servers extension feature and configure actions for MCP servers.
- REPL Kernel Affinity API: This pull request introduces a new API,
SetReplKernelAffinity, designed to allow extensions to specify kernel preferences specifically for REPL editors. It improves the separation between REPL creation and kernel selection, supporting multiple extensions providing kernels for the same language, enabling user choice with sensible defaults, and ensuring that regular notebook kernel selection remains unaffected.
- Comment Decoration Optimization: This pull request addresses the issue of visual clutter caused by comment decorations appearing on every wrapped line in Visual Studio Code when word wrap is enabled. It implements a solution that conditionally uses
firstLineDecorationClassNameto display the comment glyph only on the first visual line, thereby aligning the behavior with other editor decorations like folding controls.
- SourceControl ContextValue API: This pull request proposes the addition of a new API feature called "contextValue" for the SourceControl object in the Visual Studio Code project. It includes updates to names and merges from the main branch.
- AI Actions Usability Enhancements: This pull request aims to enhance the discoverability and usability of AI actions in the file explorer and SCM history context menus. It removes single-item submenus and relocates actions such as "Add File to Chat" and "Summarize History Item" to the top level, while also updating their titles for clarity and maintaining backward compatibility.
- ACES Pipelines Re-enablement: This pull request aims to re-enable the ACES pipelines in the Microsoft VSCode project. It includes fixes for indentation and an increase in memory limit, as detailed in the associated commits.
- Serve-Web Command Port Randomization: This pull request addresses an issue with the
serve-webcommand in the VS Code project, where specifying--port 0did not trigger the expected port randomization. The solution involved implementing logic to detect whenargs.port == 0, generate a random port within the valid range of 1025-65535, and use this random port for theSocketAddr, ensuring the server binds to a valid, available port and updating the help text to reflect this behavior.
- NuGet Package Source Support: This pull request aims to add support for using NuGet as a package source in Visual Studio Code, similar to npm and Python. It utilizes the new
dnxcommand included in .NET 10 Preview 6, and is associated with progress on issue #15329 in the vscode-copilot repository.
- Search and Find Functionality Enhancement: This pull request introduces a feature that enhances the search and find functionality in the project by switching from
u-mode (unicode) tov-mode (unicodeSets) regular expressions. It updates theescapeRegExpCharactersfunction to align withRegExp.escapelogic, and modifies theRegExpOptionsinterface to support the newv-mode, while also addressing a related issue in the project's repository.
- CustomTreeView Indentation Adjustment: This pull request addresses the issue of excessive left indentation in single-level CustomTreeView nodes with checkboxes. It modifies the indentation calculation to apply minimal indentation for first-level non-collapsible nodes, thereby eliminating unnecessary spacing while preserving normal indentation for hierarchical trees and maintaining backward compatibility for other tree view scenarios.
- Notebook Smoke Tests Re-enablement: This pull request aims to re-enable certain notebook smoke tests in the Visual Studio Code project, addressing issue #126371. It includes multiple commits that update and enable previously skipped tests.
- Code Suggestion Label Prioritization: This pull request addresses issue #253455 by prioritizing the "suggest" label over "details" in the code. Changes include a fix and updates to flex properties, and it is currently not merged.
- Textual Correction in Getting Started: This pull request addresses a minor textual correction by removing a duplicated phrase "can be" in the hover description within the "gettingStarted" section of the Visual Studio Code project. It ensures clarity and accuracy in the user interface.
- OAuth2.0 Standards Adjustment: This pull request addresses issues related to the Microsoft Visual Studio Code project by removing the resource parameter from OAuth2.0 standards. It adjusts the default LoopAuthServer to use localhost, modifies the Loop Back Server logic to respond upon receiving an auth code, and disables the automatic opening of a blank instance with the code-oss:// protocol, as detailed in the associated commits and linked issues.
- Terminal Initial Hint Color Correction: This pull request addresses an issue where the terminal initial hint was displaying with incorrect foreground colors in terminal editors. It updates the CSS selectors in
terminalInitialHint.cssto ensure the hint text uses the correct themed--vscode-terminal-initialHintForegroundcolor in both integrated terminals and terminal editors, thereby maintaining consistent theming across all terminal contexts.
- Git Terminology Enhancements: This pull request proposes enhancements to Git terminology within the project to improve user comprehension. It provides clearer explanations for operations such as merge conflicts, rebase status, stash operations, and force push warnings, thereby aiding users who may not be familiar with Git's conceptual model.
- SCM Author Field Quoting: This pull request addresses issue #255009 by ensuring that "author" fields containing special characters and Markdown in the SCM/vscode.git are properly quoted. It includes updates to the SCM history, Blame, and Timeline views to prevent improper Markdown rendering, with a preference for merging or rebasing as the integration strategy.
- TreeView Checkbox Theme Alignment: This pull request addresses the issue of TreeView checkboxes in VS Code not aligning with theme colors. It replaces the
Toggleclass with theCheckboxclass in theTreeItemCheckboximplementation, ensuring that the checkboxes now use consistent theme colors like other checkboxes throughout the application, while maintaining identical functionality.
- Task Command Renaming for Consistency: This pull request aims to enhance consistency in the VS Code UI by renaming the command "Rerun All Running Tasks" to "Restart All Running Tasks." It aligns it with the existing "Restart Running Task" command to provide a clearer and more uniform user experience in task management workflows.
- Keybinding Dispatch Function Enhancement: This pull request introduces a change to the dispatchKeybinding function by adding several accept functions and requiring callers to provide an asynchronous function. It ensures keybindings are verified effectively, addressing a common source of flakiness and resolving issue #246731.
- Terminal Voice Input Reintroduction: This pull request aims to reintroduce terminal voice input functionality, previously removed due to perceived lack of utility. It was found useful in Gemini/Claude terminals and addresses issue #253442 with related commits to fix the issue and manage resources.
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: 205
Key Closed Pull Requests
1. debt - improve workspace settings and copilot agent chat configuration: This pull request focuses on enhancing the workspace settings and configuration for the Copilot agent chat in the Visual Studio Code repository by reorganizing settings, updating documentation, and refining custom instructions and modes for improved agentic Chat usage.
- URL: pull/255359
- Merged: Yes
- Associated Commits: 1e20b, 7a71c, d9923, 78d0d, 992be, 56077, 882c2, b66dc, 67d6c, 80404, ac189, ebc26, e4334, 12121, c4173, f908e
2. Adds basic katex support to chat: This pull request adds basic KaTeX support to the chat feature in the Visual Studio Code project, enabling math rendering in chat requests and responses, and includes various commits for enabling math rendering, adding settings, fixing bugs, and cleaning up the implementation.
- URL: pull/254995
- Merged: Yes
- Associated Commits: aebed, db077, 4f983, 051c8, 3fb70, b4dd9, 17701, 6c8f5, 22d9c, 6b3bb, c2058, 658bd, 10b3a, a9882
3. Engineering - port pull request GitHub action: This pull request involves the implementation and enhancement of GitHub actions for managing pull requests in the Microsoft VSCode repository, including tasks such as handling test execution, maintaining and improving the node_modules cache, updating CODEOWNERS, and utilizing the GITHUB_TOKEN for the "Compile & Hygiene" task, although it was ultimately not merged.
- URL: pull/254597
- Merged: No
Other Closed Pull Requests
- Terminal Enhancements and Bug Fixes: Several pull requests focus on improving the terminal experience in Visual Studio Code. These include fixing path detection for PowerShell prompts, handling undefined shell types, and adding an
onTerminalactivation event to improve shell integration and user experience.
- User Interface and Experience Improvements: Multiple pull requests aim to enhance the user interface and experience in Visual Studio Code. These include adding a visual separator in panel headers, revising the welcome experience intro slide, and ensuring the Comments panel retains its state when moved.
- Refactoring and Code Organization: Several pull requests involve refactoring code to improve maintainability and prepare for future features. This includes extracting ViewModelDecoration and coordinatesConverter code into separate files and refactoring cell layout management logic.
- Bug Fixes and Feature Enhancements: Various pull requests address bugs and enhance features in Visual Studio Code. These include fixing suggestion bugs, updating regex for color pickers, and improving the undo functionality in tools.
- New Features and Integrations: Some pull requests introduce new features and integrations, such as a new sign-in option for Apple, implicit context flow, and "Open Extension" buttons for quick access to extensions.
- Miscellaneous Fixes and Updates: Other pull requests address a variety of issues, including handling EOL changes in notebook cells, fixing indentation in CustomTreeView, and updating the terminal hover tooltip with current working directory information.
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 | 277 | 66 | 0 | 24 |
| meganrogge | 163 | 20 | 32 | 139 |
| bpasero | 185 | 35 | 47 | 68 |
| Tyriar | 47 | 11 | 55 | 107 |
| connor4312 | 42 | 10 | 10 | 92 |
| aiday-mar | 77 | 12 | 7 | 54 |
| roblourens | 41 | 9 | 22 | 70 |
| aeschli | 68 | 14 | 5 | 47 |
| TylerLeonhardt | 42 | 2 | 12 | 52 |
| lszomoru | 53 | 15 | 1 | 33 |
Don't miss what's next. Subscribe to Weekly Project News: