April 2024 (version 1.89)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. April 2024 (version 1.89) Update 1.89.1 : The update addresses these issues . Downloads for 1.89.1 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the April 2024 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some of the key highlights include: Preview Markdown images & videos - Hover over a link to preview images & videos in Markdown.
Enhanced branch switching - Restore open editors seamlessly when switching between branches. Middle-click paste support - Paste text quickly in the terminal using a mouse middle-click. WSL over Remote - SSH - Use WSL when connected to a remote machine via Remote - SSH. Accessible View - Navigate through comments, chat code blocks & terminal commands from the Accessible View. Keyboard shortcuts for UI actions - Customize keybindings for UI actions directly with a right-click.
Quick Search - Search for text across your workspace with Quick Search. AI-powered rename suggestions - Get intelligent rename suggestions in the editor with Copilot. Copilot content exclusion - Exclude files from being used in the Copilot context. Local workspace extension - Include and install extensions directly in your workspace. 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. Accessibility Progress accessibility signal The setting, accessibility.signals.progress , enables screen reader users to hear progress anywhere a progress bar is presented in the user interface. The signal plays after three seconds have elapsed, and then loops every five seconds until completion of the progress bar.
Examples of when a signal might play are: when searching a workspace, while a chat response is pending, when a notebook cell is running, and more. Improved editor accessibility signals There are now separate accessibility signals for when a line has an error or warning, or when the cursor is on an error or warning. We support customizing the delay of accessibility signals when navigating between lines and columns in the editor separately.
Also, aria alert signals have a higher delay before playing them than audio cue signals. Inline suggestions no longer trigger an accessibility signal while the suggest control is shown. Accessible View The Accessible View ( ⌥F2 (Windows Alt+F2 , Linux Shift+Alt+F2 ) ) enables screen reader users to inspect workbench features. Terminal improvements Now, when you navigate to the next ( ⌥↓ (Windows, Linux Alt+Down ) ) or previous ( ⌥↑ (Windows, Linux Alt+Up ) ) command in the terminal Accessible View, you can hear if the current command failed.
This functionality can be toggled with the setting accessibility.signals.terminalCommandFailed . When this view is opened from a terminal with shell integration enabled, VS Code alerts with the terminal command line for an improved experience. Chat code block navigation When you're in the Accessible View for a chat response, you can now navigate between next ( ⌥⌘PageDown (Windows, Linux Ctrl+Alt+PageDown ) ) and previous ( ⌥⌘PageUp (Windows, Linux Ctrl+Alt+PageUp ) ) code blocks.
Comments view When there is an extension installed that is providing comments and the Comments view is focused, you can inspect and navigate between the comments in the view from within the Accessible View. Extension-provided actions that are available on the comments can also be executed from the Accessible View. Workbench Language model usage reporting For extensions that use the language model, you can now track their language model usage in the Extension Editor and Runtime Extensions Editor.
For example, you can view the number of language model requests, as demonstrated for the Copilot Chat extension in the following screenshot: Local workspace extensions Local workspace extensions, first introduced in the VS Code 1.88 release , is generally available. You can now include an extension directly in your workspace and install it only for that workspace. This feature is designed to cater to your specific workspace needs and provide a more tailored development experience.
To use this feature, you need to have your extension in the .vscode/extensions folder within your workspace. VS Code then shows this extension in the Workspace Recommendations section of the Extensions view, from where users can install it. VS Code installs this extension only for that workspace. A local workspace extension requires the user to trust the workspace before installing and running this extension. For instance, consider the vscode-selfhost-test-provider extension in the VS Code repository .
This extension plugs in test capabilities, enabling contributors to view and run tests directly within the workspace. Following screenshot shows the vscode-selfhost-test-provider extension in the Workspace Recommendations section of the Extensions view and the ability to install it. Note that you should include the unpacked extension in the .vscode/extensions folder and not the VSIX file. You can also include only sources of the extension and build it as part of your workspace setup.
Custom Editor Labels in Quick Open Last month, we introduced custom labels , which let you personalize the labels of your editor tabs. This feature is designed to help you more easily distinguish between tabs for files with the same name, such as index.tsx files. Building on that, we've extended the use of custom labels to Quick Open ( ⌘P (Windows, Linux Ctrl+P ) ). Now, you can search for your files using the custom labels you've created, making file navigation more intuitive.
Customize keybindings We've made it more straightforward to customize keybindings for user interface actions. Right-click on any action item in your workbench, and select Customize Keybinding . If the action has a when clause, it's automatically included, making it easier to set up your keybindings just the way you need them. Find in trees keybinding We have addressed an issue where the Find control was frequently being opened unintentionally for a tree control.
For example, when the Find control appears in the Explorer view instead of searching in the editor. To reduce these accidental activations, we have changed the default keybinding for opening the Find control in a tree control to ⌥⌘F (Windows, Linux Ctrl+Alt+F ) . If you prefer the previous setup, you can easily revert to the original keybinding for the list.find command using the Keyboard Shortcuts editor. Auto detect system color mode improvements If you wanted your theme to follow the color mode of your system, you could already do this by enabling the setting window.autoDetectColorScheme .
When enabled, the current theme is defined by the workbench.preferredDarkColorTheme setting when in dark mode, and the workbench.preferredLightColorTheme setting when in light mode. In that case, the workbench.colorTheme setting is then no longer considered. It is only used when window.autoDetectColorScheme is off. In this milestone, what's new is that the theme picker dialog ( Preferences: Color Theme command) is now aware of the system color mode.
Notice how the theme selection only shows dark themes when the system is in dark mode: The dialog also has a new button to directly take you to the window.autoDetectColorScheme setting: Paste Markdown links in comments In the input editor of the Comments control, pasting a link has the same behavior as pasting a link in a Markdown file. The paste options are shown and you can choose to paste a Markdown link instead of the raw link that you copied.
Source Control Save/restore open editors when switching branches This milestone, we have addressed a long-standi
The rest of this page is on the live site.