Text of code.visualstudio.com › blogs › 2026 › 10 › 15 › modern-ui 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

Modernizing the VS Code UI

Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. On this page VS Code has changed a lot since its first preview in 2015 . Tabs, themes, and new ways to organize your work have made it more capable, but over a decade of adding and refining features has also introduced visual complexity and inconsistencies across the workbench. This modernization isn't about reinventing the editor.

We're refining the familiar interface to make its hierarchy clearer, reduce distractions, and give VS Code a shared design foundation that can support both editing and newer workflows such as agent sessions. The goal is a more coherent, approachable experience without giving up the density, customization, or muscle memory developers rely on. The modernized UI is available today in preview. The work began with the 2026 color themes, expanded through the Agents window, and is now shaping the editor itself.

In this post, we'll share how the modernization evolved and how your feedback continues to shape it. An interface that's always evolving Some interface changes have been small refinements. Others have introduced new ways to organize your work. Even features that now feel like part of the original editor arrived gradually. The timeline highlights the first preview in 2015 , editor tabs in 2016 , the new tree widget in 2019 , the Dark Modern and Light Modern themes in 2023 , and the modernized UI preview in 2026.

The previous workbench design, which we refer to as the classic UI, and the modernized UI preview. We continued refining each feature after it was introduced, guided by feedback across different themes, layouts, and workflows. The current modernization follows the same approach. The first step: color Color is part of how you make VS Code your own, but it also shapes how quickly you can read the interface. A balanced palette helps important content and states stand out without making every part of the workbench compete for attention.

We began the modernization journey by rethinking color with the Dark 2026 and Light 2026 themes. We looked at workbench colors and syntax highlighting as one experience, establishing a visual foundation that we later carried into the modernized UI. A tighter range of surface colors creates a clearer hierarchy and keeps code at the center. More consistent hover, focus, selection, validation, and agent states help the interface read clearly in both light and dark environments.

Dark 2026 and Light 2026 themes. Color gave us a starting point, but creating a more cohesive interface required shared rules for spacing, typography, surfaces, and controls. The opportunity to develop those rules came with a new kind of VS Code window. One VS Code, different ways of working The Agents window became available in Stable as a Preview earlier in 2026. It brings the full agent workflow into one place, from starting sessions and following progress to reviewing results.

It represents a new way of working in VS Code, centered on delegating tasks and reviewing work as it progresses. Supporting that shift called for a fresh approach to the interface, so session state and next actions remain easy to scan without crowding the prompt and review areas. We're aligning the Agents and editor windows around the same approach to typography, spacing, colors, tabs, and controls. Moving between them should feel like changing how you're working, not switching to a different product.

That doesn't mean making the layouts identical or making everyone's VS Code look the same. Each window remains optimized for its purpose, and you can still choose a theme, adjust density, and arrange your workspace to suit your screen and workflow. The existing workbench was designed around direct interaction with files and had evolved component by component. Spacing, typography, surfaces, and controls didn't always follow a shared system, which made it harder to adapt the interface to this new workflow or carry improvements across windows.

The Agents window gave us a place to develop that shared design system. We worked through those design decisions together and tested how they supported managing sessions, following progress, and reviewing changes. The result was a shared visual language we could refine across VS Code, not a separate identity for the Agents window. The Agents window organizes the interface around agent sessions and reviewing their work.

The screenshot shows an early implementation of the updated design system. Once those decisions worked together in the Agents window, the next question was whether the same system could support the editor. The editor brings different demands, including dense file navigation, multiple editor groups, and long-established workflows. Bringing the shared system into that environment became the next phase of the modernization.

Rather than redesigning file editing itself, we started with the shared workbench shell: the foundational areas and controls people see and use across workflows. These elements define how the interface is organized and how people move through it. Starting there let us improve consistency while preserving dense navigation, multiple editor groups, and long-established patterns. As the workbench had grown, related parts such as the Activity Bar, side bars, editor groups, panel, tabs, and status bar had developed different approaches to common design problems.

The initial work focused on: Separating major areas of the workbench clearly without making them feel disconnected. Making controls for resizing and moving panels easier to discover. Simplifying typography and visual hierarchy so your work remains the focus. Using a consistent approach to spacing, corner radii, colors, and elevation. Refreshing tabs while preserving customization. Shared design tokens provide named values for spacing, sizes, and colors instead of defining them separately in every component.

This lets us adjust the interface consistently and support different densities and themes. Earlier: the editor and Agents experiences began with layouts shaped independently around their workflows. Both windows use Dark 2026. Now: a shared design system creates a stronger family resemblance while each window remains optimized for its purpose. Both windows use Dark 2026. Rolling out and learning from feedback We introduced the modernized UI gradually so we could learn from increasingly broad groups of developers before making it the default.

It first appeared as an experimental setting in Stable and was enabled by default in Insiders. We then ran a controlled experiment in Stable for a subset of users. After learning from that rollout, we enabled it by default while keeping the option to return to the classic UI during the transition. As the preview reached more people, our design assumptions met the realities of different displays, zoom levels, themes, and workflows.

We opened a public feedback discussion , and developers shared dozens of detailed examples. We combined that feedback with individual issue reports and team self-hosting to identify patterns rather than treating any screenshot or preference as universal. Several common themes emerged: Overall density: Gaps and panel padding left less room for code, tree rows, and terminal output, particularly on smaller displays and layouts with several editor groups.

Editor tabs: The pill design made the active file feel detached from its editor, while tab labels and actions competed for limited horizontal space. Status bar: Wider item spacing reduced how much information fit before items were hidden. Panel boundaries: Separators and resize controls needed to be easy to find without becoming visually distracting. Theming and contrast: Theme users and authors needed more control over new surfaces, borders, and active states.

Responsiveness: Some reports called out rendering performance as the workbench updated. On a 1920 x 1080 display at 100% zoom, the modern

The rest of this page is on the live site.