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

April 2025 (version 1.100)

🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. April 2025 (version 1.100) Release date: May 8, 2025 Update : Enable Next Edit Suggestions (NES) by default in VS Code Stable ( more... ). Update 1.100.1 : The update addresses these security issues . Update 1.100.2 : The update addresses these issues . Update 1.100.3 : The update addresses these issues .

Downloads for 1.100.3 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the April 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 Custom instructions and reusable prompts ( more... ). Smarter results with tools for GitHub, extensions, and notebooks ( more... ). Image and Streamable HTTP support for MCP ( more... ).

Chat performance Faster responses on repeat chat requests ( more... ). Faster edits in agent mode ( more... ). Editor experience Improved multi-window support for chat and editors ( more... ). Staged changes now easier to identify ( 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 Prompt and instructions files You can tailor your AI experience in VS Code to your specific coding practices and technology stack by using Markdown-based instructions and prompt files. We've aligned the implementation and usage of these two related concepts, however they each have distinct purposes. Instructions files Setting : chat.instructionsFilesLocations Open in VS Code Open in VS Code Insiders Instructions files (also known as custom instructions or rules) provide a way to describe common guidelines and context for the AI model in a Markdown file, such as code style rules, or which frameworks to use.

Instructions files are not standalone chat requests, but rather provide context that you can apply to a chat request. Instructions files use the .instructions.md file suffix. They can be located in your user data folder or in the workspace. The chat.instructionsFilesLocations Open in VS Code Open in VS Code Insiders setting lists the folders that contain instruction files. You can manually attach instructions to a specific chat request, or they can be automatically added: To add them manually, use the Add Context button in the Chat view, and then select Instructions... .

Alternatively use the Chat: Attach Instructions... command from the Command Palette. This brings up a picker that lets you select existing instructions files or create a new one to attach. To automatically add instructions to a prompt, add the applyTo Front Matter header to the instructions file to indicate which files the instructions apply to. If a chat request contains a file that matches the given glob pattern, the instructions file is automatically attached.

The following example provides instructions for TypeScript files ( applyTo: '**/*.ts' ): --- applyTo : '**/*.ts' --- Place curly braces on separate lines for multi-line blocks: if (condition) { doSomething(); } else { doSomethingElse(); } You can create instruction files with the Chat: New Instructions File... command. Moreover, the files created in the user data folder can be automatically synchronized across multiple user machines through the Settings Sync service.

Make sure to check the Prompts and Instructions option in the Backup and Sync Settings... dialog. Learn more about instruction files in our documentation. Prompt files Setting : chat.promptFilesLocations Open in VS Code Open in VS Code Insiders Prompt files describe a standalone, complete chat request, including the prompt text, chat mode, and tools to use. Prompt files are useful for creating reusable chat requests for common tasks.

For example, you can add a prompt file for creating a front-end component, or to perform a security review. Prompt files use the .prompt.md file suffix. They can be located in your user data folder or in the workspace. The chat.promptFilesLocations Open in VS Code Open in VS Code Insiders setting lists the folder where prompt files are looked for. There are several ways to run a prompt file: Type / in the chat input field, followed by the prompt file name.

Open the prompt file in an editor and press the 'Play' button in the editor tool bar. This enables you to quickly iterate on the prompt and run it without having to switch back to the Chat view. Use the Chat: Run Prompt File... command from the Command Palette. Prompt files can have the following Front Matter metadata headers to indicate how they should be run: mode : the chat mode to use when invoking the prompt ( ask , edit , or agent mode). tools : if the mode is agent , the list of tools that are available for the prompt.

The following example shows a prompt file for generating release notes, that runs in agent mode, and can use a set of tools: --- mode : 'agent' tools : [ 'getCurrentMilestone' , 'getReleaseFeatures' , 'file_search' , 'semantic_search' , 'read_file' , 'insert_edit_into_file' , 'create_file' , 'replace_string_in_file' , 'fetch_webpage' , 'vscode_search_extensions_internal' ] --- Generate release notes for the features I worked in the current release and update them in the release notes file.

Use [ release notes writing instructions file ]( .github/instructions/release-notes-writing.instructions.md ) as a guide. To create a prompt file, use the Chat: New Prompt File... command from the Command Palette. Learn more about prompt files in our documentation. Improvements and notes Instructions and prompt files now have their own language IDs, configurable in the language mode dialog for any file open document ("Prompt" and "Instructions" respectively).

This allows, for instance, using untitled documents as temporary prompt files before saving them as files to disk. We renamed the Chat: Use Prompt command to Chat: Run Prompt . Furthermore, the command now runs the selected prompt immediately , as opposed to attaching it as chat context as it did before. Both file types now also support the description metadata in their headers, providing a common place for short and user-friendly prompt summaries.

In the future, this header is planned to be used along with the applyTo header as the rule that determines if the file needs to be auto-included with chat requests (for example, description: 'Code style rules for front-end components written in TypeScript.' ) Faster agent mode edits We've implemented support for OpenAI's apply patch editing format (GPT 4.1 and o4-mini) and Anthropic’s replace string tool (Claude Sonnet 3.7 and 3.5) in agent mode.

This means that you benefit from significantly faster edits, especially in large files. The update for OpenAI models is on by default in VS Code Insiders and gradually rolling out to Stable. The Anthropic update is available for all users in both Stable and Insiders. Base model in chat We're gradually rolling out GPT-4.1 as the default base model in chat in VS Code. You can use the model switcher in the Chat view to change to another model at any time.

Search code of a GitHub repository with the #githubRepo tool Imagine you need to ask a question about a GitHub repository, but you don't have it open in your editor. For example, you want to know how a specific function is implemented in the microsoft/vscode repository. You can now use the #githubRepo tool to search for code snippets in any GitHub repository that you have access to. This tool takes a user/repo as extra input.

For example, "how to implement factory pattern in TS #githubRepo microsoft/vscode". You can also use custom instructions to hint when and how to use this tool, as shown in the following example: --- applyTo : '**' --- Use the `#githubRepo` tool with `microsoft/vscode` to

The rest of this page is on the live site.