Text of code.visualstudio.com › updates › v1_56 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

April 2021 (version 1.56)

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. April 2021 (version 1.56) Update 1.56.1 : The update addresses these security issues . Update 1.56.2 : The update addresses these issues . Downloads for 1.56.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the April 2021 release of Visual Studio Code.

The VS Code team has been busy this month working on several longer lead time updates so check out the Preview features section to learn what's upcoming. Here are some of the highlights included in this release: Improved hover feedback - Helps you quickly find clickable editor actions. Terminal profile improvements - Create a custom default terminal profile. Debugger inline values - Display variable values inline during debugging sessions.

Notebook KaTeX support - Math support in notebook Markdown cells. Dev Containers volumes view - Manage mounted volumes within Docker containers. winget installation - VS Code is available via the Windows Package Manager. New introductory videos - Videos for getting started with VS Code as well as working with C++. Terminal tabs preview - Get a first look at managing open terminals with the new tabs view. If you'd like to read these release notes online, go to Updates on code.visualstudio.com .

Join us live at the VS Code team's livestream on Tuesday, May 11 at 8am Pacific (4pm London) to see a demo of what's new in this release, and ask us questions live. 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. Workbench Improved action hover feedback We have changed the mouse hover feedback for actions all around the workbench, to provide a better UX around clickable actions.

Untitled editors hint We have noticed that many new users are not aware that a language has to be set in order to get full VS Code language support. To help with this problem, we have introduced a hint for untitled editors to help users set the correct language mode. The untitled hint might not be helpful to advanced users, so it goes away immediately as you start typing or you can select don't show to never display the hint again.

Default custom editor and notebook resolution If you have two editors that both state they should be your default editor for a resource (for example, an image viewer and an image editor), you will receive a prompt to resolve the conflict. In the short video below, the user opens a PNG file, which is associated with two editors. The notification lets the user keep using the Luna Paint Image Editor or configure a new default, which they do and start using the binary Hex Editor.

Updated custom dialogs We have updated our custom dialog styles, which you can enable via "window.dialogStyle": "custom" . VS Code now dims the background so there is better focus on the dialog and also uses the secondary button style when there is more than one action. Product Icon Theme: Fluent Icons You can theme the secondary button style by using the following color tokens: button.secondaryBackground button.secondaryForeground button.secondaryHoverBackground Auto update only enabled extensions You can now configure VS Code to auto update only your extensions that are currently enabled.

Theme: GitHub Light Theme Terminal Profile improvements Last iteration, we introduced terminal profiles . The terminal now supports setting a default profile with the terminal.integrated.defaultProfile.<platform> settings. Environment and icon support was also added to the profiles system: "terminal.integrated.profiles.windows" : { "PowerShell" : { "source" : "PowerShell" , "overrideName" : true , "icon" : "terminal-powershell" , "env" : { "TEST_VAR" : "value" } } }, "terminal.integrated.defaultProfile.windows" : "PowerShell" , Going forward, these settings are the recommended way to switch out the default terminal configuration and the terminal.integrated.shell and terminal.integrated.shellArgs settings have been deprecated.

New terminal picker Profiles and setting shortcuts have moved out of the dropdown and into a new + button with a dropdown. This also supports creating a new split terminal based on a non-default profile. New keybindings The terminal has several new default keybindings this release: Move to previous terminal - Ctrl+PageUp (macOS Cmd+Shift+] ) Move to next terminal - Ctrl+PageDown (macOS Cmd+shift+[ ) Focus terminal tabs view - Ctrl+Shift+\ (macOS Cmd+Shift+\ ) - Terminal tabs preview As always, these default keybindings can be removed or custom keybindings can be added via the keybindings system .

Linux selection paste command The new command workbench.action.terminal.pasteSelection is available on Linux to paste into the terminal from the selection clipboard. Terminal workspace shell permissions changed In order to support incoming changes related to profiles, the prompt that would show if terminal settings were present in .vscode/settings.json was removed in favor of a setting to opt into workspace settings use.

Note that this can be dangerous in untrusted workspaces. "terminal.integrated.allowWorkspaceConfiguration" : true When Workspace Trust is enabled by default, we will remove this and use that system. Tasks Removal of Tasks 0.1.0 with upgrade Tasks 2.0.0 has been available and working well for over three years, and tasks 0.1.0 has been deprecated throughout that time. In light of our Node.js-free renderer goal, tasks 0.1.0 has been deleted rather than brought into the Node.js-free world.

When you open a folder that contains 0.1.0 tasks, they will be automatically upgraded to version 2.0.0 for you. No "Task" prefix in terminal tabs When using the new Terminal tabs feature, the "Task" prefix will no longer be added to the terminal name. Instead, tasks are indicated by the "tools" icon to make better use of the available space. Better matching with eslint-stylish The $eslint-stylish problem matcher matches multiline problems more accurately.

Debugging Breakpoints view improvements Access type is shown for data breakpoints For data breakpoints, VS Code now shows the access type ("Read", "Write", or "Access") next to its name in the Breakpoints view. Better status/error reporting for exception breakpoints For exception breakpoints, VS Code now shows their individual verification status and detailed reason in the Breakpoints view. If an exception breakpoint cannot be verified (for example because its condition contains a syntax error), it will be grayed out and, on hover, the corresponding error message is shown.

Other UI improvements Alternative behavior for Stop and Disconnect commands A debug session is typically stopped via the Debug: Stop and Debug: Disconnect commands. If the debug session is of type launch , the Stop command does not only stop the session but it also terminates the debuggee. For attach type debug sessions, there is a Disconnect command, which stops debugging and resumes execution of the debuggee. With this release, it is now possible to flip this behavior by pressing the Alt modifier while triggering the command from the Debug toolbar.

Altering the behavior makes it possible to leave the debuggee running for launch type debug sessions, and to terminate the debuggee for attach type debug sessions. Apart from using Alt with the default commands, it is also possible to access both the Debug: Stop and Debug: Disconnect commands from the Command Palette for both launch and attach debug sessions. The alternative behavior is only available for debug extensions that have opted in to this feature.

Improved flow for installing missing debug extensions We have improved the flow if a user wants to start debugging but hasn't installed the necessary language extension that provides debugging support (like Python or Java). When this happens, VS Code now prompts the user to install the appropriate exte

The rest of this page is on the live site.