Skip to content

Conversation

@dileepyavan
Copy link
Member

fixes:#291022
For linux, bubblewrap, socat and ripgrep should be installed. Updated the setting UI to show this

image

Copilot AI review requested due to automatic review settings January 28, 2026 19:15
@dileepyavan dileepyavan requested review from Tyriar and removed request for Copilot January 28, 2026 19:16
@vs-code-engineering vs-code-engineering bot added this to the January 2026 milestone Jan 28, 2026
Copilot AI review requested due to automatic review settings January 28, 2026 19:21
@dileepyavan dileepyavan enabled auto-merge (squash) January 28, 2026 19:22
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the terminal sandbox settings description for Linux to clarify required dependencies for the sandboxed terminal tool. It ensures that users are informed about necessary binaries when configuring the Linux sandbox filesystem access.

Changes:

  • Updated the TerminalSandboxLinuxFileSystem setting’s markdownDescription to mention that bubblewrap, socat, and ripgrep need to be installed for the setting to work.
  • Improved structure of the description by splitting the “applicable only when enabled” note onto its own line.
Comments suppressed due to low confidence (1)

src/vs/workbench/contrib/terminalContrib/chatAgentTools/common/terminalChatAgentToolsConfiguration.ts:546

  • In the markdown description, there's no space before **bubblewrap** (".env).**bubblewrap**"), which will render awkwardly; consider adding a space so it reads ".env). **bubblewrap**".
		markdownDescription: localize('terminalSandbox.linuxFileSystemSetting', "Note: this setting is applicable only when {0} is enabled. Controls file system access in the terminal sandbox on Linux.Paths does not support glob patterns, only literal paths (ex: ./src/, ~/.ssh, .env).**bubblewrap**, **socat** and **ripgrep** should be installed for this setting to work.", `\`#${TerminalChatAgentToolsSettingId.TerminalSandboxEnabled}#\``),

dileepyavan and others added 18 commits January 28, 2026 12:28
…/terminalChatAgentToolsConfiguration.ts

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…91370)

* chat: use ConnectionObserverElement to track template mount state

Replaces the hacky 'renderedPartsMounted' boolean with a custom element
that leverages the native connectedCallback and disconnectedCallback
lifecycle hooks to track whether parts are mounted in the DOM.

- Adds ConnectionObserverElement custom element (connection-observer) that
  fires onDidConnect and onDidDisconnect callbacks
- Updates IChatListItemTemplate to use connectionObserver element instead
  of renderedPartsMounted boolean
- Removes manual mount state management in disposeElement since the
  element's disconnectedCallback handles it automatically
- Uses native element.isConnected property to check mount state

Fixes #290903

(Commit message generated by Copilot)

* pr comments
Co-authored-by: hediet <2931520+hediet@users.noreply.github.com>
* Fix issue with runSubagent result text
It was collecting text between tool calls when it should only collect the text after the final tool calls.

And edits in subagents left behind an empty codeblock in the result text.

* Delete comment
…nt (#291390)

When the input has content, the widget now stays visible and clamps to viewport edges (respecting sticky scroll height) instead of hiding when the anchor line scrolls out of view.

Fixes #291075
…ation (#291304)

* fix: update argument for using custom source in nuget package installation

* fix tests
- Remove context menu for open in editor since there's a button now
- Faster pinch zoom
- Only pan when holding alt/option
- Fix transparent button on hover
… by quality (#291404)

* #290627 support extension management CLI to support forced versioning by quality

* feedback
* Sanity tests updates

* Revert qemu accidental change.
Feeling more confident in its current state. Let's preview this feature for stable users too
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: rzhao271 <7199958+rzhao271@users.noreply.github.com>
* smarter check for confirmation

* address some comments

* fix carousel question icon not showing

* undo commit

* undo commit 2
justschen and others added 13 commits January 28, 2026 17:11
Fixes compatibility with pre-1.104 versions where the source property
may be undefined for deserialized tool invocations. Uses optional chaining
when accessing the source property to prevent errors.

- Make source property optional in IChatToolInvocationSerialized interface
- Use optional chaining operator when checking source.type in chat renderer
- Add comment explaining the pre-1.104 compatibility requirement

Ref #288489

(Commit message generated by Copilot)
Also cancel event propegation in toggles which would cause he item to be accepted when you clicked on the the toggle.

Fixes #290775
@vs-code-engineering
Copy link

vs-code-engineering bot commented Jan 29, 2026

📬 CODENOTIFY

The following users are being notified based on files changed in this PR:

@jrieken

Matched files:

  • src/vs/workbench/contrib/inlineChat/browser/inlineChatOverlayWidget.ts

@dileepyavan dileepyavan removed the request for review from Tyriar January 29, 2026 03:51
@dileepyavan dileepyavan disabled auto-merge January 29, 2026 15:27
Copy link
Member

@jrieken jrieken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this PR shouldn't change the inlineChatOverlayWidget

@dileepyavan
Copy link
Member Author

this PR shouldn't change the inlineChatOverlayWidget

yeah just saw this, seems wrong merge. Updating it.

@dileepyavan
Copy link
Member Author

Incorrect merges and lot of merge conflicts, created a new PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.