Text of code.visualstudio.com › updates › v1_101 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

May 2025 (version 1.101)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. May 2025 (version 1.101) Release date: June 12, 2025 Security update : The following extension has security updates: ms-python.python . Update 1.101.1 : The update addresses these issues . Update 1.101.2 : The update addresses these issues . Downloads for 1.101.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the May 2025 release of Visual Studio Code.

There are many updates in this version that we hope you'll like, some of the key highlights include: MCP Expand your agent coding flow with support for prompts, resources, and sampling ( Show more ). Access MCP servers that require authentication ( Show more ). Debug MCP servers with development mode ( Show more ). Publish MCP servers from an extension ( Show more ). Chat Group and manage related tools by combining them in a tool set ( Show more ).

Source Control View files in Source Control Graph view ( Show more ). Assign and track work for GitHub Copilot Coding Agent from within VS Code ( Show more ). If you'd like to read these release notes online, go to Updates on code.visualstudio.com . Insiders: Want to try new features as soon as possible? You can download the nightly Insiders build and try the latest updates as soon as they are available. Chat Chat tool sets VS Code now enables you to define tool sets, either through a proposed API or through the UI.

A tool set is a collection of different tools that can be used just like individual tools. Tool sets make it easier to group related tools together, and quickly enable or disable them in agent mode. For instance, the tool set below is for managing GitHub notifications (using the GitHub MCP server ). { "gh-news" : { "tools" : [ "list_notifications" , "dismiss_notification" , "get_notification_details" ], "description" : "Manage GH notification" , "icon" : "github-project" } } To create a tool set, run the Configure Tool Sets > Create new tool sets file command from the Command Palette.

You can then select the tools you want to include in the tool set, and provide a description and icon. To use a tool set in a chat query, reference it by #-mentioning its name, like #gh-news . You can also choose it from the tool picker in the chat input box. Learn more about tool sets in our documentation. MCP support for prompts VS Code's Model Context Protocol support now includes prompt support. Prompts can be defined by MCP servers to generate reusable snippets or tasks for the language model.

Prompts are accessible as slash / commands in chat, in the format /mcp.servername.promptname . You can enter plain text or include command output in prompt variables, and we also support completions when servers provide it. The following example shows how we generate a prompt using AI, save it using the Gistpad MCP server , and then use it to generate a changelog entry: MCP support for resources VS Code's Model Context Protocol support now includes resource support, which includes support for resource templates.

It is available in several places: Resources returned from MCP tool calls are available to the model and can be saved in chat, either via a Save button or by dragging the resource onto the Explorer view. Resources can be attached as context via the Add Context... button in chat, then selecting MCP Resources... . You can browse and view resources across servers using the MCP: Browse Resources command or for a server by its entry in the MCP: List Servers command.

Here's an example of attaching resources from the Gistpad MCP server to chat: MCP support for sampling (Experimental) VS Code's Model Context Protocol support now includes sampling, which allows MCP servers to make requests back to the model. You'll be asked to confirm the first time an MCP server makes a sampling request, and you can configure the models the MCP server has access to as well as see a request log by selecting the server in MCP: List Servers.

Sampling support is still preliminary and we plan to expand and improve it in future iterations. MCP support for auth VS Code now supports MCP servers that require authentication, allowing you to interact with an MCP server that operates on behalf of your user account for that service. This feature implements the MCP authorization specification for clients, and supports both: 2025-3-26 spec , where the MCP server behaves as an authorization server.

Draft spec , where the MCP server behaves as a resource server (this is expected to be finalized any day now). If the MCP server implements the draft spec and leverages GitHub or Entra as the auth server, you can manage which MCP servers have access to your account: You can also manage which account that server should use (via the gear button in the previous quick pick): For other MCP servers that rely on dynamic client registration, we include the auth state in the same place as everything else, for example with Linear: There you can also sign out.

For these we support not only the code authorization flow but also the device code flow should your authorization server support it. We have also introduced the command Authentication: Remove Dynamic Authentication Providers that allows you to clean up any of these dynamic client registrations. This will throw away the client id issued to VS Code and all data associated with this authentication provider. Remember, you can use the MCP: Add Server... command to add MCP servers.

This is the same entry point for servers with authentication. MCP development mode You can enable development mode for MCP servers by adding a dev key to the server config. This is an object with two properties: watch : A file glob pattern to watch for files change that will restart the MCP server. debug : Enables you to set up a debugger with the MCP server. Currently, we only support debugging Node.js and Python servers launched with node and python respectively. .vscode/mcp.json { "servers": { "gistpad": { "command": "node", "args": ["build/index.js"], + "dev": { + "watch": "build/**/*.js", + "debug": { "type": "node" } + }, Chat UX improvements We're continuously working to improve the chat user experience in VS Code based on your feedback.

One such feedback was that it can be difficult to distinguish between user messages and AI responses in the chat. To address this, we've made the appearance of user messages more distinct. Undoing previous requests is now also more visible - just hover over a request and select the X button to undo that request and any following requests. Or even quicker, use the ⌘Backspace (Windows, Linux Delete ) keyboard shortcut!

Finally, attachments from the chat input box are now more navigable. Learn more about using chat in VS Code in our documentation. Apply edits more efficiently When editing files, VS Code can take two different approaches: it either rewrites the file top to bottom or it makes multiple, smaller edits. Both approaches differ, for example the former can be slower for large files and intermediate states do often not compile successfully.

Because of that the UI adopts and conditionally disables auto-save and squiggles, but only when needed. We have also aligned the keybindings for the Keep and Undo commands. Keeping and undoing individual changes is now done with ⌘Y (Windows, Linux Ctrl+Y ) and ⌘N (Windows, Linux Ctrl+N ) . In the same spirit, we have also aligned the keybinding for keeping and undoing all changes in a file, they are now ⇧⌘Y (Windows, Linux Ctrl+Shift+Y ) and ⇧⌘N (Windows, Linux Ctrl+Shift+N ) .

This is not just for alignment but also removes prior conflicts with popular editing commands (like Delete All Left ). Implicit context We've streamlined and simplified the way that adding your current file as context works in chat. Many people found the "eyeball toggle" that we previously had to be a bit clunky. Now, your current file is offered

The rest of this page is on the live site.