This repository was archived by the owner on Sep 15, 2025. It is now read-only.
update #1
Open
update #1
+313,796
−165,192
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We generally don't want services exposing providers in their api. Instead we can use `getChatSessionItems` for this
…onPickerActionItem.ts
* Support UX for parallel subagents Similar to thinking ux * Show prompt when expanded as well * Add ellipsis * Fix unit test * Get subagents working with tool streaming changes * Fixes * Just keep this the same, close enough
…essionPickerActionItem.css Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…oup-visuals Fix locked optionGroup display in chat input - show grayed out, non-clickable
* Initial plan * Change agents control to open quick chat instead of toggling sidebar Co-authored-by: joshspicer <23246594+joshspicer@users.noreply.github.com> * toggle quick chat --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: joshspicer <23246594+joshspicer@users.noreply.github.com>
Harden handling of old timing info
Looks like this broke when we finalize an API
* change how we draw their attention * more
* chore: bump native-watchdog * Rename more instances * chore: update Debian x64 dep list
…der failures (#287798) * feat: expose gpu log messages as part of --status This is useful in scenarios where the application rendering completely breaks and we want to know the health of gpu process on demand without having to restart the application. The log messages are usually available on demand via Developer: Show GPU Info page but during complete rendering failure the developer page will also fail to render. * feat: add support for argv.json switch to recover from failure * chore: address feedback * chore: update build * chore: bump distro
Bumps [undici](https://github.com/nodejs/undici) from 7.9.0 to 7.18.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.9.0...v7.18.2) --- updated-dependencies: - dependency-name: undici dependency-version: 7.18.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Simplify the logic and avoid layout thrashing when we would layout multiple times
Address copilot comments in #288641
* Lazy render collapsed thinking group parts Fix #287176 * re-comment * Update src/vs/workbench/contrib/chat/browser/widget/chatContentParts/chatThinkingContentPart.ts Co-authored-by: Justin Chen <54879025+justschen@users.noreply.github.com> * - In fixedScrolling mode, need to make sure we know that the part is not streaming before rendering it, so that we don't render the tool parts then immediate finalize and collapse the group - Diffing with lazily created tool parts is a bit weird, led to rendering extra tool parts at the bottom of the response. One thing I added to help with this is clearing out all rendered parts when a new model is swapped in. I wanted to do this anyway because keeping all those parts around can lead to leaks. --------- Co-authored-by: Justin Chen <54879025+justschen@users.noreply.github.com>
Only show the request/response, don't show any of the previous response. This looks cleaner, part of #274099. Also, measuring from the top means that we don't shift the response up and down when expanding the list of edited files (if the response is shorter than the minimum)
* Fix error in chatwidget setup Leftover from #288653 * Also remove this unneeded layout call that runs too often
…/unarchive (#288449) * Initial plan * Add multi-select support for agent session mark read/unread and archive/unarchive operations Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com> * polish --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: bpasero <900690+bpasero@users.noreply.github.com> Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com> Co-authored-by: Benjamin Pasero <benjamin.pasero@microsoft.com>
* Initial plan * Fix default log level not applied to extensions correctly The issue was in extHostOutput.ts where getLogLevel() always returns a value (never undefined) because it falls back to the global default. This was overriding the extension-specific default log level. Changed to only override if there's an explicitly set log level for that logger resource using getRegisteredLogger() which returns the ILoggerResource with logLevel as undefined when using default. Co-authored-by: ulugbekna <16353531+ulugbekna@users.noreply.github.com> * Improve comment clarity based on code review feedback Co-authored-by: ulugbekna <16353531+ulugbekna@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ulugbekna <16353531+ulugbekna@users.noreply.github.com>
…88427) * Initial plan * Fix: convert query to revealSetting when opening JSON settings editor Co-authored-by: sandy081 <10746682+sandy081@users.noreply.github.com> * Check for @id: prefix before using query as setting key Co-authored-by: sandy081 <10746682+sandy081@users.noreply.github.com> * Remove build-output.log and add to gitignore Co-authored-by: sandy081 <10746682+sandy081@users.noreply.github.com> * clean up --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: sandy081 <10746682+sandy081@users.noreply.github.com> Co-authored-by: Sandeep Somavarapu <sasomava@microsoft.com>
#269294 use default account in chat entitlements service
…animation frame in NativeEditContext and TextAreaEditContext (#285906) Co-authored-by: Alexandru Dima <alexdima@microsoft.com>
…ith a bullet list (#288113) * Initial plan * Fix excessive top padding in chat request bubble when user replies with a bullet list Co-authored-by: joaomoreno <22350+joaomoreno@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: joaomoreno <22350+joaomoreno@users.noreply.github.com>
Move continue chat into agent type picker
Remove chat_enabled flag
* feat: enabled windows version update for stable * chore: update setup file * temp: bump distro * chore: fix electron re-download * fix: oss callsite in updateservice * chore: simplify check in tunnel-forwarding
* Add tooltip to chat context item Part of #280658 * Copilot feedback
) * Initial plan * Don't persist extension contributed chat contexts across reload Filter out IChatRequestStringVariableEntry and IChatRequestImplicitVariableEntry with StringChatContextValue values during serialization as these have handles that become invalid after window reload. Fixes #280380 Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: alexr00 <38270282+alexr00@users.noreply.github.com>
* chat - end the log spam when reading from disk * . * Update src/vs/workbench/contrib/chat/common/model/chatSessionStore.ts Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…sion (#288889) * agents - fix regression with projection not applying when opening session * limit to setting only * .
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.