Text of code.visualstudio.com › updates › v1_102 as Styx crawled it on Oct 9, 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

June 2025 (version 1.102)

🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. June 2025 (version 1.102) Release date: July 9, 2025 Update 1.102.1 : The update addresses these issues . Update 1.102.2 : The update addresses these issues . Update 1.102.3 : The update addresses these issues . Downloads for 1.102.3 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the June 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: Chat Explore and contribute to the open sourced GitHub Copilot Chat extension ( Read our blog post ). Generate custom instructions that reflect your project's conventions ( Show more ). Use custom modes to tailor chat for tasks like planning or research ( Show more ). Automatically approve selected terminal commands ( Show more ).

Edit and resubmit previous chat requests ( Show more ). MCP MCP support is now generally available in VS Code ( Show more ). Easily install and manage MCP servers with the MCP view and gallery ( Show more ). MCP servers as first-class resources in profiles and Settings Sync ( Show more ). Editor experience Delegate tasks to Copilot coding agent and let it handle them in the background ( Show more ). Scroll the editor on middle click ( 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 Copilot Chat is open source We're excited to announce that we've open sourced the GitHub Copilot Chat extension! The source code is now available at microsoft/vscode-copilot-chat under the MIT license.

This marks a significant milestone in our commitment to transparency and community collaboration. By open sourcing the extension, we're enabling the community to: Contribute directly to the development of AI-powered chat experiences in VS Code Understand the implementation of chat modes, custom instructions, and AI integrations Build upon our work to create even better AI developer tools Participate in shaping the future of AI-assisted coding You can explore the repository to see how features like agent mode , inline chat , and MCP integration are implemented.

We welcome contributions, feedback, and collaboration from the community. To learn more about this milestone and our broader vision for open source AI editor tooling, read our detailed blog post: Open Source AI Editor - First Milestone . Chat mode improvements Last milestone, we previewed custom chat modes . In addition to the built-in chat modes 'Ask', 'Edit' and 'Agent', you can define your own chat modes with specific instructions and a set of allowed tools that you want the LLM to follow when replying to a request.

This milestone, we have made several improvements and bug fixes in this area. Configure language model Upon popular request, you can now also specify which language model should be used for a chat mode. Add the model metadata property to your chatmode.md file and provide the model identifier (we provide IntelliSense for the model info). Improved editing support The editor for chat modes , prompts , and instruction files now supports completions, validation, and hovers for all supported metadata properties.

Gear menu in the chat view The Configure Chat action in the Chat view toolbar lets you manage custom modes as well as reusable instructions, prompts, and tool sets: Selecting Modes shows all currently installed custom modes and enables you to open, create new, or delete modes. Import modes, prompts and instructions via a vscode link You can now import chat mode, reusable prompt and instruction files from external links, such as a gist or our awesome-copilot community repository.

For example, the following link will import the chat mode file for Burke's GPT 4.1 Beast Mode: Add GPT 4.1 Beast Mode to VS Code This will prompt for a destination, either your current workspace or your user settings, and confirm the name before importing the mode file from the URL. Try it out on the 100+ community-contributed instructions, prompts, and chat modes at awesome-copilot . Generate custom instructions Setting up custom instructions for your project can significantly improve AI suggestions by providing context about your coding standards and project conventions.

However, creating effective instructions from scratch might be challenging. This milestone, we're introducing the Chat: Generate Instructions command to help you bootstrap custom instructions for your workspace. Run this command from the Command Palette or the Configure menu in the Chat view, and agent mode will analyze your codebase to generate tailored instructions that reflect your project's structure, technologies, and patterns.

The command creates a copilot-instructions.md file in your .github folder or suggests improvements to existing instruction files. You can then review and customize the generated instructions to match your team's specific needs. Learn more about customizing AI responses with instructions . Load instruction files on demand Instruction files can be used to describe coding practices and project requirements. Instructions can be manually or automatically included as context to chat requests.

There are various mechanisms supported, see the Custom Instructions section in our documentation. For larger instructions that you want to include conditionally, you can use .instructions.md files in combination with glob patterns defined in the applyTo header. The file is automatically added when the glob pattern matches one or more of the files in the context of the chat. New in this release, the large language model can load instructions on demand.

Each request gets a list of all instruction files, along with glob pattern and description. In this example, the LLM has no instructions for TypeScript files explicitly added in the context. So, it looks for code style rules before creating a TypeScript file: Edit previous requests (Experimental) You can now click on previous requests to modify the text content, attached context, mode, and model. Upon submitting this change, this will remove all subsequent requests, undo any edits made, and send the new request in chat.

There will be a controlled rollout of different entry points to editing requests, which will help us gather feedback on preferential edit and undo flows. However, users can set their preferred mode with the experimental chat.editRequests Open in VS Code Open in VS Code Insiders setting: chat.editRequests.inline Open in VS Code Open in VS Code Insiders : Hover a request and select the text to begin an edit inline with the request. chat.editRequests.hover Open in VS Code Open in VS Code Insiders : Hover a request to reveal a toolbar with a button to begin an edit inline with the request. chat.editRequests.input Open in VS Code Open in VS Code Insiders : Hover a request to reveal a toolbar, which will start edits in the input box at the bottom of chat.

Terminal auto approval (Experimental) Agent mode now has a mechanism for auto approving commands in the terminal. Here's a demo of it using the defaults: There are currently two settings: the allow list and the deny list. The allow list is a list of command prefixes or regular expressions that when matched allows the command to be run without explicit approval. For example, the following will allow any command starting with npm run test to be run, as well as exactly git status or git log : "github.copilot.chat.agent.terminal.allowList" : { "npm run test" : true , "/^git (status|log)$/" : true } These settings are merged across setting scopes, such that you can have a set of user-approved commands, as well as workspace-specific approved commands.

As for chained commands, we try to d

The rest of this page is on the live site.