Ben VillalobosandGitHub 2efe62ec1b 🧹 Remove isSessionTypeVisible from ChatInputPart (#325697)
* Remove redundant hideEhCopilotCli visibility logic from session picker

The `_isVisible` override in SessionTypePickerActionItem duplicated the
Extension Host Copilot CLI hide check that isVisibleEditorChatSessionType
already performs (keyed on the same chat.editor.copilotCli.hideExtensionHost
setting). It also introduced an isSessionTypeVisible delegate hook that no
delegate ever implemented.

Restore _isVisible to the pre-#323914 one-liner that defers to the shared
isVisibleEditorChatSessionType, and drop the now-dead isSessionTypeVisible
member from the picker delegate interface. No behavior change: the hide rule
remains centralized in isVisibleEditorChatSessionType.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 53512dbc-d36f-4137-b6fe-739338b4844b

* Remove dead IAutomationSessionTypeProvider bridge

The IAutomationSessionTypeProvider abstraction was registered as a singleton
but never injected or called by anyone. It was intended as the layering seam
for a workbench-side automations UI to reach the Sessions layer, but the
automations dialog lives in vs/sessions and drives its session-type picker
(MobileSessionTypePicker) directly against ISessionsManagementService.
getSessionTypesForFolder, bypassing the bridge entirely.

Delete the interface, its IAutomationSessionTypeChoice type, the
AutomationSessionTypeProvider implementation, and the singleton
registration. No behavior change: the live path was always the sessions
picker.
2026-07-13 23:21:23 +00:00
2026-07-12 20:30:31 +00:00
2026-07-12 20:30:31 +00: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
Visual Studio Code
Readme
2.3 GiB
Languages
TypeScript 79.1%
jsonc 16.7%
CSS 1.4%
JavaScript 0.6%
C 0.6%
Other 1.3%