Sandeep Somavarapu 5bcfb040f4 sessions: support multi-session delete via session capability (#322310)
* sessions: support multi-session delete via session capability

Enable deleting multiple sessions at once and consolidate the delete
action into the sessions workbench core instead of each provider.

- Add required `deleteSessions(sessionIds)` batch API to `ISessionsProvider`
  and `deleteSessions(sessions)` to the sessions management service, which
  groups sessions by provider before delegating.
- Implement a real batch delete in the agent host base provider that
  resolves all targets synchronously up front before disposing, avoiding a
  reconcile dropping not-yet-processed cached sessions.
- Introduce a `supportsDelete` session capability and a
  `chatSessionSupportsDelete` context key, mirroring the `supportsRename`
  pattern. A single core `DeleteSessionAction` (gated on the capability)
  replaces the per-provider delete actions and the delete-session helper.
- Move the delete confirmation dialog into the action and remove it from
  the provider implementations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* sessions: address CCR feedback on multi-session delete

- Filter the action's incoming context to sessions that advertise
  `capabilities.supportsDelete`, so a mixed multi-selection never deletes
  sessions that don't support it.
- Use a singular vs plural delete error message and distinct localization
  keys instead of a plural-only message.
- Make the management service batch delete best-effort: continue deleting
  other providers' sessions if one provider rejects, then surface the first
  error. Emit `onDidDeleteSession` only for providers that succeeded.
- Clarify the `deleteSessions` JSDoc to say implementations may batch or
  delegate to `deleteSession`.
- Revert the unrelated "Copilot CLI" -> "Copilot" session type label change.
- Add a best-effort batch delete test to the management service suite.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2026-06-21 18:12:34 -07:00
2026-05-19 23:06:02 -07:00
2026-05-27 14:57:41 +02:00

Visual Studio Code - Open Source ("Code - OSS")

Feature Requests Bugs Gitter

The Repository

This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, but we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.

Visual Studio Code

VS Code in action

Visual Studio Code is a distribution of the Code - OSS repository with Microsoft-specific customizations released under a traditional Microsoft product license.

Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.

Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on Visual Studio Code's website. To get the latest releases every day, install the Insiders build.

Contributing

There are many ways in which you can participate in this project, for example:

If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:

Feedback

See our wiki for a description of each of these channels and information on some other available community-driven channels.

Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter repositories are separate from each other. For a complete list, please visit the Related Projects page on our wiki.

Bundled Extensions

VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features extension provides rich language support for JSON.

Development Container

This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.

  • For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command which creates a Docker volume for better disk I/O on macOS and Windows.

    • If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
  • For Codespaces, install the GitHub Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.

Docker / the Codespace should have at least 4 cores and 6 GB of RAM (8 GB recommended) to run a full build. See the development container README for more information.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the MIT license.

S
Description
Languages
TypeScript 77.2%
jsonc 18.5%
CSS 1.3%
JavaScript 0.7%
C 0.7%
Other 1.3%