* ai-customizations: improve list visual scannability (#299211)
- Add type-specific icon to each list item (agent, skill, instructions, prompt, hook)
- Format item names: convert dashes/underscores to spaces and apply title case
- Truncate descriptions to first sentence (max 120 chars fallback) to reduce visual noise
- Make item name font-weight 500 so titles pop against secondary text
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: add type icon + name/description polish for MCP servers and plugins (#299211)
- Export formatDisplayName and truncateToFirstSentence helpers from aiCustomizationListWidget
- Add mcpServerIcon to McpServerItemRenderer (local + builtin items)
- Add pluginIcon to PluginInstalledItemRenderer
- Apply formatDisplayName (dash/underscore → spaces, title case) to names
- Apply truncateToFirstSentence to descriptions
- Set font-weight: 500 on mcp-server-name to match AI customization list style
- Remove left-indent padding on mcp-server-item now that the icon fills that space
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: mute group count badges (#299211)
Replace badge-background/foreground pill styling with plain descriptionForeground
text (opacity 0.8) on both the group-header count and the sidebar section count.
This lets the section label dominate visually.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: restore badge pill with reduced opacity (#299211)
Keep badge-background/foreground colors but apply opacity: 0.6 so the
pill is still visible but clearly secondary to the section label.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: use keybindingLabel tokens for count badges (#299211)
Switch from badge-background (bright accent) to keybindingLabel-background/
foreground/border tokens, which are designed for subtle inline labels.
No opacity hacks needed — the color itself is naturally muted.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: use list.inactiveSelection tokens for count badges (#299211)
Switch to list.inactiveSelectionBackground/Foreground — the semantically
closest tokens for a secondary/muted count pill in a list/tree context.
No opacity hacks needed and the name directly reflects the role.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: strip trailing .md from display names (#299211)
formatDisplayName now strips a case-insensitive .md suffix before
applying the title-case transform, so 'my-file.Md' no longer
appears as a title.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: remove explicit font-weight from item titles (#299211)
Drop the font-weight: 500 on item-name and mcp-server-name. The visual
hierarchy is already established by the 13px full-foreground title vs the
11px muted descriptionForeground description below it, without needing an
explicit weight bump.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: use star icon for built-in MCP server items (#299211)
Built-in MCP items now show builtinIcon (star) instead of mcpServerIcon,
consistent with the prompts built-in group. Icon is now set per-element
in renderElement so the two item types can show different icons.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Revert "ai-customizations: use star icon for built-in MCP server items (#299211)"
This reverts commit 6b08675a22.
* ai-customizations: use star icon for Built-in MCP group header (#299211)
Change the Built-in group header icon from extensionIcon to builtinIcon
(starFull), consistent with the Built-in group in the prompts list.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: remove unused extensionIcon import from mcpListWidget (#299211)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* prompts: add create-pr prompt with compile-check reminder
Ensures the TypeScript compile check is run before opening a PR,
catching unused import and type errors that tsgo would flag in CI.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ai-customizations: fix IMatch highlight positions for formatted names (#299211)
nameMatches are now computed against formatDisplayName(item.name) in
filterItems so highlight positions align with the displayed string.
The .md stripping in formatDisplayName changes string length, so matches
against the raw name would produce incorrect highlight spans.
Also removed the outdated '1:1 transformation' claim from the JSDoc.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Visual Studio Code - Open Source ("Code - OSS")
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, 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
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:
- Submit bugs and feature requests, and help us verify as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to additional and new content
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:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Upvote popular feature requests
- File an issue
- Connect with the extension author community on GitHub Discussions or Slack
- Follow @code and let us know what you think!
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
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.
