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

June 2021 (version 1.58)

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

There are a number of updates in this version that we hope you will like, some of the key highlights include: Terminals in the editor - Create or move terminals into the editor area. Workspace Trust - Quickly customize Workspace Trust settings, disable Restricted Mode banner. Editor scroll bar customization - Set bar visibility and width, click navigation behavior. Markdown preview KaTeX support - Math support in the Markdown preview.

Settings editor improvements - Support for multiple checkboxes and enumeration dropdowns. Sticky debug environment choice - Debugger remembers your previous environment choice. Jupyter Interactive window - Run Jupyter code directly in an interactive window. Jupyter notebook debugging - Debug Jupyter notebook code from within VS Code. Data Science tutorials - Learn about Jupyter Notebooks, PyTorch, and more. 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, July 13 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 Workspace Trust The Workspace Trust feature was a big change that came in the 1.57 release and we believe it is important that developers can safely browse code, even when they are unfamiliar with the source.

This milestone we've been absorbing customer feedback and have focused on fixing issues and following up on suggestions. In order to help people discover the user settings that can customize Workspace Trust , there is a new Configure your settings action in the header of the Workspace Trust editor. This action will bring up the Settings editor filtered by @tag:workspaceTrust . Speaking of settings, there is a new setting to configure when the banner appears indicating that the current window is in Restricted Mode.

Similar to the security.workspace.trust.startupPrompt setting, the new security.workspace.trust.banner allows you to disable the banner after you've become familiar with the Workspace Trust feature and don't need a reminder that you are working in Restricted Mode. By default, this banner shows once per workspace and remains until it is dismissed ( "untilDismissed" ). The other options for displaying the Restricted Mode banner are "always" and "never" .

You can learn more about the rationale and development of Workspace Trust in the recent Workspace Trust blog post . The post explains how Restricted Mode helps protect you from unintended, and potentially malicious, code execution and has tips to set up your development machines so you can work both quickly and safely. Settings editor This iteration adds support to the Settings editor for settings objects with a fixed number of Boolean properties, by rendering the properties as a list of checkboxes.

This iteration also adds additional support for arrays of enumerations, by using dropdowns in editing mode instead of plain textboxes. Transient workspaces There is now a new flavor of workspace, called a "transient" workspace, that behaves differently than usual workspaces, specifically: Restarting or reloading VS Code will not attempt to open the workspace again. Workspaces set as transient do not show up in the list of recently opened workspaces.

Designate a transient workspace by adding the transient property set to true in the workspace .code-workspace file: { "folders" : [], "transient" : true } Settings Sync There is now a Troubleshoot view for Settings Sync that contains all logs and the last sync states. You can access this view by running the command Settings Sync: Show Synced Data and enabling it by opening the Views submenu and checking Troubleshoot : Theme: GitHub Light Theme Search max results setting There is a new setting, search.maxResults , which lets you set the maximum number of text search results.

The default is 20,000, up from 10,000 previously. You may see some slowness when loading a very large number of search results. Integrated Terminal Terminals in the editor area Terminals can now be created in or moved to the editor area, enabling a multi-dimensional grid layout that persists and remains visible regardless of panel state. To use terminals in the editor area, there are several options: Create via the Create Terminal in Editor Area command.

Drag and drop a terminal from the tabs list to the editor. Run Move Terminal into Editor Area with a terminal focused. Select Move into Editor Area on the terminal tab context menu. The new terminal.integrated.defaultLocation setting can be set to editor to direct newly created terminals to the editor area by default. Explicitly setting canvas renderer In a prior iteration, we enabled the WebGL terminal renderer by default and replaced the terminal.integrated.rendererType setting with the simpler terminal.integrated.gpuAcceleration .

Unfortunately, some machines see degraded experience with WebGL and the only option available was to disable GPU acceleration all together and move to the much slower DOM-based renderer. terminal.integrated.gpuAcceleration can now be set explicitly to canvas , which may be preferable for these environments. Hide link hovers The new terminal.integrated.showLinkHover setting lets you disable link hovers in the terminal.

This can be useful if you find hovers on terminal links distracting. Editor Editor scroll bar customization There are new settings to customize the editor's scroll bars: Control scroll bar visibility using editor.scrollbar.horizontal and editor.scrollbar.vertical . Change their thickness with editor.scrollbar.horizontalScrollbarSize and editor.scrollbar.verticalScrollbarSize . Determine whether clicking scrolls by page or jumps to the click position (default behavior) using editor.scrollbar.scrollByPage .

Below the editor's vertical scroll bar width is set to 30 pixels. Languages Math formula rendering in the Markdown preview VS Code's built-in Markdown preview can now render math equations using KaTeX . Inline math equations are wrapped in single dollar signs: Inline math: $x^2$ You can create a math equation block with double dollar signs: Math block: $$ \displaystyle \left( \sum_{k=1}^n a_k b_k \right)^2 \leq \left( \sum_{k=1}^n a_k^2 \right) \left( \sum_{k=1}^n b_k^2 \right) $$ You can set "markdown.math.enabled": false to disable this feature.

Markdown math formula syntax highlighting VS Code also now supports highlighting of math equations in Markdown source: This works both in normal Markdown files and in Markdown cells inside notebooks. TypeScript 4.3.5 We now bundle TS 4.3.5. This minor update fixes a few important bugs, including auto imports not working in JSX . Debugging Remember chosen environment per file When debugging is started without a launch.json file, VS Code looks at the active editor and based on the language mode of the editor decides what debug extension to use.

However, for some languages, multiple debug extensions are possible, and in that case, VS Code prompts you to choose one of them. To make debugging smoother, VS Code now remembers the chosen debugger per file, so that the next time you start debugging, the session starts without any prompts. In the short video below, the user selects the Node.js debug environment for debugging a single JavaScript file and that choice is remembered when a new debug session starts for that file.

Debug console suggestions no longer accepted on Ente

The rest of this page is on the live site.