VS Code 1.131 and 1.132 add a hybrid Markdown editor — here is how writers can use it

Two back-to-back releases have quietly made Visual Studio Code a much better Markdown writing tool. The 1.131 update, which landed in late July 2026, introduced a new hybrid Markdown editor — an experimental editor that lets you view, edit, and add agent-actionable comments to Markdown files inside the Agents window. The 1.132 update, released on August 5, 2026, went further and added Markdown diffs to that editor, alongside multilingual dictation and side chats.

For years VS Code has been one of the most popular ways to write in Markdown — we ranked it among the top editors in our round-up of the best Markdown editors for 2026. But its Markdown experience has mostly been: write in the raw file, then open a separate preview pane. The hybrid editor closes that gap, and it arrives at a moment when more writers than ever are using AI agents to draft, summarize, and edit their posts. This guide explains what the hybrid editor actually does, how to turn it on, and the practical workflow for going from a VS Code draft to a finished, formatted post on LinkedIn, X Articles, or Medium.

What the hybrid Markdown editor is

The hybrid Markdown editor is described in the official VS Code 1.131 release notes as an experimental feature to "view, edit, and add agent-actionable comments to Markdown files in the Agents window." The key idea is that you no longer have to choose between the raw source view and the rendered preview — or jump between an editor and a separate tab to see what an AI agent has changed.

In one view, the hybrid editor gives you the rendered document, the editable Markdown source, and the ability to attach comments that an agent can act on. That last point is the real differentiator. As coding assistants like Copilot, Claude, and Codex increasingly work on content — not just code — having a Markdown surface where an agent's suggested changes are visible, actionable, and reviewable matters. The editor is controlled by the setting workbench.editor.markdownDefaultEditorInAgentsWindow, and it is part of a broader rearchitecture of agent sessions in VS Code around the agent host.

The 1.132 update, released on August 5, sharpened the feature further with Markdown diffs: you can now see exactly what changed in a Markdown file — useful when a subagent rewrote a section, restructured your headings, or trimmed a paragraph. Seeing a clear before-and-after diff is far safer than blindly accepting an AI rewrite, and it fits the same "one Markdown source, many outputs" philosophy we explore in this survey of the 2026 Markdown tool landscape.

Built-in dictation: draft with your voice

Alongside the hybrid editor, VS Code 1.131 added built-in dictation — an experimental feature that lets you dictate in chat, editors, and across the workbench. The 1.132 release extended this to multilingual dictation, so you can draft in more than one language without leaving the editor.

For Markdown writers this is a genuinely useful combination. You can dictate a rough draft while pacing around the room, let VS Code transcribe it into Markdown, then switch to the hybrid editor to clean up structure and verify the rendered output. Because everything stays in a plain-text Markdown file on your own machine, you keep full control of the draft — there is no proprietary lock-in and no mandatory cloud round-trip. That local-first posture is exactly the same privacy argument that drives client-side versus cloud Markdown converters, and it is central to how md2rich is built.

A practical writing and publishing workflow

Here is a clean, repeatable workflow that combines VS Code's new Markdown tools with a client-side converter for publishing.

Step 1 — Update and enable the hybrid editor. Make sure you are on VS Code 1.131 or later (1.132 for Markdown diffs). Run Check for Updates, or grab the Insiders build to test features early. If the hybrid editor is not your default in the Agents window, set workbench.editor.markdownDefaultEditorInAgentsWindow to true.

Step 2 — Write and review in one view. Create a draft.md file and open it in the Agents window. Draft with dictation if you like, then use the hybrid editor to see the rendered result, add comments for an agent, and review any diffs it produces. Keep your draft in plain Markdown so it stays portable.

Step 3 — Convert to rich text for the destination. When the draft is final, copy the Markdown and paste it into a client-side tool. On md2rich, conversion happens entirely in your browser — nothing is uploaded, and you get formatted rich text you can paste straight into LinkedIn, X Articles, Notion, or Medium. This is the same no-upload workflow we documented for Markdown to LinkedIn and Markdown to X Articles.

Step 4 — Keep one source of truth. Store the final .md file in your repository, notes app, or sync folder. Because it is plain text, you can later repurpose the same draft for a newsletter, a blog, or a different social platform without re-typing anything. That single-source pattern is the backbone of write-once, publish-anywhere workflows.

Three Markdown-to-rich-text examples

To see the value of ending your VS Code workflow in a client-side converter, here are three common output shapes. Write each in Markdown in VS Code, then convert with a local tool to get the formatted result.

Example 1 — a LinkedIn post with a heading, a list, and a bold lead. Source Markdown:

## What 3 things define a strong long-form post in 2026?

1. A clear point in the first two sentences.
2. **Structured formatting** the reader can skim.
3. A human voice with a specific example.

Draft in Markdown, then convert to rich text before you paste.

Example 2 — an X Articles draft with an H2 and a short quote. Source Markdown:

# Why I draft everything in plain text

> A Markdown draft is a promise you can keep anywhere.

Most platforms make you paste twice. A client-side converter
lets you write once and format on the way out.

Example 3 — a Notion page with a checklist and a link. Source Markdown:

## Publishing checklist

- [x] Draft in VS Code
- [x] Review the Markdown diff
- [ ] Convert with md2rich (no upload)
- [ ] Paste rich text into Notion

Each of these starts as a plain-text .md file you can version, archive, and reuse — then becomes a formatted post the moment you need it.

Why this matters for Markdown writers

The hybrid Markdown editor is a small feature with a big implication: the most widely used code editor on the planet is now treating Markdown as a first-class content format, not just a config file format. When VS Code invests in rendered Markdown editing, Markdown diffs, and dictation, it signals that plain-text writing is here to stay — and that the editing experience is catching up with the convenience of rich-text apps.

For writers who publish to social and professional platforms, the practical takeaway is clearer than ever: keep drafting in Markdown, and use a small client-side converter at the end of the pipeline to get formatted output. That way the editor stays fast and universal, while the paste step stays private and free of formatting rewrites. It is the same division of labor we mapped out in this Markdown to rich text guide, and it now has an even stronger editor on the drafting side.

If you mostly write prose rather than code, you do not need to switch your whole workflow overnight. But the arrival of a serious Markdown editor inside VS Code is a good moment to reconsider a lighter-weight tool for the final step. There is no reason to fight a rich-text editor's toolbar when you can write clean and convert locally.

FAQ