November 2023 (version 1.85)
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. November 2023 (version 1.85) Update 1.85.1 : The update addresses these issues . Update 1.85.2 : The update addresses these issues . Downloads for 1.85.2 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Welcome to the November 2023 release of Visual Studio Code.
There are many updates in this version that we hope you'll like, some of the key highlights include: Floating editor windows - Drag and drop editors onto your desktop. Accessible View workflow - Smoother transitions to and from the Accessible View. Finer extension update control - Choose which extensions to auto update. Source Control incoming and outgoing view - Easily review pending repository changes. JavaScript heap snapshots - Visualize heap snapshots including memory object graphs.
TypeScript Go to Definition from inlay hints - Jump to definition from inlay hint hovers. Python type hierarchy display - Quickly review and navigate complex type relationships. GitHub Copilot updates - Inline chat improvements, Rust code explanation. Preview: expanded Sticky Scroll support - Sticky Scroll in tree views and the terminal. 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 Universe, Copilot, and VS Code If you were able to watch or attend GitHub Universe this year, you saw that GitHub Copilot was center stage. Copilot was featured in the Opening Keynote and breakout sessions such as GitHub Copilot: the AI pair programmer for today and tomorrow .
The VS Code team has been working hard to integrate Copilot into the editor and you can learn more about the team's progress leading up to GitHub Universe in the recent Pursuit of "wicked smartness" in VS Code blog post. The post details the development of Copilot Chat agents , that behave as subject matter experts on code bases and technologies, and describes how extension authors will be able to contribute their own custom agents to VS Code.
Accessibility Accessible View Last iteration, we introduced automatic closing of the Accessible View when a key is pressed for a seamless flow between a UI component and its Accessible View. In some cases, this behavior might not be desirable and can now be disabled via the accessibility.accessibleView.closeOnKeyPress setting. If you find yourself toggling between the terminal and the terminal's Accessible View, you might want to enable terminal.integrated.accessibleViewFocusOnCommandExecution , which automatically opens the Accessible View after a command is executed in the terminal.
Tooltips shown on keyboard focus To improve the experience for keyboard users, tooltips are now shown on keyboard focus for items with custom hovers such as Activity Bar and Status Bar items. Speech detection timeout A new setting accessibility.voice.speechTimeout controls how long to wait during silence before accepting speech input, for example to Copilot Chat. By default, voice input is automatically submitted after 1.2 seconds of silence.
You can set this to 0 to disable accepting speech input entirely. Workbench Floating editor windows We are happy to announce that with this release you can move editors out of the main window into their own lightweight windows. Changes to an editor in one window apply immediately to all other windows where the editor is open. The easiest way to create a floating editor window is to drag an editor out of the current window and drop it on an empty space on your desktop: Theme: GitHub Dark (preview on vscode.dev ) The new workbench.editor.dragToOpenWindow setting can disable this behavior.
There are also new global and contextual commands to move or copy editors and editor groups into their own windows: View: Copy Editor into New Window ( workbench.action.editor.copyWithSyntaxHighlightingAction ) View: Move Editor into New Window ( workbench.action.editor.moveEditorToNextWindow ) View: Copy Editor Group into New Window ( workbench.action.editor.copyGroupToNextWindow ) View: Move Editor Group into New Window ( workbench.action.editor.moveGroupToNextWindow ) View: New Empty Editor Window ( workbench.action.newWindow ) The editor area in floating windows can be arranged with any complex layout that you want.
And since both terminals and search results can be opened as editors, you can now have these features in separate windows as well! Give this new feature a try and report back any issues you encounter. Make sure to review our existing issues and cast your vote on missing features. Native paste support in the File Explorer VS Code now supports natively pasting files from your operating system's Explorer into the VS Code File Explorer.
Extension auto update control You can now choose which extensions to auto update. This is helpful if you do not want to auto update all extensions but selectively choose which ones to auto update. You can either select an extension or all extensions from a publisher. If you choose to auto update all extensions from a publisher, you can then unselect individual extensions from that publisher. You should have auto updates either disabled ( None ) or enabled for selected extensions ( Selected Extensions ) to use this feature.
New Profile icons The following new Profile icons are available to add to your profiles. vr piano coffee snake robot game chip music Settings editor search improvements and bug fixes The Settings editor is back to sorting search results by match type first, rather than only by the table of contents. In other words, title and keyword matches show up at the top, so you don't have to scroll down to find a setting with a matching title.
Theme: Light Pink (preview on vscode.dev ) The Settings editor still orders settings by the table of contents for tie-breakers, meaning that extension authors' order keys are respected for search queries such as @ext:<extension-id> . Many Settings editor regressions were also fixed this iteration, including the Settings editor failing to load due to network issues and hanging on certain search queries. Editor Code Actions on Save and Auto You can now enable Code Actions on Auto Save in the editor, and Editor: Code Actions On Save (editor.codeActionsOnSave) settings have been migrated over to corresponding enum values.
When set to always , Code Actions can be run when you save or Auto Save with window change ( onWindowChange ) or focus change ( onFocusChange ). To enable this feature, check Editor: Code Actions On Save (editor.codeActionsOnSave) and change each Code Action's setting to always . The setting value updates are as follows, with the previous boolean values to be deprecated in favor of the string equivalent. The options are: explicit - Triggers Code Actions when explicitly saved.
Same as true . always - Triggers Code Actions when explicitly saved and on Auto Saves from window or focus changes. never - Never triggers Code Actions on save. Same as false . Multi document highlighting Multi document highlighting has additional support from a new proposed MultiDocumentHighlightProvider API. There is now built-in support for semantic occurrence highlighting for the TypeScript language that can be enabled by changing the Editor: Occurrences Highlight ( editor.occurrencesHighlight ) setting value from singleFile to multiFile .
For languages besides TypeScript, multi document occurrences are highlighted based off of textual occurrences rather than semantic occurrences until more language-specific providers are implemented. Source Control Incoming/Outgoing changes This milestone we have introduced a new Incoming/Outgoing section in the Source Control view to display incoming and outgoing changes for the current branch compared to its remote. The new sectio
The rest of this page is on the live site.