Weekly GitHub Report for Vscode: August 31, 2026 - September 07, 2026 (21:21:45)
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 addressing a range of issues resolved under the "February 2025 Recovery 2" milestone. For detailed information, users are directed to the complete release notes available on the official Visual Studio Code updates page.
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.
-
[RECENT-REGRESSION] Icons render as missing glyphs in Remote-SSH since 1.136.0 — glicons.woff2 fails to load: This issue reports that starting with VS Code version 1.136.0, icons in Remote-SSH sessions render as missing glyphs because the
glicons.woff2font file fails to load, causing multiple unrelated extension icons to appear as empty or boxed placeholders while tooltips and functionality remain intact. The problem is traced to a referrer check added in a recent commit that incorrectly rejects requests with empty referrer headers, resulting in failed resource loads and a visual regression limited to remote sessions, with various users confirming the issue across platforms and versions.- The comments confirm widespread reproduction of the icon loading failure in Remote-SSH since 1.136.0, discuss detailed diagnostics identifying a faulty referrer check in the protocol handler as the root cause, share logs and bisect results, and suggest a workaround by disabling the exec server, though some report connection issues with that workaround.
- Number of comments this week: 19
-
[UX] [MODERNIZATION] Primary Side Bar width resets after toggling visibility (Ctrl+B): This issue reports a regression in VS Code version 1.136.0 where the Primary Side Bar width resets to its default narrow size after toggling its visibility using Ctrl+B, instead of retaining the custom width set by the user. The problem specifically occurs when the side bar is positioned on the right side and persists even with all extensions disabled, with some users finding a temporary workaround by switching the layout density to "Compact."
- Multiple users confirmed the issue across different operating systems and setups, noting it as a regression from previous versions; several suggested workarounds such as enabling "Layout Density | Compact" or disabling Modern UI, while developers acknowledged the problem and indicated a fix is forthcoming.
- Number of comments this week: 17
-
[TRIAGE-NEEDED] Send x-opencode-session header on API requests (required by OpenCode Go from 09/05): This issue requests that the OpenCode Go managed-inference API include an
x-opencode-sessionheader with a stable per-conversation ID on all outbound API requests starting from 09/05, as requests without this header will begin to error. The user highlights that GitHub Copilot Chat currently does not send this header, causing disruptions for many users who rely on the service through VS Code and Copilot CLI.- The comments express significant frustration and urgency from users who are stuck due to the new header requirement, with some suggesting workarounds like third-party extensions and others calling for an official fix from the development team; there is also criticism directed at the API provider for breaking service without a timely solution.
- Number of comments this week: 11
-
[FEATURE-REQUEST] [EDITOR-CORE] [Feature request] Hide cursor while typing: This issue requests the addition of a feature in VS Code to hide the mouse cursor while typing, similar to functionality available in other text editors and operating systems, to improve typing visibility and reduce distraction. Users discuss various workarounds including third-party utilities and extensions, but highlight the need for an integrated solution within VS Code, noting technical challenges and platform differences.
- The comments show strong user demand for this feature, sharing multiple third-party tools and extensions as temporary fixes, discussing technical limitations and possible implementation approaches, and noting that the issue has been partially resolved on macOS but remains open for Windows and Linux, with plans to address it in upcoming Chromium updates.
- Number of comments this week: 9
-
[TRIAGE-NEEDED] [NEW RELEASE] MCP tool calls intermittently rejected "disabled by the user" while cache shows enabled and server log shows execution: This issue describes an intermittent problem where calls to MCP tools in Copilot Chat's ask mode are sometimes rejected with a "disabled by the user" error despite the cache showing the tools as enabled and server logs confirming execution. The root cause is identified as a timing and synchronization issue between the MCP tool authorization cache, per-window server connection states, and Copilot's permission checks, exacerbated by multiple VS Code windows and stale cached workspace-level MCP configurations.
- The comments provide a comprehensive root cause analysis showing that the issue arises from a static snapshot of available tools taken before all tools are registered, causing some tools to be incorrectly marked as disabled; two fix proposals were submitted—one dynamically updating tool availability scoped to referenced servers (recommended) and another simpler but less secure approach; additional observations highlight multi-window architecture limitations that affect MCP state synchronization, suggesting a separate issue for those concerns.
- 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.
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: 463
Summarized Issues:
- Authentication and Sign-in Issues: Multiple problems affect user authentication flows, including persistent error pop-ups when cancelling sign-in, invalid GitHub authentication tokens immediately after signing in causing 401 errors, inability to log in despite authorization, and account mismatches between Copilot Pro+ and Copilot Chat. These issues disrupt user access and functionality, requiring repeated sign-in attempts or causing features to be unusable.
- Chat Session and UI Behavior Problems: There are numerous UI inconsistencies and bugs in chat sessions, such as flickering or disappearing sessions when restoring checkpoints, missing hover effects on nested chats, lost chat history after closing custom agent popups, inability to close main chat tabs, and unexpected UI jumps when interacting with subsessions. These issues degrade the user experience by causing confusion, loss of data, or inconsistent interface behavior.
- Model and Agent Configuration Challenges: Users face difficulties with model selection and agent configuration, including confusing model picker UX, outdated or missing model updates, inability to use third-party BYOK models as subagents, and bugs causing model dropdowns to show only "Auto" option. These problems limit flexibility and clarity in choosing and managing AI models within VS Code.
- Performance and Stability Issues: Several reports describe severe performance regressions and crashes, including UI freezes during heavy Copilot Chat use, extension host crashes on startup, renderer out-of-memory crashes during plugin sync, and frequent VS Code crashes during specific tasks. These issues cause interruptions, data loss, and degraded productivity.
- File and Workspace Management Bugs: Problems include incorrect attribution of file changes in multi-agent workspaces, inability to push changes after branch checkout, deletion of parent folders when deleting nameless files, and issues with Git worktree recognition and remote file URI handling. These bugs risk data integrity and complicate source control workflows.
- issues/333633, issues/333954, issues/333841, [issues/334453](https://github.com/issues/334453]
- Terminal and Shell Integration Problems: Issues include terminal tabs sharing sessions across windows, failure to respect configured terminal profiles in agent shells, integrated terminal freezing, and shell sandboxing permission denials. These problems hinder command execution and terminal usability within VS Code.
- Agent and Automation Functionality Defects: Bugs affect agent behaviors such as failure to dispatch follow-up prompts, autopilot mode not ending turns properly, skills not refreshing across sessions, and subagents producing no visible output. These defects reduce automation reliability and agent effectiveness.
- Customization and Settings Issues: Users report problems with settings not being recognized or applied correctly, such as workspace-level disabling of summarization, migration hints not showing or disappearing unexpectedly, and inability to inherit customizations in Git submodules or parent repositories. These issues complicate configuration management and user control.
- issues/333667, issues/334553, issues/334454, [issues/334571](https://github.com/issues/334571]
- UI Layout and Visual Design Inconsistencies: Multiple issues describe misalignments, overlapping elements, missing or inconsistent focus indicators, and problematic spacing in menus, tabs, and chat icons. These visual defects impair usability and accessibility.
- issues/333600, issues/334199, issues/334610, [issues/334114](https://github.com/issues/334114]
- Extension and Plugin Management Problems: Problems include persistent file handles blocking plugin updates, failure to load or recognize agents in plugins, and extension signature verification failures. These issues disrupt extension lifecycle and security.
- issues/334391, issues/334153, [issues/334799](https://github.com/issues/334799]
- Search and Navigation Limitations: Users face missing or inconsistent search functionality in markdown previews, chat sessions, and global search, as well as navigation issues like missing scrollbars or inability to switch tabs with arrow keys. These limitations reduce efficiency in locating and managing content.
- issues/334860, issues/334639, [issues/334605](https://github.com/issues/334605], issues/334685
- Security and Data Privacy Concerns: There are reports of cross-session data leaks where remote read tools return data from unrelated SSH sessions, and Copilot reading files outside the workspace without permission prompts, raising serious security and privacy risks.
- issues/334881, [issues/334925](https://github.com/issues/334925]
- Agent Merge and Pull Request Integration Issues: Problems include failure to initiate agent merge for multiple PRs targeting different branches, unclear UI for agent merge status, and PR views failing to load or resizing unexpectedly. These issues hinder smooth PR workflows.
- issues/334662, issues/334891, [issues/334873](https://github.com/issues/334873]
- Miscellaneous Bugs and Feature Requests: Various other issues include requests for improved telemetry, keyboard shortcuts, UI theming options, and bug reports on emoji deletion, markdown editor cursor behavior, and workspace folder identification. These reflect ongoing refinement needs across the product.
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: 455
Summarized Issues:
- UI and Menu Interaction Issues: Several issues report problems with the VS Code menu bar and hamburger menu failing to open or respond correctly, especially when using compact menu bar visibility or after updates. These bugs cause menus to be inaccessible or improperly rendered, impacting user navigation and workflow.
- Extension Icon Rendering Failures: Multiple reports indicate that extension icons fail to display properly in VS Code, particularly in Remote SSH environments or after recent updates. Users see missing, invisible, or placeholder icons instead of the expected extension visuals, which hinders extension identification and usage.
- Sidebar and Panel Size Persistence Problems: Several issues describe the sidebar, explorer panel, or primary side bar not remembering user-resized widths after being closed or hidden, often reverting to a narrow or default size. This regression affects user customization and requires manual resizing on each use.
- Copilot and Chat Extension Bugs: Numerous issues report problems with GitHub Copilot and Copilot Chat, including crashes, failure to activate, session management errors, UI glitches, and incorrect behavior such as frozen chat windows or unexpected command triggers. These bugs disrupt AI-assisted coding workflows and user productivity.
- Agent Host and Session Management Issues: Several reports highlight problems with the Agent Host, including session discovery delays, session state inconsistencies, migration failures, and UI sluggishness when handling multiple sessions or large catalogs. These issues affect the reliability and responsiveness of agent-based features.
- Performance and Memory Consumption Problems: Some issues describe severe performance regressions, including high memory usage, UI lag, and renderer process freezes, often triggered by specific extensions or workflows. These degrade the overall user experience and can cause system instability.
- Terminal and Integrated Console Bugs: Multiple issues report problems with the integrated terminal, such as failure to open, inability to clear the screen properly, and crashes related to terminal rendering or command execution. These bugs hinder command-line workflows within VS Code.
- Chat UI and Interaction Glitches: Several issues describe UI problems in chat interfaces, including clipped pills, inconsistent font sizes, frozen or unresponsive chat windows, and incorrect rendering of links or session indicators. These affect usability and clarity in chat-based features.
- Network and Proxy Configuration Issues: Some reports highlight problems with proxy settings, network errors, and failures to access online services like the extensions marketplace or GitHub Copilot API, often due to special characters in credentials or misconfigured proxy rules.
- Accessibility and Voice Mode Enhancements: A few issues focus on improving voice mode features, including session awareness, navigation, and intent recognition, as well as accessibility improvements for screen readers and keyboard navigation in chat and agent windows.
- File and Workspace Management Problems: Reports include issues with file visibility, workspace folder selection, symbolic link tooltip enhancements, and problems with multi-root workspace handling, affecting project organization and navigation.
- Buggy Behavior in Diff and Editor Features: Some issues describe bugs in diff editors, bracket coloring, inline suggestions, and code folding, leading to incorrect visual feedback or broken editing experiences.
- Security and Sandbox Policy Concerns: A few issues address sandbox enforcement inconsistencies, security flaws allowing unauthorized file writes, and policy conflicts affecting feature enablement, raising concerns about enterprise security compliance.
- Miscellaneous Bugs and Feature Requests: Various other issues include requests for improved model management UI, chat mode defaults, file path autocomplete in terminal, and bug reports about unexpected behavior in specific languages or themes.
2.5 Issue Discussion Insights
This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.
-
- Toxicity Score: 0.75 (Rapid escalation potential, aggressive language, strong emotional tone)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and using aggressive language to report a bug, with no subsequent comments or interactions. The tone is highly emotional and confrontational, but the conversation has not yet developed or escalated.
-
Send x-opencode-session header on API requests (required by OpenCode Go from 09/05)
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, insults, mounting frustration)
- This GitHub conversation begins with users expressing frustration and confusion about a new requirement impacting their workflow, with some offering solutions or suggestions. The tone shifts from initial concern to increasing irritation, culminating in aggressive and insulting language directed at a specific user. Requests for urgent fixes and dissatisfaction with the handling of the issue are prevalent, indicating mounting tension and dissatisfaction.
-
- Toxicity Score: 0.95 (Rapid escalation, offensive language, explicit content, lack of moderation)
- This GitHub conversation features a single user posting a highly inappropriate and offensive comment containing explicit and derogatory language. There is no constructive or technical discussion present, and the tone is aggressive and disrespectful. The comment appears to be a deliberate provocation or spam, triggering immediate tension due to its content. No other users engage in the thread, leaving the conversation unresolved and potentially prone to further toxic remarks.
-
https://developers.stellar.org/docs/ZUJY020828UY4/data/apis/rpc/providersyaelzdj
- Toxicity Score: 0.75 (Rapid escalation, spam content, invalid label)
- This GitHub conversation involves a single user posting a spam comment, which triggers a label marking the issue as invalid. The tone is neutral but the presence of spam indicates a potential for disruption. No further interaction or escalation is observed.
-
- Toxicity Score: 0.65 (Rapid escalation, ambiguous language, potential offensiveness)
- This GitHub conversation involves minimal interaction with two brief comments, one of which appears to be a command and the other a response containing unclear or potentially offensive language. The tone is terse and lacks constructive engagement, with no clear resolution or collaborative effort. The presence of a label marking the issue as invalid suggests the conversation did not progress productively.
-
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, spam-like comments)
- This GitHub conversation involves multiple users posting brief, disjointed comments with a mix of nonsensical text and profanity, indicating frustration and a lack of constructive engagement. The tone shifts quickly from neutral or playful to aggressive, with some comments potentially intended to provoke or spam. The presence of offensive language and irrelevant messages triggers tension and disrupts productive discussion.
-
- Toxicity Score: 0.65 (Rapid escalation, spam content)
- This GitHub conversation involves a user posting a bug report template with no substantive content, followed by a single comment containing a spam message. The tone is neutral initially but shifts abruptly due to the spam comment, which likely triggers moderation actions. There is no evidence of direct conflict or extended discussion.
-
- Toxicity Score: 0.65 (Rapid escalation, disruptive comment, spam detected)
- This GitHub conversation involves a single user posting a performance issue report with detailed system and environment information, followed by a single comment containing a spam command. The tone is neutral in the initial report but shifts abruptly due to the spam comment, which introduces a negative and disruptive element. There is no evidence of dialogue or resolution, and the spam comment acts as a trigger for potential tension or moderation intervention.
-
- Toxicity Score: 0.75 (Rapid escalation, spam comment, lack of moderation response)
- This GitHub conversation involves a single user posting a spam comment shortly after the initial feature proposal, which is met with no further engagement or constructive discussion. The tone is neutral to negative due to the spam nature of the comment, and the conversation is quickly marked with an 'invalid' label, indicating a lack of productive interaction. The trigger of tension is the spam comment disrupting the otherwise technical and structured proposal.
-
Implement new backup solution with 99.9% reliability target
- Toxicity Score: 0.75 (Rapid escalation, spam content, lack of constructive engagement)
- This GitHub conversation involves a single user posting a spam comment, which likely triggered the application of 'invalid' and 'triage-needed' labels by maintainers. The tone is neutral to negative due to the spam nature of the comment, and no constructive discussion or resolution is evident. The interaction is minimal and does not escalate beyond the initial spam post.
-
Implement new backup solution with 99.9% reliability target
- Toxicity Score: 0.75 (Rapid escalation, spam content, dismissive tone)
- This GitHub conversation involves a single user posting a spam comment, which likely triggered the application of labels indicating the issue is invalid and requires triage. The tone is dismissive and unconstructive, with no meaningful engagement or discussion from other participants. The interaction is minimal and does not develop beyond the initial spam message.
-
- Toxicity Score: 0.75 (Rapid escalation, spam content, dismissive response)
- This GitHub conversation involves a single user posting a spam comment, which triggers a negative sentiment and a dismissive tone from the community or maintainers, leading to the issue being labeled as invalid. There is no further engagement or constructive discussion following the spam message.
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: 200
Key Open Pull Requests
1. Add MCP customization migration: This pull request introduces a guarded MCP server migration feature within the Agent Customizations editor, enabling the migration of eligible workspace server entries from .vscode/mcp.json to a workspace-root .mcp.json file with enhanced UI integration, session-aware eligibility checks, safe write operations including rollback protection, and detailed logging, all gated behind a new feature flag for controlled enablement.
- URL: pull/334369
- Associated Commits: bdc14, d8d7f, 920bf, 7c7ed, 3e656, 48e82, e58fd, d84e6, e0f11, f067a, 8651c, 1e724, 41f19, 14288, 5387b, 5eb89, 8e251, 22827, 7a37f, 7f2ff
2. editor: hide mouse cursor while typing: This pull request introduces an opt-in setting editor.hideMouseCursorOnTyping that hides the mouse cursor during keyboard text input to prevent it from obscuring nearby code, with the cursor reappearing on mouse activity or focus changes, and includes comprehensive browser tests and refinements to cursor visibility logic.
- URL: pull/334080
- Associated Commits: aebca, d88a1, 32555, cafe3, 03d29, a6fbd, afc43, 7afbd, 741ed, b75d8, 64d2a, 1dc80, 9637f, 18d5e
3. Make action widget menu items directly clickable by Playwright: This pull request improves the action widget menu items in Visual Studio Code by enabling Playwright to click them directly without requiring forced clicks or preliminary hover actions, while preserving native CSS hover styling and keyboard focus behavior, removing a temporary pointer shield, updating automation helpers, and validating these changes through extensive testing across multiple environments.
- URL: pull/334705
- Associated Commits: a25d2, 1e6b3, 583eb, b00ea, 1c803, 9a8da, a800f, 46f70, 3982d, 2cf00, 13b15, 23734, 4e63c
Other Open Pull Requests
- Webview service worker registration and recovery: This topic covers improvements to the webview service worker registration process by implementing a retry mechanism with exponential backoff and cleanup of corrupted states. It also includes reloading the webview up to five times on fatal errors before showing an error notification, with safeguards to prevent repeated failures and improve recovery without requiring a full window reload.
- Agent session lifecycle management: These pull requests introduce opt-in, application-scoped settings to automatically archive and delete inactive agent sessions after their associated pull requests are merged. They include configurable retention periods, enterprise policy support, lifecycle safeguards for manually archived sessions, and integration into Agent Host configuration and session workflows.
- Copilot Agent Host testing and runtime updates: This topic includes enhancements to Copilot Agent Host prompt snapshot tests by publishing canonical client-tool profiles and refactoring shared helpers for improved synchronization. It also covers updates to the Copilot runtime and SDK versions with strengthened end-to-end Agent Host test scenarios to cover regressions and platform-specific issues.
- Chat feature bug fixes and UI improvements: These pull requests fix issues such as text editing before inline
#file:references deleting them, errors when opening Chat in new editors or auxiliary windows, and alignment of the context-usage widget with custom chat backgrounds. They add logic to preserve references, guard against unrendered widget parts, and restore visual alignment with regression tests.
- Agent Hosts and Automation session enhancements: This includes adding an end-to-end smoke test for Agents Window validating Dev Container sessions across platforms and implementing a system to capture, share, and persist scoped Agent Host customization snapshots and plugin artifacts for consistent Automation sessions.
- Accessibility and input improvements: These pull requests add an enhanced focus feature to the AccessibilityService with new states, configuration listeners, and events, and fix IME input jitter in WebKit browsers by adjusting editor textarea content during composition updates.
- Code hygiene and ESLint compliance: This topic covers replacing identifier-safe bracket notation with standard dot notation in Workbench UI and service files, removing cleaned groups from ESLint allowlists, and refactoring default-account tests to use typed subclasses with protected access, improving code hygiene across multiple source files.
- Voice Mode and session focus improvements: These pull requests improve Voice Mode session awareness by resolving focus targets using case-insensitive session labels, preferring live chat-model states, immediately publishing idle transitions, and adding regression tests for label-based focus and stale status issues.
- Customizations migration and management UI: This includes implementing a new customizations migration dashboard within the customizations modal for reviewing and managing prompt files, user data customizations, and MCPs, with UI enhancements aligned to recent redesigns and comprehensive testing.
- Chat input control height unification: This pull request unifies chat input control heights across new and existing sessions in the VS Code Agents window by introducing a shared 22px height variable applied to various controls, ensuring visual alignment and adding focused component fixtures.
- CLI update command and transport implementation: This pull request introduces a new CLI update command control transport with nested commands, routing update requests through a main-process IPC service supporting windowless instances, preserving output and exit codes, and removing deprecated update command forms.
- Custom Endpoint wizard validation fixes: This pull request fixes a bug where empty
models[].urlvalues caused a TypeError by adding validation and improving error messages to clearly indicate missing or invalid URLs, ensuring valid URLs resolve correctly.
- Code review skill and user instructions: This pull request adds a code review skill with user-specific instructions, fixes path references, enhances username discovery, and provides debugging support.
- Copilot tool execution progress routing: This pull request updates Copilot integration to route tool execution progress messages through a dedicated progress line channel, coalescing repeats and maintaining running state consistency while keeping progress separate from partial tool output.
- Replay attribution index hydration: This pull request implements hydration of the replay attribution index into resumed sessions to correctly attribute tool results arriving after restarts, improving session continuity by reading transcripts on resume and managing attribution seeds.
- Agent Host MCP connector discovery service: This pull request introduces a shared Agent Host service that discovers and manages MCP connectors by fetching the Copilot Connectors catalog with OAuth credentials, validating and caching responses, merging connected MCP servers, and unifying local and remote host implementations without new token plumbing.
- Right-to-left editor layout support: This pull request adds a new
editor.textDirectionoption enabling full right-to-left layout of editor contents, including mirroring UI elements, preserving per-line direction decorations, and providing a toggle command for per-file text direction switching.
- Copilot prompt snapshot test update: This temporary test branch validates automated updates to Copilot prompt snapshot expectations caused by a CLI version bump, regenerating prompt snapshots and adjusting the mock LLM server without production code changes.
- Webview image copy fix: This pull request fixes the issue where copying an image from a webview context menu did not place it on the clipboard by tracking the context menu target, encoding images as PNG, and writing them directly to the clipboard with fallbacks and focus handling.
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: 459
Key Closed Pull Requests
1. Update default Copilot prompts: This pull request proposes updates to Copilot's default prompt guidance covering autonomy, required skills, repository conventions, delegation, follow-up handling, verification, and audience-ready deliverables, introduces explicit opt-in for sub-agent delegation, adds hidden model N prompt routing and GPT-5.6 capability checks, and includes validation through model capability tests and prompt ESLint diagnostics, targeting the release/1.136 branch.
- URL: pull/334115
- Associated Commits: 0f7b8, 61d23, 055d7, cb7a0, 4df58, a3fb1, fcbe6, e69a7, b3b70, a6297, 81ba3, 9e790, 400d8, ffad9, 07864, c3f2a, 9e1f9, 45a37, 54f9f, dbc1f, 58e59, feaa8, 05b0e, 736a3, 28abc, 634e1, 61bf9, 5fef1, 759f7, 9eebd, 14060, 1dbbc, f1e25, 05144, 75f6e, 006c4, 5238b, 4d3de, 374ea, 17eb8, dba2b, f8357, 95bb5, 752a8, 00e9a, 6dc71, dcfcb, aa5dc, deea7, 94db6, e05ba, bcec3, 1c1a4, 69343, 1d74e, ab3de, c9479, 74293, a2379, 40c96, 5886d, fb628, 95922, 1b67e, a270c, ec7a0, 2936a, d62f8, 3596f, 193cd, e51f3, d2273, 2b829, 57341, b590b, 9a754, 33451, 735c7, 3d32d, 24998, 5ae9f, 6b606, 71730, 768c8, 7c90a, c652b, eb84d, aaa62, 1d88d, cf307, 214e6, 23a3a, e8423, 3e33b, 9b8b6, 494b9, d6fff, c88ff, e6094, 9e596, 74ebc, 6ef49, d264a, 8098e, 04897, 519f5, df241, 8af52, c1604, 8d032, daf67, 3d759, 22f76, 63f32, 9f878, 737ec, 47352, 0f7c9, 0ff22, 9f921, f83aa, 58d8a, 959f7, bb41c, 86775, ac256, 35e20, 15463, 39767, 1f027, 0352a, ca462, 2fede, daae5, 3a5a3, 2bb7d, 06678, fda58, 67069, aea89, fde1a, b176e, 91b0c, 46f6e, bf1d0, 9fefe, c2d05, 5a60c, c89cd, 6abb0, 33913, 9e62c, d7a95, fef8e, b8b40, ebbbc, 41837, 05829, ba0c0, 4fdf4, 54157, 3a753, 22652, 0b0fb, e5391, cf724, 42b53, 8a6a8, ab4e1, 91078, 49d49, e565c, 32e32, d5a3b, b5a06, 93c19, aa56e, 98807, 7cc26, 48465, 55825, 63acf, d953e, f8749, 6737a, f6258, 1f625, 3bd9f, cfc47, 845b7, 40d4b, 3df78, fb4a0, 529cf, 3d6f1, ab099, afb58, 0eb8e, 02e05, f9a71, 8ba7a, 1b7f0, c3a0e, 359cb, 9dfde, b948a, 42b84, 3a01d, 4fe18, 6995a, 967c9, 23d05, 79f13, cc9de, a9638, ea742, 6d487, 1ab68, 03978, f6f7c, ba368, 3f953, b8d56, ca904, d2c49, 2583f, 62be3
2. Enhance AI network access control for integrated browser: This pull request aims to enhance and harden the AI network access control for the integrated browser in VS Code by enforcing domain-based policies across various browser components and actions, serializing network filtering operations to prevent race conditions, isolating unshared views, securing the Playwright sandbox environment, maintaining active network filtering during dialog interruptions, and ensuring comprehensive policy validation and ownership tracking for popups and nested browser views.
- URL: pull/328880
- Associated Commits: df270, ff13e, 12325, 59ce1, a3c15, fdac1, 8b1ab, 18e64, 25ef8, 13d6b, 6d382, 3297c, e2fea, 27b63, 6d516, f176f, 6c79d, 3e0d4, 2858b, 4a222, c4ae3, f0212, e5e0f, 73e00, e89e0, 9997b, 564f0, a9ecb, d4cf5, 99b07, 4183c, 1618f, 5f725, c8e5e
3. automations: refactor: make provider session templates canonical: This pull request refactors the Automation system in VS Code to replace legacy flattened session configuration fields with a canonical, provider-owned session template that faithfully represents model, agent, mode, approvals, and provider-specific settings, enabling consistent editing, storage, and execution through the Agent Host Protocol while preserving backward compatibility, improving configuration capture and validation, unifying fallback and AHP execution paths, and enhancing UI behavior and policy enforcement.
- URL: pull/334521
- Associated Commits: 1e3c7, 1bbf5, d6ab9, 23960, 4dd77, ee251, 4b9db, 4df0d, fa0e7, 82ba2, 018e7, 920d1, 51438, 4a42f, 48d93, 869f1, a53d6, 7eda6, a5a21, d7efa, f9ab7, 2dec7
Other Closed Pull Requests
- Editor Character Width Alignment: This pull request introduces an opt-in setting
editor.forceFullwidthCharacterWidththat ensures full-width characters like CJK glyphs are centered within exactly two monospace character cells, improving alignment and consistent rendering across editor features. It maintains existing behavior for non-full-width characters and proportional fonts to avoid disrupting current user experiences.
- Workspace and Repository Management Enhancements: Multiple pull requests improve workspace and repository handling by consolidating GitHub execution workspaces and remote hosts into a single Remote workspace-picker tab, enhancing repository selection prompts, and fixing GitHub context repository selection in chat features. These changes support multi-root workspaces, Git worktrees, and preserve folder and remote preferences to streamline user workflows across Agents and editor windows.
- Agent Host and Evaluation Session Features: Several pull requests add support for VS Code-owned evaluation sessions with private CLI flags, implement automatic SDK downloads with improved notifications and error handling, and enable Python environment activation within Agent Host shell tools using per-session shell initialization scripts. These enhancements are gated behind experimental settings and include validation and end-to-end testing to ensure robustness.
- Agent Merge and Draft Pull Request Improvements: Pull requests enhance the Agent Merge widget by improving accessibility, interaction, and visual presentation, and introduce a combined operation in agentHost to create draft pull requests with Agent Merge enabled. These updates include consolidating status summaries, refining layout and focus behaviors, managing draft readiness through required checks, and updating UI elements and notifications for a smoother merge experience.
- Chat and Skill Completion Enhancements: Improvements include fixing skill completion interactions in the Automations dialog by enabling Tab and Enter keys to accept suggestions properly, unifying chat reference decoration styling, and adding the chat extension's custom URI scheme to allowed schemes for rendering. These changes ensure consistent styling, better user input handling, and support for extension-provided virtual file system URIs.
- UI and Layout Refinements: Multiple pull requests refine the styling and layout of editor and chat tabs in the Agents window, stabilize the Sessions title-bar layout, fix dark theme scrollbar colors and layout on customization pages, and redesign the model picker interface as an experimental feature. These updates standardize header sizes, spacing, separators, and improve accessibility, performance, and visual consistency across themes and modes.
- Session and Migration Management: Pull requests implement conversion of workspace-less sessions to workspace sessions for better continuity, and introduce a migration page in the chat customization dialog to detect, filter, and migrate agents, instructions, and skills from unsupported locations. These features include new services, experimental settings, and comprehensive testing to enhance session management and user control over migrations.
- Security and Authentication Enhancements: Enhancements include validating gallery server URLs to restrict requests to configured origins, disabling redirect following, enforcing runtime validation of package registry types, and enabling sign-in with Microsoft Entra ID for Private Marketplace access with provider-aware authentication paths and server-enforced eligibility checks. These changes improve security, reliability, and access management in VS Code.
- Testing and Performance Optimizations: A pull request optimizes the startup process of repeated unit tests by checking cached Electron versions and executables directly, avoiding unnecessary prelaunch helper startups, invalidating caches on relevant changes, and unifying test launch entry points across platforms. This significantly reduces test launch times while preserving dependency installation expectations.
- Bug Fixes in Suggestions and Context Handling: A pull request fixes an issue where implicit pull request suggestions would reappear after being attached by refining identity comparison logic, preventing duplicate suggestions while allowing relevant file suggestions.
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 | 351 | 24 | 21 | 947 |
| dmitrivMS | 443 | 39 | 21 | 107 |
| roblourens | 478 | 34 | 25 | 36 |
| meganrogge | 430 | 39 | 35 | 36 |
| benibenj | 372 | 34 | 6 | 21 |
| sandy081 | 369 | 20 | 10 | 28 |
| connor4312 | 291 | 15 | 4 | 29 |
| mrleemurray | 212 | 22 | 10 | 14 |
| RyanEwen | 126 | 38 | 13 | 62 |
| lramos15 | 188 | 8 | 21 | 14 |
Access Last Week's Newsletter: