Markdownのプレビューを見ながら編集できる──VS Code 1.131 新機能を試すVS Code 1.131 introduces an experimental Hybrid Markdown editor that lets users…

Visual Studio Code 1.131 has introduced an experimental capability called the Hybrid Markdown editor, which allows users to edit Markdown documents while viewing them in their rendered form. For anyone who writes documentation, README files, or notes in Markdown, this addresses a long-standing friction point: the constant switching between a raw source pane and a separate preview pane to check how formatting will ultimately appear.

Traditionally, editing Markdown in VS Code has meant working with plain source text on one side and, if desired, opening a live preview alongside it using the built-in Markdown preview command. That side-by-side workflow is functional, but it splits attention across two panes and doubles the horizontal space a document occupies. The Hybrid Markdown editor appears designed to collapse those two views into one, so that headings, bold text, lists, links, and other elements are displayed as they will render, while the underlying text remains directly editable in place. According to the release notes, the feature is also surfaced in the context of the Agents window, where Markdown can be displayed and worked with, suggesting it is being positioned partly around AI-assisted and agent-driven workflows rather than solely as a standalone editing mode.

The approach is broadly similar to what some dedicated Markdown applications already offer. Tools such as Typora popularized the idea of a seamless, near-WYSIWYG editing surface where formatting syntax is hidden or styled as you type, and note-taking applications like Obsidian and Notion have their own variations of live or hybrid rendering. Bringing a comparable experience into VS Code is notable because the editor is widely used by developers who keep documentation close to their code. Being able to edit rich-looking Markdown without leaving the editor could reduce context switching for tasks like maintaining project READMEs, writing changelogs, or drafting technical notes.

Because the feature is explicitly labeled Experimental, it is likely to be gated behind a setting or flag and may not be enabled by default. VS Code has a long history of shipping features in preview form, iterating based on user feedback, and either promoting them to stable or reworking them over subsequent monthly releases. Users interested in trying it should expect rough edges, potential behavior changes, and the possibility that some Markdown constructs, embedded HTML, or extension-provided syntax may not render or edit as smoothly as the standard source view. Treating it as a preview rather than a finished replacement for the existing editing and preview panes is the prudent stance for now.

The connection to the Agents window is worth situating within the broader direction of VS Code and GitHub Copilot. Over recent releases, Microsoft has been steadily expanding AI and agent capabilities inside the editor, moving from simple inline completions toward chat interfaces and more autonomous agent modes that can read, generate, and act on content. Markdown is a natural medium for this kind of interaction, since AI responses, plans, and documentation are frequently formatted in Markdown. A hybrid editor that presents that content in a readable, rendered form while still allowing edits fits the pattern of making generated output easier to review and refine directly.

For readers who want to experiment, the prerequisite is simply updating to VS Code 1.131, after which the experimental setting can be located and toggled. It helps to understand a few underlying concepts first: Markdown itself is a lightweight markup syntax, VS Code already ships robust Markdown language support including preview, outline, and link validation, and experimental features are typically documented in the version's official release notes with guidance on how to opt in. Anyone already comfortable with the existing preview command will find the mental model familiar, just consolidated into a single surface.

In practical terms, the significance of this change is incremental rather than revolutionary. It does not add new Markdown syntax or change how files are stored; documents remain plain-text Markdown on disk. What it changes is the editing experience, potentially lowering the barrier for less technical contributors and speeding up routine formatting work for everyone else. Whether the Hybrid Markdown editor graduates to a stable, default experience will depend on how it performs in real-world use and the feedback the VS Code team gathers during this experimental phase.