January 2025 (version 1.97)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. January 2025 (version 1.97) Update 1.97.1 : The update addresses these security issues . Update 1.97.2 : The update addresses these issues . Downloads for 1.97.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the January 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: Next Edit Suggestions (preview) - Copilot predicts the next edit you are likely to make. Reposition Command Palette - Drag the Command Palette and Quick Inputs to a new position. Auto accept edits - Automatically accept edits from Copilot after a configurable timeout. Extension publisher trust - Keep your environment secure with extension publisher trust.
Compound logs - Combine multiple logs into a single, aggregated log view. Filter output logs - Filter the contents of the Output panel. Git blame information - Rich git blame information and open on GitHub. Search values in debug variables - Filter and search for specific values in debug variables. Notebook inline values - View inline values for code cell variables in notebooks. Python no-config debug - Quickly debug a Python script or module without setup.
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. GitHub Copilot Copilot Next Edit Suggestions (Preview) Setting : github.copilot.nextEditSuggestions.enabled Open in VS Code Open in VS Code Insiders GitHub Copilot code completions are great at autocomplete, but since most coding activity is editing existing code, it's a natural evolution of completions to also help with edits.
So, we're excited to release a new preview feature, Copilot Next Edit Suggestions (Copilot NES). Based on the edits you're making, Copilot NES both predicts the location of the next edit you'll want to make and what that edit should be. NES suggests future changes relevant to your current work, and you can simply Tab to quickly navigate and accept suggestions. Notice in the following example that changing a variable triggers an edit suggestion further down the file.
Just use the Tab key to navigate and accept the suggestion. The gutter indicator will guide you to your next edit suggestion. Enable Copilot NES via the VS Code setting github.copilot.nextEditSuggestions.enabled Open in VS Code Open in VS Code Insiders . Based on the size and type of edit, the rendering of the suggestion might change dynamically from side-by-side to below the current line. Configure the editor.inlineSuggest.edits.renderSideBySide Open in VS Code Open in VS Code Insiders setting to always render suggestions below the current line.
Copilot NES is rapidly evolving, and we can't wait to get your feedback via issues in our repo . You can read our full Copilot NES docs for more information and scenarios as we expand the NES experience. Note : If you are a Copilot Business or Enterprise user, an administrator of your organization must opt in to the use of Copilot "Editor Preview Features," in addition to you setting github.copilot.nextEditSuggestions.enabled Open in VS Code Open in VS Code Insiders in your editor.
Copilot Edits Copilot Edits general availability In our VS Code October release, we announced the preview of Copilot Edits. Today, we're now announcing the general availability of Copilot Edits! Copilot Edits is optimized for code editing and enables you to make code changes across multiple files in your workspace, directly from chat. Improved editor controls Edits can now be accepted and discarded individually, giving you more control.
Also new is that the editor controls for edits remain visible when switching to the side-by-side view. This is useful for understanding larger changes. Theme: GitHub Light Colorblind (Beta) (preview on vscode.dev ) Lastly, we have added a new setting for automatically accepting edit suggestions after a configurable timeout. The setting for that is chat.editing.autoAcceptDelay Open in VS Code Open in VS Code Insiders , which specifies the number of seconds after which changes are accepted.
The countdown stops when you interact with the accept button or when you start to review changes. This should be familiar to anyone who binge-watches on the weekends. Theme: GitHub Light Colorblind (Beta) (preview on vscode.dev ) Apply in editor In Copilot Chat, any code block can be applied to a file in the workspace by using the Apply to Editor action in the toolbar of the code block. We made several improvements to this experience: The hover of the action now shows the file the code block was generated for.
If the code block is for a non-existent file, you are prompted where to create the file. This can be at a file path suggested by Copilot, in an untitled editor, or in the currently active editor. When the changes are computed and applied, the same flow and UI as for Copilot Edits are used. You can review, improve, or discard each change individually. Temporal context Temporal context helps when editing or generating code by informing the language model about files that you have recently interacted with.
We are experimenting and measuring its effectiveness but it can also be enabled manually, github.copilot.chat.editor.temporalContext.enabled Open in VS Code Open in VS Code Insiders for Inline Chat and github.copilot.chat.edits.temporalContext.enabled Open in VS Code Open in VS Code Insiders for Copilot Edits. Workspace index status UI When you ask Copilot a question about the code in your project by using @workspace or #codebase , we use an index to quickly and accurately search your codebase for relevant code snippets to include as context.
This index can either be a remote index managed by GitHub , a locally stored index , or a basic index used as a fallback for large projects that can't use a remote index. This iteration, we've added the new workspace index to the language status indicator in the Status Bar that shows the type of index being used by Copilot and related information, such as the number of files being reindexed. To see this, just select the {} icon in the VS Code Status Bar.
Check out the Copilot workspace docs for more info about the types of workspace indexes and how you can switch between them. Build a remote workspace index Remote workspace indexes are managed by GitHub. A remote index can provide high-quality results quickly, even for large projects. They also only have to be built once per GitHub project, instead of once per user. Given all these advantages, we have added several new ways to upgrade a project to a remote index: Run the new GitHub Copilot: Build Remote Index command.
Select the Build Index button in the workspace index status UI . This only shows up if your project is eligible for remote indexing. Select the Build Index button in the first @workspace response you see. This only shows up if your project is eligible and also only shows once per workspace. Keep in mind that only projects with a GitHub remote can currently use a remote index. It may also take some time to build up the remote index, especially if your project is large.
Check the Workspace index status UI to see if remote indexing has completed. Workspace search improvements We've also continued optimizing code search for @workspace and #codebase . Highlights include: Improved tracking and handling of locally changed files when using a remote index . Added background updating of changed files in the local index , so that @workspace questions don't have to wait for them to be updated.
Optimized the basic index for large projects. Git changes context variable When writing queries for Chat or Edits, you can now reference files that were modified in G
The rest of this page is on the live site.