Weekly GitHub Report for Vscode: April 06, 2026 - April 13, 2026 (19:28:12)
Weekly GitHub Report for Vscode
Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.
Table of Contents
I. News
1.1 Recent Version Releases:
The current version of this repository is 1.98.2
1.2 Version Information:
The version released on March 12, 2025, primarily focuses on resolving various issues as detailed in the linked GitHub milestone for "February 2025 Recovery 2." For a comprehensive overview of all updates and improvements, users are directed to the official release notes on the Visual Studio Code website.
II. Issues
2.1 Top 5 Active Issues:
We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.
-
[INFO-NEEDED] [WINDOWS] Integrated terminal duplicates output after switching VS Code windows (intermittent): This issue describes a bug in the VS Code integrated terminal where output logs are intermittently duplicated multiple times after switching between VS Code windows, particularly after the script execution has completed. The duplication appears to be related to terminal resizing or reflow events, causing the terminal to re-render previous output incorrectly, which significantly impacts log readability and debugging.
- The comments discuss attempts to clarify the issue, with one user identifying terminal resizing as a consistent trigger for the duplication, suggesting a problem with how the terminal handles redraws or buffer state. Others inquire about configuration settings and whether the issue reproduces in other terminals, with shared video evidence supporting the bug’s persistence and suspected relation to the Windows conpty subsystem.
- Number of comments this week: 7
-
[INFO-NEEDED] Unable to input Chinese characters: This issue reports a bug where the user is unable to input Chinese characters in any input field within VS Code, including the editor, search box, terminal, and chat input, with the characters being underlined but no candidate characters appearing. The user is on Windows 10 using the system input method, and the problem also occurs in the Command Palette, indicating a widespread input failure across the application.
- The comments include requests for more detailed information about where the input fails and which IME is used, followed by the user confirming the issue occurs everywhere with the Windows 10 system input method; screenshots were shared showing the problem, and it was confirmed that the issue also affects the Command Palette input.
- Number of comments this week: 7
-
'Add Models...' button in GitHub Copilot Chat is disabled ("greyed out"): This issue reports that the "Add Models..." button in the GitHub Copilot Chat extension for VS Code is disabled, preventing users from managing language models as expected. The problem appears linked to enterprise policy settings that disable custom models, and even after enabling them at the enterprise level, the button remains inactive without clear explanation.
- The comments reveal that the button is disabled due to enterprise policy restrictions on custom models, confirmed by a team member; however, even after these restrictions were lifted, users still experience the button being disabled, with additional reports indicating that Copilot Business accounts face similar limitations when trying to run local AI models.
- Number of comments this week: 6
-
[TERMINAL-RENDERING] Black background after space in terminal: This issue describes a problem where the terminal in VS Code shows a black background after typing a space, making it difficult to write. The user has tried multiple themes, disabled extensions, reinstalled previous versions, and checked various settings without resolving the issue, which persists across different projects and terminal shells except for Command Prompt and Git Bash.
- The comments include requests to reattach the gif demonstrating the issue, inquiries about theme and terminal settings, and detailed user troubleshooting steps such as testing different themes, disabling extensions, reinstalling VS Code, and verifying shell configurations, all confirming the problem remains unresolved.
- Number of comments this week: 6
-
[BUG] [CHAT-TERMINAL] ERROR while calling tool: The terminal was closed Please check your input and try again.: This issue reports an error occurring when calling a tool due to the terminal being unexpectedly closed, accompanied by false positives in input detection and a non-functional "focus terminal" command. The user suspects terminal crashes and provides logs indicating that a previous VS Code session did not properly detach from the terminal, likely due to a crash or forceful shutdown, causing the terminal to be in a bad state when reused.
- The comments discuss a probable fix for bad output detection, analyze logs revealing an orphaned process from a crashed session, confirm the issue relates to window crashes, and suggest improving resilience by creating a new terminal when such cases are detected.
- Number of comments this week: 6
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.
As of our latest update, there are no stale issues for the project this week.
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: 525
Summarized Issues:
- Authentication and Session Issues: Multiple issues describe problems with authentication persistence, session management, and token errors in Copilot and Agents apps. Users face repeated sign-in prompts, session timeouts, token expiration errors, and failures to maintain or restore chat sessions, causing disruptions in workflow and access to features.
- Chat and Agent Responsiveness Problems: Several reports highlight that Copilot Chat and Agents app become unresponsive, enter endless loops, or freeze during use. These issues include infinite working loops, failure to publish messages, and chat windows freezing or failing to load, severely impacting usability.
- Terminal and Async Terminal Issues: Problems with the integrated terminal and async terminal include unreadable text, unexpected headers, crashes, and incompatibility with execution subagents. Users report black backgrounds, duplicated output logs, and terminal sessions not resuming properly, affecting command execution and debugging.
- UI and UX Inconsistencies and Bugs: Multiple issues describe UI problems such as flickering input buttons, broken dropdowns, missing visual indicators, and confusing or broken user interface elements. These include problems with chat input flicker, session duplication, disabled buttons, and inconsistent session icons causing user confusion.
- Performance and Freezing Issues: Users report severe performance degradation, including high CPU usage, freezing, and slow response times in VS Code when using Copilot or Agents. These issues cause the editor to become unusable, with frequent crashes and delays in processing requests.
- Model and API Errors: Several issues describe errors related to model selection, unsupported parameters, and API request failures including 400 and 413 errors. These cause requests to fail, degrade response quality, or prevent model usage, impacting AI-assisted coding workflows.
- Extension and Installation Problems: Users face issues with extension signature verification failures, disabled features, and installation problems across platforms. These include extensions becoming unresponsive, failing to update, or being disabled due to signature errors, as well as problems with installing or uninstalling extensions.
- Agent and Session Management Features: Requests and bugs related to session management include inability to persist custom agent selections, duplicate sessions, lack of session sorting, and missing features like session forking or saving. These issues affect workflow continuity and session organization.
- Feature Requests for UI and Workflow Improvements: Users request enhancements such as adding tabs for active chat sessions, visual indicators for approvals, grouping tabs, voice conversation mode, and better artifact management. These aim to improve usability, efficiency, and accessibility in the Agents app and Copilot Chat.
- File and Workspace Handling Issues: Problems include incorrect file path handling, inability to open or delete files properly, issues with worktree visibility, and problems with workspace trust state synchronization. These affect file navigation, version control integration, and workspace management.
- Network and Connectivity Errors: Several issues report network errors, timeouts, and connection closures affecting Copilot and Agents functionality. These errors cause failed requests, lost sessions, and degraded user experience despite stable internet connections.
- Security and Privacy Concerns: A security vulnerability is reported where malicious tasks can execute arbitrary shell commands silently on repository open, enabling zero-click remote code execution without user consent. Additionally, concerns about unauthorized file access by Copilot agents are raised.
- Localization and Input Method Issues: Problems with keyboard input, such as Japanese keyboard input errors, inability to input Chinese characters, and incorrect language responses from Copilot, affect international users and input accuracy.
- Bug Reports Lacking Details or Templates: Numerous reports are templates or lack sufficient information, making diagnosis or resolution difficult. These include generic error reports, incomplete reproduction steps, or placeholders without actionable data.
- Miscellaneous Bugs and Feature Requests: Various other issues cover a wide range of smaller bugs and feature requests including color theme contrast improvements, debug toolbar customization, clickable buttons for suggested tasks, and improved error messaging.
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: 506
Summarized Issues:
- Copilot Chat UI and Interaction Bugs: Multiple issues describe problems with Copilot Chat's UI and interaction, including incorrect status reporting of TODO lists, inability to change agent type or chat mode due to dropdown malfunction, repeated prompts for user confirmation without task progress, and chat windows not displaying commands properly or disappearing. These bugs cause confusion, prevent mode selection, and disrupt user workflow by making chat features unreliable or unresponsive.
- Agent and Extension Stuck or Unresponsive States: Several reports indicate that agents or extensions become stuck in "working" or "loading" states, fail to respond to commands, or enter infinite loops, causing users to lose progress or requiring restarts. These issues affect multiple extension versions and platforms, leading to token consumption without output and repeated failures in task execution.
- Terminal and Integrated Terminal Issues: Users report multiple terminal-related problems including inability to paste images via keyboard shortcuts, terminal command line refreshing infinitely, terminal output clipping, slow or heavy terminal performance, terminal crashes on script execution, and issues with terminal input being misdirected or causing repeated prompts. These issues degrade terminal usability and cause workflow interruptions.
- Performance and Lag Problems: Multiple issues describe severe lag, unresponsiveness, or slowdowns in VS Code and its extensions, including Remote SSH lag, UI lag when opening Jupyter notebooks on CIFS/SMB mounts, high CPU usage by ripgrep, and general application freezes or slow loading times. These performance degradations significantly impact user productivity and system responsiveness.
- Session and Chat History Data Loss or Corruption: Several reports highlight issues where chat histories or session data disappear, become unrecoverable, or fail to serialize properly, often due to errors like invalid string length during JSON.stringify operations. This results in loss of user work and frustration due to inability to recover past conversations or session states.
- Agent Command and Tool Invocation Failures: Users experience problems with agents failing to execute commands properly, including commands not showing in chat responses, failed merges in Sessions, inability to delegate tasks to Copilot CLI, and agents running tasks in wrong repositories or failing to locate pull requests. These issues disrupt automated workflows and reduce trust in agent functionality.
- Model and API Errors: Multiple issues report errors related to AI models, including unsupported models, API access failures, hallucinated completions, and errors caused by invalid parameters or organization policy restrictions. These problems cause failures in code generation, chat responses, and model availability.
- UI and Layout Problems: Several issues describe UI glitches such as misaligned text, flickering buttons, misplaced controls, incorrect padding, and problems with modal window sizing or theme synchronization. These issues affect usability and visual consistency in VS Code and its extensions.
- Extension Installation and Configuration Issues: Users report problems with extension installation paths, lost custom syntax coloring after updates, inability to disable inline suggestions, and issues with tool approval management UI, complicating extension management and customization.
- Authentication and Access Problems: Some users face issues with signing out, authorization failures, or inability to access Azure tenant subscriptions or Claude extension, leading to blocked features and disrupted workflows.
- Feature Requests and Usability Improvements: Requests include adding clickable links to workspace symbols in Copilot Chat, voice selection options, collapsing file list sidebar in diff modal, and better keyboard navigation and accessibility support in the Agents app. These aim to enhance navigation, customization, and accessibility.
- Crash and Stability Issues: Reports include frequent VS Code crashes, extension crashes, and runtime errors without clear reproduction steps, causing loss of work and requiring restarts.
- Code Generation and Formatting Bugs: Issues include code snippets disappearing, incomplete or truncated code blocks, incorrect code insertion, and formatting errors in generated code, negatively impacting code quality and user trust.
- Miscellaneous Bugs and Reports: Various other issues include problems with keyboard shortcuts, workspace folder display, agent tool manifest inconsistencies, and unexpected behavior in specific workflows or extensions.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
Copilot diff is broken and unreadable on a single file.
- Toxicity Score: 0.75 (Rapid escalation, dismissive language, personal attacks)
- This GitHub conversation begins with a user reporting an issue and another participant quickly labeling it as a duplicate. The original poster questions the duplicate claim, leading to a dismissive and accusatory response targeting the new user's experience on GitHub and implying spamming behavior. The tone shifts from neutral to confrontational, with tension triggered by the perceived invalidation of the original report and personal remarks about the user's account age.
-
I feel the 10$ plan hallucinates less than the 40$ plan!!
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, emotional outbursts)
- This GitHub conversation involves a user expressing strong dissatisfaction with a service, followed by other participants contributing comments that reflect frustration and blame towards the software and its components. The tone escalates from critical to highly emotional and accusatory, with the original poster and commenters venting about significant negative experiences and losses. The tension is triggered by perceived failures of the product and the impact on the user's work, leading to a breakdown in constructive dialogue.
-
keep losing all extensions and config settings you fucking assholes
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, unresolved frustration)
- This GitHub conversation features a single user expressing intense frustration and anger through aggressive language and profanity, triggered by repeated loss of settings and configurations. The tone is highly emotional and confrontational, with no responses or attempts at resolution visible in the thread. The lack of engagement from others leaves the conversation one-sided and unresolved.
-
- Toxicity Score: 0.65 (Rapid escalation, disruptive comment, dismissive tone)
- This GitHub conversation involves a user submitting a feature request with detailed environment information, followed by a single comment containing a spam command, which likely triggered the issue being labeled as invalid. The tone is neutral in the initial post but shifts to dismissive or disruptive due to the spam comment, causing a breakdown in constructive dialogue.
-
- Toxicity Score: 0.65 (Rapid escalation, disruptive comment, dismissive tone)
- This GitHub conversation involves a user submitting a bug report with detailed system information, followed by a single comment containing a spam-like message. The tone shifts from neutral and technical in the initial post to dismissive or disruptive in the comment. The presence of a spam comment triggers tension, leading to the issue being labeled as invalid and requiring triage.
-
don't give the reference of code. This is really bad for coders who are in begineer phase.
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, profanity, emotional outburst)
- This GitHub conversation involves a user expressing strong frustration and dissatisfaction with a recent update, using aggressive and profane language to emphasize their negative sentiment. The tone is highly emotional and confrontational, with the user clearly upset about the impact on beginners. The initial comment triggers tension due to its harsh wording and explicit criticism, but there are no recorded responses or attempts at de-escalation in the provided data.
-
- Toxicity Score: 0.65 (Rapid escalation, dismissive tone, spam-like content)
- This GitHub conversation involves a single user posting a message that appears to be nonsensical or spam-like, followed by a comment that simply states "/spam". The tone is dismissive and unconstructive, with no meaningful engagement or resolution attempts. The interaction is brief and lacks collaborative or problem-solving elements, which could potentially trigger frustration or negative responses if the conversation were to continue.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, threats, initial hostility)
- This GitHub conversation begins with a highly aggressive and frustrated user posting a hostile and threatening message. A community member responds calmly, directing the user to follow the code of conduct and to open a new issue with clear symptoms for assistance. Another user expresses confusion about the situation, indicating a lack of clarity and escalating tension due to the initial outburst. The tone shifts from hostile to neutral and procedural, with no further escalation observed.
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: 172
Key Open Pull Requests
1. FindWidget/TerminalFindWidget: Provide random access to search matches via an inline "Nth Match" input field. : This pull request introduces an inline "Nth Match" input field to the findWidget and terminalFindWidget components, enabling users to jump directly to any specific search match for more efficient navigation through large sets of results, with corresponding updates to both the UI and underlying functionality, including integration with the terminal editor via the upstream xterm.js dependency.
- URL: pull/309109
- Associated Commits: 90dc3, 32eee, 622de, ceda7, 7da80, f2728, 119f8, d366c, 9c2c3, 11d59, e607e, ee61f, fd67d, ee803
2. agentHost: Restore selected model across sessions: This pull request restores the selected model across agent-host session surfaces by propagating model metadata through backend session summaries, websocket list responses, session providers, and chat history, ensuring that model state is managed by sessions/providers rather than the picker, and includes comprehensive unit and integration tests to validate these changes.
- URL: pull/309331
- Associated Commits: 5a3a2, 8f27b, e353d, e9984, 28421, f4749, d4f79, 0bf61, 319b9, 8f766, 59dfd, 80766, e93db, c3481
3. Abadawi/send has image to router: This pull request updates the client-side routing logic to delegate image presence handling to the server-side auto-intent-service by removing the client-side early return for hasImage and instead sending has_image: true in router requests when images are present, while also enhancing error handling, telemetry, and tests related to vision model fallbacks and router decision errors.
- URL: pull/308321
- Associated Commits: 155c2, a55ff, 9b084, 75af0, 24c33, 4ad55, d9a91, 7bff5, 895f6, 3f8e4, b369d, 6615f, b2eee
Other Open Pull Requests
- Agent Sessions and Agents App Enhancements: Multiple pull requests improve the Agent Sessions experience by adding session configuration support, a responsive mobile-compatible PWA layout, and updating the titlebar to show the signed-in user's GitHub avatar. Additionally, a welcome page banner promotes the new Agents app with telemetry and styling for user engagement.
- Memory Leak Fixes and Telemetry Improvements: Several pull requests address memory leaks in the chat widget rendering pipeline by adding proper cleanup and null guards, and enrich telemetry for listener leak errors by adding new fields to error classes for better leak detection and GDPR-compliant logging.
- Chat and Endpoint Performance Optimizations: Pull requests fix a race condition in the
resolveAutoModeEndpointfunction by implementing promise coalescing to reduce duplicate telemetry and token fetches, and refactor the tool-calling loop to resolve the chat endpoint once per round, improving efficiency and reducing redundant calls.
- Copilot Extension and CLI Updates: Updates to the Copilot extension include using core vscode type definitions for better integration and enhancing the Copilot CLI with per-model chat configuration, session handling refactor, and related test fixes.
- Security and Secret Storage on macOS: A pull request implements a shared keychain service on macOS for secure token sharing between Code editor and embedded Agents app, refactors secret storage with lazy migration, and configures product-specific keychain access with entitlement-based detection.
- Terminal and Source Control Enhancements: New terminal tab management features include keyboard commands for reordering tabs and a context menu to kill terminal groups below the active one, while the Source Control pane gains automatic sorting of repositories by most recent changes for better visibility.
- Installer and Update UI Improvements: A pull request prevents the installer UI from launching during automated background update and restart scenarios on Windows by protecting code paths that could cause race conditions.
- Node Executable Resolution and TypeScript Fixes: The synchronous subprocess waits in TypeScript node path resolution are removed and replaced with a cross-platform function to resolve the Node executable from the system PATH, including helper functions and unit tests while preserving existing warnings.
- Localization and Accessibility Fixes: Fixes include correcting typos and improving localization translator hints, as well as enhancing keyboard accessibility for the "Select a language" action in the empty editor hint by adding tabindex and focus styling.
- Performance Improvements in Chat Rendering: Caching chat progress content parts reduces trace duration, heap usage, and garbage collection overhead in the VSCode renderer, significantly improving performance.
- Chronicle Feature for VSCode Events Storage: A new feature called "Chronicle" implements local and remote storage for VSCode events, including uploading events to a cloud store, adding user consent UI and settings, and various optimizations and fixes.
- Operator-Agent Extension Introduction: The new
operator-agentextension provides a bounded execution controller for privileged workspace operations with core modules for action planning, agent orchestration, execution with policy enforcement, approval flows, auditability, and integration into build and packaging systems.
- macOS Window State Restoration: A pull request adds the
electron-osx-spacesdependency and implements native macOS APIs to save and restore each window's virtual desktop (Space) on restart, ensuring windows reopen in their original Spaces with backward compatibility.
- Welcome Page and UI Asset Updates: The sessions sign-in screen is updated by replacing the monochrome walkthrough logo with the full-color Sessions product icon, consolidating assets, removing unused files, and ensuring dynamic icon quality matching the build.
- Git Keyboard Shortcut Additions: Default keyboard shortcuts are added for git stage and unstage commands, improving discoverability and accessibility of these operations with Ctrl/Cmd+Shift+S/U/A combinations.
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: 477
Key Closed Pull Requests
1. Add agent network filter policy settings: This pull request introduces agent network filter policy settings by renaming existing configuration keys, adding migrations, centralizing settings and domain matching logic, implementing the AgentNetworkFilterService to allow or deny network traffic in web fetch and browser chat tools, and includes sample interactions and various improvements to error handling and policy enforcement.
- URL: pull/308434
- Associated Commits: cd99a, 3e194, ad4d8, 3e48d, 53a5a, f814a, 40b8a, 70159, 3d72a, f652b, e82c6, a24d2, bdabf, 99b40, 59089, 89b02, 2f242, 8e0d8, b85ea, c9e4f, 4e2d3, 5eb50, 08d65, 4e905, e752a, dde88
- Associated Commits: cd99a, 3e194, ad4d8, 3e48d, 53a5a, f814a, 40b8a, 70159, 3d72a, f652b, e82c6, a24d2, bdabf, 99b40, 59089, 89b02, 2f242, 8e0d8, b85ea, c9e4f, 4e2d3, 5eb50, 08d65, 4e905, e752a, dde88
2. Ship Copilot as a built-in extension: This pull request integrates GitHub Copilot as a built-in extension in the Visual Studio Code project by adding the Copilot submodule, incorporating its compilation into the main build tasks, setting up specific scripts and CI workflows, and updating related build and telemetry configurations to fully support Copilot within the core editor.
- URL: pull/302778
- Associated Commits: d83a4, 68ef7, 029ce, 49135, 4a530, 79695, bd35a, 59653, c965a, 6bfb0, ec0e4, 1d3e9, 3c73c, 0f869, 2784b, d1c74, 179a9, 1f45f, d07d1, f3a01, 4e4a5, 52435, 16030, 70f14, f88f4
- Associated Commits: d83a4, 68ef7, 029ce, 49135, 4a530, 79695, bd35a, 59653, c965a, 6bfb0, ec0e4, 1d3e9, 3c73c, 0f869, 2784b, d1c74, 179a9, 1f45f, d07d1, f3a01, 4e4a5, 52435, 16030, 70f14, f88f4
3. Add LM Studio integration with BYOK support: This pull request proposes adding integration with LM Studio, including support for Bring Your Own Key (BYOK), by introducing a new language model chat provider, updating configuration settings, cleaning up code, and adjusting TypeScript configuration paths for improved organization.
- URL: pull/309151
- Associated Commits: c61eb, a97e9, 56466, b35fb, cf679, 13de0, f8a32, f6f4e, 3d891, bf5b0, 4aaa9, fc430, 74b9e, 66359, 14ddd, 83bed, 8a7be, d4ebf, 1ae1b, aeab3, 638da, 42fd1
- Associated Commits: c61eb, a97e9, 56466, b35fb, cf679, 13de0, f8a32, f6f4e, 3d891, bf5b0, 4aaa9, fc430, 74b9e, 66359, 14ddd, 83bed, 8a7be, d4ebf, 1ae1b, aeab3, 638da, 42fd1
Other Closed Pull Requests
- Onboarding and Welcome Experience Enhancements: Multiple pull requests focus on improving the onboarding and welcome experience in Visual Studio Code, including a comprehensive onboarding walkthrough with A/B test variations, sign-in call-to-actions, keyboard mapping hints, themed UI elements, and an in-context UI tour with spotlight overlays. Additionally, the chat customizations editor welcome page was redesigned with a new self-contained welcome page class, improved navigation, and polished visual hierarchy to enhance usability and clarity.
- Chat and Terminal Interaction Improvements: Several pull requests enhance chat and terminal interactions by adding automatic detection and display of retries for sandbox-blocked terminal executions, improving interactive terminal input handling, adding a terminal button to the questions tool with progress messages, and implementing an auto-approval mechanism for tool confirmations triggered by inline chat edits on sensitive files. These changes improve user feedback, streamline input handling, and reduce errors related to confirmation prompts.
- ChatSessionCustomizationProvider API Fixes and Enhancements: Multiple pull requests address fixes and improvements to the
ChatSessionCustomizationProviderAPI, including dynamic group creation, immediate list refresh after deletions, resetting section counts to prevent UI flashes, adding tooltips, preventing dropdown jumping, fixing focus outline clipping, and better classification of plugin-sourced items. These updates improve the API's stability, usability, and visual consistency.
- Terminal Input and Command Handling Refactor: A significant refactor removes LLM-powered terminal input elicitation code, replacing it with a lightweight regex-based event to detect input prompts and adding support for interacting with foreground terminals via enhanced commands. This reduces latency and token usage by enabling autonomous detection and response to terminal input requests without extra LLM calls or UI prompts.
- UI and Visual Improvements: Several pull requests improve UI elements such as the update button redesign to a visible blue "Update" state, enhancements to Browse buttons on MCP Servers and Plugins welcome page cards for direct marketplace browsing, and fixes to the OS display name and related app shortcuts. These changes refine visual clarity, user interaction, and branding consistency.
- Performance and Code Cleanup: Pull requests include reducing BASE64 data in tool requests by replacing images with placeholders, refactoring inline summarization to run in the background compaction loop with standardized telemetry, and removing obsolete flags and properties. These efforts improve efficiency, reduce request sizes, and enhance robustness.
- Enterprise Policy and Security Enhancements: One pull request implements enterprise policy enforcement to block access to the Agents app when disabled by organizational settings, adds a UI overlay to notify users, and updates policy configuration to support inheritance from parent app policies. This ensures compliance with organizational restrictions and improves user awareness.
- Miscellaneous Fixes and Updates: Additional pull requests include fixing the Copilot Chat debug experience by correcting launch configurations, updating the project version to 1.117.0 with related dependency and build improvements, and adding informational text to indicate experimental or evaluation model status. These updates maintain project stability and improve user 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 | 281 | 31 | 0 | 1006 |
| sandy081 | 690 | 24 | 4 | 13 |
| roblourens | 303 | 38 | 38 | 20 |
| meganrogge | 252 | 14 | 33 | 73 |
| joshspicer | 323 | 29 | 3 | 11 |
| yogeshwaran-c | 213 | 103 | 0 | 0 |
| bpasero | 271 | 0 | 3 | 3 |
| lszomoru | 212 | 43 | 2 | 7 |
| mrleemurray | 249 | 2 | 0 | 0 |
| DonJayamanne | 127 | 31 | 24 | 20 |
Access Last Week's Newsletter: