Weekly GitHub Report for Vscode: December 01, 2025 - December 08, 2025 (12:00:54)
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.
-
File explorer is not updating view with new files: This issue reports a bug in the VS Code Insiders edition where the file explorer does not automatically update to show new files created via the integrated terminal, requiring the user to leave and re-enter the workspace to see them. The problem appears consistently across all workspaces on Linux, and attempts to diagnose it involved checking file watcher behavior, running with extensions disabled, and comparing with the stable build where the issue does not occur.
- The discussion focused on reproducing the issue in a clean environment and gathering detailed logs related to file watching, with suggestions to enable verbose logging and try different folders. Despite these efforts, the file watcher failed to detect changes in the Insiders build, while the stable build worked correctly. Attempts to bisect the regression were hindered by errors with commit references, and no definitive cause was identified, leaving the file watcher malfunction unresolved on the reporter’s system.
- Number of comments this week: 21
-
I should only see a single fetch prompt if there's a 301: This issue addresses the problem of users being prompted multiple times to confirm fetch requests when a URL returns a 301 redirect, specifically using the example of fetching top stories from nyt.com redirecting to www.nytimes.com. The user suggests implementing a preflight check to detect 301 redirects beforehand so that only a single confirmation prompt is needed, while also noting potential issues with fetching the redirected URL due to possible bot blockers.
- The comments explain that the multiple prompts are intentional for security reasons to prevent malicious redirects from trusted domains leading to harmful sites, with concerns about open redirects and data exfiltration. Some participants consider the safety of using HEAD requests for preflight checks but conclude it is not secure enough, while others discuss the possibility of allowing certain safe redirects within the same fetch session, emphasizing the importance of user approval when redirecting between different origins.
- Number of comments this week: 9
-
Bogous legacy name for usages-tool: This issue addresses confusion around the legacy naming convention for the
usagestool, where the legacy name is identical to the current name, potentially causing ambiguity. The discussion focuses on how the namespace and legacy tool references should be defined and mapped, with suggestions to move the association to the tool level for clarity and concerns about the current schema exposing proposal-gated properties prematurely.- The comments clarify that the naming is intentional to link
usagestosearch/usages, but there is debate about where the namespace should be defined, with consensus leaning towards defining it at the tool level rather than the toolset. It was agreed that legacy name properties should remain proposal-gated and not be finalized or exposed in the schema yet, leading to the removal of these properties from the schema and consideration of whether this change should be a candidate for further discussion. - Number of comments this week: 8
- The comments clarify that the naming is intentional to link
-
Ranges reported as by the model do not match the file: This issue describes a problem where the ranges reported by the AI model when reviewing TypeScript files do not correctly correspond to the actual locations in the source code, causing confusion in mapping reported issues to the code. The discussion explores the root cause as the model's difficulty in accurately counting lines, the impact of recent changes encouraging the use of line numbers, and potential solutions such as improving symbol linking and refining instructions to the model to balance line number and symbol references.
- The comments analyze the issue as stemming from the model's inaccurate line counting rather than a misrepresentation of the file data, noting that downstream tools do not rely on line numbers. Suggestions include enhancing symbol-based references for better precision, revisiting the use of line numbers in file reading, and updating the model's instructions to reduce overuse of line links while preserving symbol links, with some improvements demonstrated but concerns about timing and confidence in the fix remain.
- Number of comments this week: 7
-
User skill not used: This issue reports that a user-defined skill, although recognized in the chat debug logs, is not being utilized by the agent as expected. The user describes attempts to explicitly invoke the skill and tweak its description without success, contrasting this with workspace-defined skills that do work, and includes detailed skill configuration and debugging information.
- The comments reveal multiple users experiencing the same problem where skills stored outside the workspace (e.g., in the home directory) cannot be read due to file access restrictions, resulting in errors from the read_file tool. Users discuss environment details, verify relevant settings, and note that skills are no longer included in the agent prompt, indicating a possible regression or configuration change affecting skill usage.
- Number of comments this week: 7
2.2 Top 5 Stale Issues:
We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.
- Notebook>Outline: Show Code Cell Markdown: This issue is a feature request asking for the ability to display markdown generated by code cells in the notebook outline, similar to how JupyterLab handles dynamic titles rendered in the output of code cells. The requester highlights that this functionality would allow for dynamic and code-generated markdown to appear in the outline view, enhancing usability and aligning the behavior with JupyterLab’s existing features.
- Using a vscode:// link with ?new-window or ?reuse-window still hijacks existing window: This issue reports a bug in Visual Studio Code where using a vscode:// link with the query parameters ?new-window or ?reuse-window does not open a new window as expected, but instead hijacks the existing window by disconnecting the current remote session and replacing it with the new one. The problem occurs when opening remote SSH connections via these links, causing the loss of the original remote connection instead of creating or reusing a separate window for the new connection.
${userHome}in a task command creates bad paths: This issue describes a problem in Visual Studio Code where using the${userHome}variable in a task command of type "process" generates incorrect file paths that prevent the executable from being found. The reporter notes that while${userHome}works correctly in shell-type tasks with PowerShell as the default shell, it produces malformed paths on Windows when used in process-type tasks, whereas using${env:USERPROFILE}provides the correct path format and allows the task to run successfully.- Terminal in Floating Window Does Not Echo Characters in Real Time When Remotely Connected: This issue describes a problem where the terminal in a floating window does not echo typed characters in real time when connected to a remote environment, such as WSL or SSH, if the main VS Code window is minimized. The characters only appear after restoring the main window, indicating that the remote connection may enter a sleep state when the main window is minimized, preventing immediate terminal updates despite the terminal not being truly frozen.
- Unicode character displayed as a question mark ?: This issue reports that when a fullwidth quotation mark Unicode character (U+FF02) is pasted into Visual Studio Code, it is incorrectly rendered as a question mark instead of displaying the correct symbol. The problem does not occur in web browsers like Firefox, indicating a rendering or font support issue specific to VS Code on Fedora 39 with version 1.87.2.
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: 720
Summarized Issues:
- Extension Unresponsiveness and Crashes: Numerous issues report the VS Code extension (mostly version 0.33.3 and 0.33.4) becoming unresponsive, freezing, or crashing across various platforms including Windows 10, Linux, and Darwin arm64. Users experience hangs during input, failure to respond to prompts, and crashes during normal operations such as debugging, chat interactions, or extension startup, severely impacting usability.
- Chat and Conversation History Issues: Multiple reports describe problems with chat history, including disappearing question history, inability to see prompts visually, chat input not appearing, and chat sessions not restoring properly after reloads or delegation. Users also face issues with chat limits, chat freezing, and chat UI glitches such as flickering or incorrect session titles.
- Performance Degradation and Resource Consumption: Several issues highlight severe performance problems including high CPU and memory usage, slow response times, and unresponsiveness during large file operations or long-running tasks. Some users report memory leaks, excessive token consumption, and freezing during debugging or agentic AI tasks, often requiring restarts.
- GitHub Copilot and Model Behavior Bugs: Many issues report Copilot-related bugs such as failure to generate suggestions, incomplete or gibberish responses, repeated code blocks, failure to follow instructions, and problems with specific models like Gemini 3 Pro, Claude Opus 4.5, and GPT-5.1. Users also report issues with model selection, token limits, and network errors affecting Copilot functionality.
- Background and Cloud Agent Session Problems: Users report issues with background and cloud agents including failure to stop sessions, incorrect display of session status, duplicate attachments, missing file changes, and inconsistent session restoration after reloads. Delegation between local, background, and cloud agents sometimes fails or behaves unexpectedly.
- Terminal and Integrated Console Issues: Several bugs involve the integrated terminal, including autocomplete dropdown failures, terminal output clipping, terminal crashes due to invalid commands, and issues with terminal input and path suggestions. Some problems relate to terminal behavior in remote or WSL environments.
- Source Control and SCM View Problems: Users report bugs with the Source Control Management (SCM) view including incorrect badge counts, inability to delete stashes, duplicate repository entries due to worktrees, and confusing UI elements. Requests include adding multi-select for stashes and better stash integration in other SCM views.
- UI and Accessibility Issues: Multiple reports highlight UI glitches such as flickering, misaligned icons, missing or confusing buttons, and poor keyboard navigation. Accessibility concerns include lack of screen reader support, confusing focus behavior, and missing tooltips or labels in chat and agent session views.
- Extension Installation, Update, and Activation Failures: Several issues describe problems with installing, updating, or activating extensions, including signature verification failures, update errors due to custom install paths, and extensions not activating on expected events or environments.
- Feature Requests and Usability Enhancements: Users request features such as multi-device chat history sync, sidebar layout improvements, better model selection controls, improved tool approval UI, and enhanced session management including search, filter, and rename capabilities.
- Security and Privacy Concerns: A few issues mention potential security and privacy risks related to account development and terminal command auto-approval bypasses, highlighting the need for stricter controls and clearer user consent mechanisms.
- Network and API Errors: Users report frequent network errors such as "getaddrinfo ENOTFOUND," 400 Bad Request, 403 Forbidden, and 500 Internal Server errors affecting Copilot and chat extension functionality, often related to connectivity, firewall, or API request issues.
- Code Editing and Debugging Problems: Several bugs involve incorrect or incomplete code edits, failure to hit breakpoints, problems with debugging configurations, and issues with code suggestions or inline completions not working as expected.
- File and Workspace Management Issues: Users report problems with file operations such as drag-and-drop inserting file paths instead of content, inability to open files via shortcuts, workspace layout not restoring, and issues with large folder expansions causing freezes.
- Model and Tool Configuration Bugs: Problems include tools not auto-approving correctly, tool metadata being incomplete, custom agents not applying model properties properly, and confusing or inconsistent tool naming and descriptions.
- Miscellaneous Bugs: Other issues cover a wide range of problems such as incorrect keyboard shortcuts, broken markdown rendering, missing or incorrect icons, and unexpected UI behaviors.
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: 448
Summarized Issues:
- Chat Session and Editor Behavior Issues: Multiple issues report problems with chat session handling in VS Code, including forced revealing of chat sessions regardless of open location causing bugs with "Open In New Window" (280128), new chat editors opening unnecessarily after closing background sessions (280205), inconsistent session opening behavior between sidebar and editor tabs (280765), and local chat sessions clearing unexpectedly when opened from the agent sessions view (280842). These inconsistencies lead to confusing user experiences and loss of chat context or unexpected UI changes when switching or reopening sessions.
- GitHub Copilot Request Failures and Model Errors: Several issues describe request failures in the GitHub Copilot extension due to unsupported parameters like
top_p(280167, 281418, 281422, 281480, 281503, 281504, 281522, 281623, 281626), invalid JSON format in tool call arguments causing 400 errors (280392, 281380, 281445, 281457, 281695, 281715), and inaccessible attachments leading to request failures (280521, 280901, 281300). These errors prevent proper completion generation and cause misleading error messages, impacting user productivity.
- Background and Cloud Agent Session Management: Issues highlight problems with background agent sessions including missing error notifications when agents get stuck (280666), lack of output or UI updates after delegating tasks to cloud agents (281367), confusion about session progress indicators showing active when paused (280862), and missing or inconsistent session statistics after reloads (281350). These issues cause users to be unaware of session states or lose track of background work progress.
- Rate Limiting and Quota Errors: Multiple reports describe users encountering frequent "rate_limited" errors despite having paid subscriptions or remaining quota (280332, 281288, 281297, 281298, 281412, 281523), with some users also reporting being charged despite failed requests (281716). These issues disrupt workflows and cause frustration due to unexpected usage limits and billing concerns.
- UI and Layout Problems in Chat and Terminal Views: Several issues report UI glitches such as misaligned borders and padding in terminal output and chat views (280173, 280221, 281030, 281064, 281448), missing or inconsistent hover tooltips and padding in recent sessions and agent session lists (280397, 280551, 280845, 280846, 281783), and problems with chat session title bars and toolbar visibility (281067, 281150, 281274). These visual inconsistencies degrade user experience and make interface elements harder to use or understand.
- Agent and Tool Configuration and Behavior: Issues discuss problems with agent tool configurations such as the
runSubagenttool using incorrect parameter names causing functionality failures (280140), theinferproperty not respected in GitHub Copilot agents (280708), and duplicated or inconsistent tool naming and layout in custom agents (280471, 280815). These cause confusion and prevent proper agent operation or tool usage.
- Terminal and Inline Terminal Issues: Several bugs involve terminal behavior such as terminal output failing to render after reload (280184), terminal output toggle disappearing after terminal disposal (280429), horizontal scrolling glitches in inline terminals (280710), and terminal autocomplete completing incorrect commands (280943). These issues cause terminal usability problems and inconsistent output display.
- Model Picker and Agent Selection Problems: Issues report that the model picker does not appear in background chat sessions due to locking flags (281100), and that switching agents or models can cause request failures or unexpected behavior (281222, 280373). These problems limit user control over model selection and cause errors during usage.
- Performance and Memory Leaks: Reports include memory leaks caused by undisposed disposable objects in terminal capability stores and chat terminal command mirrors (280281, 281293), and inefficient diff application scanning entire files causing delays (281228). These issues degrade performance and resource usage.
- Security and Injection Concerns: One issue reports a security vulnerability involving script injection via crafted input in VS Code on macOS (281188), highlighting potential risks in input handling.
- Feature Requests and Usability Enhancements: Requests include adding preview mode support for extended Markdown footnotes (280149), a CSS/style manager tool for Vue (280176), start/end timestamps for tasks (280274), ability to revoke "Always Allow" permission for fetch tool (280345), and improved agent session search to include chat thread contents (280769). These aim to improve functionality and user experience.
- Authentication and Subscription Issues: Users report problems with authentication such as expired or invalid tokens causing failures (280256), inability to switch between individual and business Copilot subscriptions (280293), and repeated GitHub login failures preventing Copilot usage (281496). These issues block access to features and cause user frustration.
- Chat Input and Inline Chat Problems: Issues include inline chat always using minimal UI ignoring settings (280357), inline chat failing intermittently with timeouts (280697), and sending inline chat failing if main chat input is populated (280605). These limit chat interaction flexibility and cause unexpected failures.
- Miscellaneous Bugs and User Complaints: Various other issues include blank white screen after idle (280220), overheating and lag on macOS/iOS when debugging Flutter apps (280243), and user complaints about AI feature intrusiveness and extension unhelpfulness (281114, 281400, 281647). These reflect diverse user-impacting problems.
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.65 (Rapid escalation, aggressive language)
- This GitHub conversation involves a user expressing dissatisfaction with a feature request, using a terse and potentially confrontational comment. The tone is abrupt and could be perceived as dismissive, with no further elaboration or constructive feedback provided. The interaction is minimal but indicates a potential for negative exchanges if the discussion continues.
-
Keeps recommending out-of-date practices, and violating instructions
- Toxicity Score: 0.65 (Rapid escalation, user frustration, perceived unresponsiveness, demands for escalation)
- This GitHub conversation involves a user expressing growing frustration and skepticism toward GitHub Copilot's assistance in generating testing suite recommendations and progress reports. The user repeatedly questions the pace and completeness of Copilot's responses, while Copilot maintains a polite, apologetic, and cooperative tone, attempting to reassure and provide incremental results. Tension escalates as the user perceives delays and incomplete deliverables, culminating in demands for escalation and termination of the assistant. This dynamic reflects a breakdown in trust and communication between the user and the AI assistant.
-
- Toxicity Score: 0.75 (Rapid escalation, accusatory tone, threats of legal action, emotional distress)
- This GitHub conversation involves a single user expressing escalating frustration and distress over a perceived rogue agent causing significant disruptions and unauthorized actions. The tone is increasingly agitated and accusatory, with the user describing severe impacts and threats of legal action. The conversation is marked by a high level of emotional intensity and a sense of urgency, with no responses or attempts at resolution visible.
-
- Toxicity Score: 0.75 (Rapid escalation potential, offensive language, strong negative sentiment)
- This GitHub conversation consists of a single initial comment by one user expressing strong frustration and dissatisfaction with the product and its marketing approach, using harsh and offensive language. There are no responses or further interactions, so the tone remains one-sided and highly negative without escalation or moderation.
-
BUG: not enough space for displaying methods/props of object in autocomplete window
- Toxicity Score: 0.75 (Rapid escalation, aggressive language, accusatory tone)
- This GitHub conversation involves a user expressing frustration towards maintainers for prematurely closing an issue without proper consideration, using a confrontational tone. The interaction is marked by a defensive and accusatory sentiment, triggered by the perceived dismissal of the user's report as a duplicate.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, hostile tone)
- This GitHub conversation consists of a single initial comment by one user expressing extreme frustration and anger through the use of profane and aggressive language, without any responses or further interaction. The tone is highly negative and hostile, and the comment appears to be a vent rather than a constructive discussion. No other usernames or sentiments are present to moderate or escalate the conversation.
-
- Toxicity Score: 0.85 (Rapid escalation, aggressive language, profanity, no de-escalation)
- This GitHub conversation consists of a single initial comment by one user expressing extreme frustration and anger in a highly aggressive and profane tone, without any responses or further interaction.
-
- Toxicity Score: 0.95 (Rapid escalation, aggressive language, vulgar insults)
- This GitHub conversation features highly aggressive and hostile language from the original poster and a commenter, both expressing intense frustration and dissatisfaction. The tone is confrontational and vulgar, with no attempts at constructive dialogue. The tension is triggered by perceived product issues and dissatisfaction with the company behind it, leading to a rapid escalation in hostility.
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: 69
Key Open Pull Requests
1. Adding coreview for slack workspace extension: This pull request adds and refactors a Slack workspace extension for Visual Studio Code, including workspace integration, command definitions, authentication improvements, message fetching enhancements, build script updates, and overall code cleanup to support Slack-based code review functionality.
- URL: pull/281508
- Merged: No
- Associated Commits: 9252c, 97a83, 397b6, bb70d, 06714, 110fb, 673a6, 70a88, 66f2d, 4a6a5, 3aa3f, 2ec18, 6e44c, ef5b5, f7076, 3e624, a6794, 1e073, 609c4
2. Initial revision of automated release sanity checks.: This pull request introduces an initial version of automated release sanity checks that fetch release target metadata from the official update service, download the release payload, validate its SHA256 hash and Authenticode signature for Windows executables, and unpack archives as needed, with tests designed to run on target OS VMs but currently runnable anywhere, laying the groundwork for future expansion to install and verify basic release functionality.
- URL: pull/280857
- Merged: No
- Associated Commits: 90671, a1127, f4646, f6102, 30669, 1a443, 59a63, 6600d, af169, 8a119, db23f, 73a07, 0bee0, 2e9f3, 40e9a, 509f9, 716eb, 9580a
3. fix: memory leak in linkDetector: This pull request fixes a memory leak in the linkDetector.ts file by replacing the use of HTMLElement.onclick event handlers with dom.addDisposableListener('click'), which requires passing a disposable store through multiple functions, and as a result, eliminates previously detected leaks in various event listeners such as keydown, click, mouseleave, and mousemove.
- URL: pull/280204
- Merged: No
Other Open Pull Requests
- UI Consistency and Styling Improvements: Multiple pull requests focus on enhancing the visual consistency and styling of the VS Code interface. These include standardizing border radius for buttons and inputs, fixing the styling of the recent sessions list in the chat view, correcting the misalignment of the chat context add button's focus outline, and removing tabIndex from the inline edits gutter indicator to improve accessibility and keyboard navigation.
- [pull/280457, pull/280713, pull/280970, pull/280498, pull/280535, pull/280953]
- Chat Session Management and Features: Several pull requests improve chat session handling and features within VS Code. They add a session picker in the chat panel title, ensure proper restoration of chat models before opening diffs, enhance session type handling in multidiff content, add telemetry for command palette selections related to chat, and add test coverage for sidebar chat session swapping.
- [pull/281051, pull/281621, pull/281369, pull/281314, pull/281379]
- Chat View Theming and Customization: One pull request introduces a new semantic color token to customize the background color of the "Recent Sessions" section in the Chat view. This improves theming flexibility and visual distinction without affecting existing themes.
- [pull/280883]
- Chat Session Reliability and Retry Logic: A pull request adds automatic retry logic for MCP tool calls that fail due to transient connection errors, targeting tools marked safe to retry. This prevents wasted premium requests and improves chat session reliability.
- [pull/280215]
- Notebook Inline Chat Architecture Migration: One pull request migrates the notebook inline chat feature from the deprecated V1 architecture to the V2 architecture. It removes V1 controllers, unifies delegation to V2 controllers, integrates observable-based session management, and updates notebook chat actions and context keys accordingly.
- [pull/280789]
- Extension Installation and Performance Fixes: A pull request addresses extension installation hanging on WSL2 by querying extension servers in parallel and restricting local extension installation queries to the local server. This prevents delays caused by slow or unresponsive remote servers.
- [pull/280362]
- Command Registration and Debugging: One pull request prevents duplicate command registrations in the chat sessions extension by skipping contributions with display names ending in "Chat" and preferring "Agent" variants, while adding trace logging for debugging.
- [pull/280382]
- Terminal Quick Suggestions Configuration: A pull request introduces a new configurable setting to delay terminal quick suggestions, preventing the autocomplete list from appearing immediately on the first keystroke and reducing distraction for experienced users.
- [pull/280406]
- Diff Editor Stability Fixes: One pull request fixes a crash in the diff editor when the experimental showMoves feature is enabled by adding proper bounds checks and includes a test fixture reproducing the issue.
- [pull/280498]
- Git Extension Push Behavior Update: A pull request modifies the Git extension's push command to respect the
push.default=currentconfiguration, pushing to a remote branch with the same name as the local branch instead of the configured upstream branch. - [pull/281486]
- Chat Widget Layout Investigation: One pull request investigates flickering and cutoff issues of the "Changed files" widget in the VS Code chat when opening completed cloud sessions. The initial fix was reverted and further investigation is ongoing.
- [pull/281646]
- Codebase Refactoring for Maintainability: A pull request extracts helper type definitions and interfaces from
settingsWidgets.tsinto a newsettingsWidgetsTypes.tsfile to improve code organization and maintainability, updating imports and re-exports to avoid forward reference issues. - [pull/281379]
- Memory Leak Fix in Extension Icon Widget: One pull request fixes a memory leak by replacing the use of
this.iconElement.onloadwithaddDisposableListenerto prevent accumulation of load event listeners when toggling the extension search view multiple times. - [pull/280566]
- Documentation Update for Branding: A pull request updates the README.md file by replacing references to "Twitter" with "X" to align with the platform's rebranding, specifically modifying the "Follow @code" text.
- [pull/280235]
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: 311
Key Closed Pull Requests
1. Chat view improvements: This pull request improves the chat view in the VSCode project by adding and refining agent session management features, updating UI elements such as icons and sidebar widths, fixing serialization and status update issues, and enhancing styling and session viewer actions to address multiple related issues.
- URL: pull/281447
- Merged: Yes
- Associated Commits: 70149, 352b2, 32eb5, c1fb1, 1757d, bdc52, e1403, 48594, b8f48, e8809, d158a, 6c06c, baf01, 4b8db, b0912, 00c54, 146fe
2. Add background color for agent sessions in chat view: This pull request proposes adding a background color to the agent session list and updating the styles of the agent sessions viewer and title container in the chat view to enhance visual distinction and improve integration with existing styles.
- URL: pull/281268
- Merged: No
3. sessions: make 'apply changes' show in working set multidiff: This pull request proposes making the "apply changes" action visible within the working set multidiff interface to improve session management and change application workflows.
- URL: pull/281644
- Merged: No
Other Closed Pull Requests
- Multidiff and Diff Editor Enhancements: Multiple pull requests improve multidiff functionality and the multi-diff editor experience by adding features such as per-request diffs, reference counting, race condition fixes, and UI refinements like avoiding redundant buttons and better content menu overlays. These changes enhance background session diffs and streamline user interaction with diff tools.
[pull/280813, pull/281431]
- Agent Sessions Integration and Improvements: Several pull requests focus on integrating and enhancing the agent sessions view within the chat interface, including embedding the sessions view directly into chat, improving CSS and UI elements, enabling session type display, and adding inline installation recommendations for alternative chat agents. These updates collectively improve session management and user experience in chat-related features.
[pull/281042, pull/280672, pull/281208, pull/280738]
- Chat Session Features and Metadata: Pull requests introduce new APIs and metadata handling for chat sessions, such as notifications for option changes, storing session statistics in metadata for efficient display, and implementing automatic panel chat exit behavior after delegation. These changes improve chat session tracking and lifecycle management.
[pull/281028, pull/281383, pull/280384]
- Terminal and Background Session Fixes: Fixes include ensuring command output remains toggleable after terminal termination by using snapshots and clearing buffers, as well as resolving issues with automatic approval processes for terminals running in background sessions. These updates stabilize terminal behavior and background session handling.
[pull/280442, pull/281333]
- Memory and Resource Leak Fixes: Pull requests address memory leaks and disposable resource management by properly disposing of composite bar actions and fixing other disposable leaks, preventing accumulation of unused objects and improving resource cleanup.
[pull/280659, pull/281295]
- Source Control Management (SCM) Logic Reversion: One pull request reverts the method of computing incoming and outgoing changes in SCM back to using history item view models, undoing a previous change to restore prior logic.
[pull/281301]
- Fetch Tool Enhancements and Fixes: Updates to the fetch tool include adding a fallback to extract content from pages when accessibility trees fail, returning error responses when no content is found, and fixing request headers to prevent redirects for specific sites like nytimes.com. These improvements enhance content extraction reliability.
[pull/281325, pull/281333]
- OAuth Metadata Resolution Improvements: A pull request clarifies and improves OAuth metadata resolution by explicitly handling multiple scenarios involving Protected Resource Metadata and Authorization Server URLs, adding fallback logic, helper functions for header handling, and enhanced logging, supported by new tests.
[pull/280234]
- Custom Chat Mode Name Collision Fixes: Fixes address issues with name collisions in custom chat modes where agents with identical names but different IDs exist across folders or after moving files, ensuring proper handling of these scenarios.
[pull/280421]
- Notebook and Inline Chat Simplification: A pull request transitions all notebook edits to use a unified v2 inline chat implementation, removing conditional routing and notebook-specific context keys, simplifying controller logic, and unifying context key expressions across editors.
[pull/280651]
- Suggest Widget Placement and UI Adjustments: Enhancements include adding a NORTH placement option for the suggest details widget to avoid overlap, conditional vertical placement logic, updated positioning calculations, sash resizing support, and typo fixes, improving the suggest widget's usability.
[pull/281210]
- Rename Refactoring and UX Enhancements: Pull requests improve rename refactoring accuracy by integrating a server plugin for rename checks and enhance the user experience with additional state properties, alternative inline edit actions, and updated styles and context keys.
[pull/280171, pull/280159]
- Worktree Changes Application: One pull request implements functionality to apply and file changes within a worktree, including iterative development, menu integration, and test fixes, successfully merging this feature.
[pull/281410]
- Data Prompt Conversion to Custom Agent: A pull request converts the
/dataprompt into a custom agent by renaming and updating its format with standard frontmatter while preserving existing workflows and formatting, improving management of complex data analysis workflows.
[pull/280651]
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 | 379 | 82 | 0 | 685 |
| bpasero | 330 | 54 | 85 | 228 |
| meganrogge | 286 | 33 | 49 | 150 |
| roblourens | 103 | 9 | 69 | 207 |
| joshspicer | 143 | 25 | 8 | 56 |
| connor4312 | 87 | 17 | 22 | 98 |
| lszomoru | 104 | 15 | 14 | 60 |
| mjbvz | 109 | 6 | 20 | 46 |
| jrieken | 50 | 11 | 39 | 75 |
| TylerLeonhardt | 24 | 6 | 30 | 109 |