Visual Studio Insiders release notes

Quickly jump to document tabs using industry-standard keyboard shortcuts.

You can now quickly switch to open documents using Ctrl+Numpad 1 through Ctrl+Numpad 9. Each shortcut activates the corresponding visible document tab in the active document group, making it faster to navigate between files without reaching for the mouse.

The numbering follows the document well's visual order, including both pinned and unpinned tabs. Preview tabs do not consume a shortcut slot, ensuring the numbering remains predictable. The shortcuts are scoped to the active document group, so switching groups updates the tab mapping automatically.

This behavior aligns Visual Studio with common editor conventions, making it easier to transition between development environments while maintaining a consistent keyboard-first workflow. The commands are available through keyboard customization and the command system.

📣 See feature ticket to share your feedback and continue the conversation.

Open Folder now honors workspace restoration preferences.

Visual Studio has long restored open documents and Solution Explorer state when reopening a folder. Previously, the Reopen documents on solution load and Restore Solution Explorer project hierarchy state on solution load settings only affected solution-based workflows, and Open Folder would restore the workspace regardless of those settings.

With this update, Open Folder now respects the same settings. If you disable either option, Visual Studio will no longer restore open documents or Solution Explorer state when reopening a folder.

To change these preferences, go to Tools → Options → Projects and Solutions → General and configure Reopen documents on solution load and Restore Solution Explorer project hierarchy state on solution load. The selected behavior now applies consistently to both solutions and folders.

📣 See feature ticket to share your feedback and continue the conversation.

Hot Exit preserves unsaved files & saved files with unsaved changes, so you can pick up exactly where you left off.

When you close Visual Studio, Hot Exit saves your session state. The next time you open Visual Studio, it restores your open documents, edits, and unsaved changes automatically, so you don't need to save manually.

Hot Exit is off by default. To turn it on, go to Tools → Options → Preview Features → Hot Exit.

Hot Exit preserves:

• Unsaved files.
• Saved files with unsaved changes.
• Undo functionality for saved files, including Ctrl+Z.
• Your tab and window layout.

📣 See feature ticket to share your feedback and continue the conversation.

Navigate your codebase using its physical folder structure and explore repositories from the root.

Navigate your codebase using the physical folder structure as it exists on disk. When working in a repository, File System view starts at the repository root, making it easier to explore source files, documentation, build assets, configuration files, and other content that may not appear in traditional project views.

For solutions outside a repository, File System view starts at the solution folder.

Switch Between Project and File System Views

The File System view is built directly into Solution Explorer, making it easy to switch between project-focused and file system-focused views without opening or managing additional tool windows.

Use Solution view when you want to understand your project's structure, dependencies, and loaded projects. Switch to File System view when you want to explore your repository as it exists on disk, including files and folders that are not part of the solution.

Need Both Views At Once?

For advanced workflows, use the New Solution Explorer View context menu command to open an additional Solution Explorer window.

This allows Solution view and File System view to remain open side-by-side as separate tool windows, giving you simultaneous access to both the logical organization of your solution and the physical structure of your repository.

Customize Visual Studio with a modernized Fonts and Colors experience built on Unified Settings.

Personalize Visual Studio with a modernized Fonts and Colors experience built on Unified Settings. Previously available through the legacy Tools > Options dialog, Fonts and Colors now benefits from the same settings platform used throughout Visual Studio.

The new experience introduces category-based navigation, integrated search, inline previews, and an updated color editing experience. Foreground colors, background colors, font styles, and previews are displayed directly within the settings grid, making it easier to review existing customizations and update multiple settings without repeatedly selecting individual items.

Backed by settings.json

Fonts and Colors settings now participate in Visual Studio's settings.json model. Changes made through the UI are reflected in settings.json, allowing advanced users to inspect, edit, share, or revert customizations directly through the file while keeping both experiences synchronized.

Control how long you need to hover over code before the Quick Info tooltip appears, so it doesn't get in your way when you're moving the mouse around the editor.

Hover tooltips in the editor have always appeared after a fixed 150 ms of hovering. If you move the mouse slowly, or just pass over code on your way somewhere else, that tooltip pops up over the exact line you were trying to click.

You can now set that delay yourself.

Tools → Options → Text Editor → Advanced → Quick Info hover delay (ms)

The default is 150 ms, which is the value Visual Studio has always used, so nothing changes until you change it. Valid values are 50 to 10000 ms. Turn it up if tooltips get in your way, turn it down if you want them faster.

The setting applies immediately. No restart, no reopening files.

One note on scope: this controls the delay for hover handlers that don't request a specific timing of their own, which is what Quick Info uses. Extensions that ask for an explicit hover delay keep their own behavior.

📣 See feature ticket to share your feedback and continue the conversation.

You can now make Visual Studio stop the build after the first failure, instead of continuing to build the remaining projects.

Visual Studio now includes an opt-in setting that stops a solution build after the first project failure. You can get back to fixing the error sooner instead of waiting for projects that can no longer produce a successful build.

Enable Stop solution build after first failure in Tools → Options → Projects and Solutions → Build and Run. When you enable it, Visual Studio stops starting queued projects and safely stops projects already building. The build still reports as failed, not canceled. If you leave the setting disabled, build behavior stays the same.

This improvement can be substantial for large solutions. In testing, four regular builds averaged 26 seconds with the setting disabled and 1.5 seconds with it enabled - a 94% reduction in post-failure completion time. Results vary by solution, but projects with longer dependency chains or many parallel builds are likely to benefit the most.

📣 See feature ticket to share your feedback and continue the conversation.

Rearrange document tabs using a new keyboard shortcut that makes it easier to organize your workspace.

You can now reorder the active tab in the document well without touching the mouse. Ctrl+Shift+PgUp moves the tab one visual position left, and Ctrl+Shift+PgDn moves it one position right. With vertical tabs enabled, the same shortcuts move the tab up and down instead, so the gesture stays the same whichever layout you prefer. The commands work for both documents and tool windows hosted in the document well.

Tab movement respects the structure you've already set up. Pinned and unpinned tabs keep their separation, so a tab won't jump across that boundary and quietly break your pinned set. In vertical tabs, a tab stays within its project group, and manual reordering is unavailable while alphabetical sorting is turned on. Preview tabs can't be moved.

Behind the shortcuts are two new global commands, Window.MoveTabLeft and Window.MoveTabRight, both listed in Tools → Options → Environment → Keyboard if you'd rather bind them somewhere else. The defaults take over the previous Text Editor bindings for Edit.ViewTopExtend and Edit.ViewBottomExtend; those commands are still available and can be reassigned to any shortcut you like.

Thanks to everyone who voted for this on Developer Community. Ctrl+Shift+PgUp/PgDn is the same binding most browsers use, so it should feel familiar from the first press.

📣 See feature ticket to share your feedback and continue the conversation.

If you've zoomed in or out of the editor, you can now reset the zoom level to 100% with a new keyboard shortcut.

Press Ctrl+NumPad0 to snap the editor zoom level straight back to 100%. Zoom in to inspect a dense block of code, zoom out to get a sense of a file's shape, then return to your normal view with a single keystroke.

Until now, getting back to 100% meant nudging the zoom with Ctrl+Mouse Wheel until it looked about right, or picking the value from the zoom control in the corner of the editor. That's easy to overshoot, and it's especially annoying when a sensitive mouse wheel changes the zoom without you asking. The new shortcut removes the guesswork and keeps a consistent editing view as you move between files.

The shortcut is backed by a new View.ZoomReset command. Ctrl+NumPad0 matches the binding used in VS Code and most browsers, but if you'd rather use something else, or you're on a keyboard without a number pad, you can remap it in Tools → Options → Environment → Keyboard.

📣 See feature ticket to share your feedback and continue the conversation.

You can now create a new markdown file from the New File dialog.

You can now create a Markdown file directly from the New File dialog. Press Ctrl+N, select Markdown, and start writing without manually creating a file or setting its extension.

This workflow makes it faster to create notes, documentation, and other Markdown content. It also works with Hot Exit, which restores your unsaved files when you restart Visual Studio so you can continue where you left off.

📣 See feature ticket to share your feedback and continue the conversation.

A refreshed Copilot chat, built on the Copilot SDK that powers Copilot everywhere.

There's a new Copilot chat experience in Visual Studio, built on the Copilot SDK, the same foundation that powers the Copilot CLI and the GitHub Copilot app. It's the next step in the journey that started with Agent (Preview), the first Visual Studio experience built on the SDK. Now that same foundation powers the whole chat experience, including Ask mode, Agent mode, and the underlying chat infrastructure.

Building on a shared foundation means Visual Studio gets better as Copilot gets better. When you turn it on, you get:

• More capable agent workflows that handle end-to-end tasks with less back-and-forth.
• Longer-running sessions with more effective prompt caching for better performance.
• Consistent behavior across every Copilot surface.

Turn it on

1. In Visual Studio, go to Tools → Options.
2. Go to GitHub → Copilot → Copilot Chat.
3. Check Use new Copilot chat experience.
4. Restart Visual Studio for the change to take effect.

Then use it on the work you already do: feature changes, bug fixes, refactors, and everything in between.

We'd love your feedback. If something is missing or not working, send it through Help → Send Feedback → Report a Problem so we know what to prioritize next.

Let AI take a first pass on merge conflicts, then dig into the changes from chat or the merge editor.

AI can resolve a conflict for you, or help you work through it. You decide how much to hand off.

From Copilot Chat

Select the Git Agent in Copilot Chat and try the "Resolve all merge conflicts" prompt. The agent works through the conflicts and links you to the merge editor, where you can review its resolutions in the new Result Only view before completing the merge.

From the merge editor

Prefer to stay in the merge editor? Click Auto Resolve in the toolbar to have the Git Agent resolve conflicts in place. You can also start from the Merge branches dialog and select Auto Resolve there instead of merging manually.

Tip: Click the gear icon next to Accept Merge and select Result Only to see just the resolved file. You can switch back to Mixed View, Vertical View, or Horizontal View at any time.

Tip: Want to start over? Click Restart resolutions in the Accept Merge dropdown to reset the conflict state.

Always review the proposed changes carefully before completing the merge.

Get started

Under Tools → Options → Environment → Preview Features, make sure Git Agent is enabled. To try out the new Result Only view, make sure to enable Merge: Results View.

This experience is not currently compatible with Use new Copilot chat experience under GitHub → Copilot → Copilot Chat. To try it, make sure that option is turned off.

See what's changed between a commit and your code today.

You can now compare any commit directly to your working tree, so you can see exactly what's changed since that point.

From commit history or the branch list, right-click a commit and select Compare with Working Tree. It opens a compare view where you can click through the diffs against your working tree without checking out the commit.

📣 See feature ticket to share your feedback and continue the conversation.

Skip resolving conflicts one file at a time: keep or take them all at once.

Resolving conflicts one file at a time gets old fast when a merge touches dozens of them.

In Git Changes, right-click any file, folder, or the repo root under Unmerged Changes and select Keep All Current or Take All Incoming to resolve everything underneath it in one step.

📣 See feature ticket to share your feedback and continue the conversation.