Skip to content
| Marketplace
Sign in
Visual Studio Code>Formatters>Muninn Markdown EditorNew to Visual Studio Code? Get it now.
Muninn Markdown Editor

Muninn Markdown Editor

bluecloud.dev

|
16 installs
| (2) | Free
Single-pane markdown editor for reading-first workflows, with built-in Mermaid and table tooling.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Muninn Markdown Editor

Muninn Markdown Editor

A reading-first Markdown editor for specifications, documentation and notes. Read, follow links and make small changes in one pane while keeping ordinary Markdown files and useful Git diffs.

See Muninn in action

Read a document and format text directly in the same pane. Replay demo.

Muninn in VS Code's light theme: selecting text and making it bold beside a syntax-highlighted code block.

Change one table cell beside a nested list and a fenced code block, then review the Git diff. Replay demo.

Muninn in VS Code: changing one table cell from Draft to Done, then showing the Git diff with the surrounding nested list and fenced code unchanged.

In the sample README, changing Draft to Done produces this diff:

 | Task    | Status | Owner |
 | :------ | :----- | ----: |
-| Docs    | Draft | Ada |
+| Docs    | Done | Ada |
 | Build   | Ready | Lin |

The list's markers and indentation, code fence, table spacing, emphasis and reference link stay unchanged. Try it by copying the sample into a Git repository, committing it, editing the cell in Muninn and saving. Open the file's changes in Source Control to inspect the diff, or run git diff -- source-preservation.md. Older VS Code versions may use rendered panes for custom-editor comparisons; the Git command shows the source diff.

This example is checked by automated tests, including save, undo/redo and reopen in the installed extension. It demonstrates this edit; edits that cannot preserve source safely still fall back to Source.

Help improve Muninn

Tell us where reading or editing Markdown feels awkward, or what would make Muninn more useful. Report a bug or suggest an improvement. When a Muninn editor is active, click Muninn: Report issue in VS Code's status bar to open the native issue reporter. You can also use Help: Report Issue… or Muninn for VS Code: Report an Issue from the Command Palette.

Please describe the task you were doing and the result you expected. Include steps to reproduce a bug when possible; remove private content from any sample Markdown or screenshots. Muninn does not collect feedback or usage data automatically.

Start reading

This source targets 1.5.0, distributed on the stable release channel. See the changelog for versioned changes. Install Muninn from the VS Code Marketplace and open a .md or .markdown file. If another editor is already your default, use Reopen Editor With… → Muninn Markdown Editor. Muninn respects your editor preferences.

  • Read and navigate: comfortable line width, Unicode heading links, the native Headings picker, relative file links and VS Code Find.
  • Edit: a toolbar with local Paragraph/Heading choices and as many controls as fit; More contains only the remaining actions; standard GFM tasks and strikethrough; editable table cells with raw-source access.
  • Capture notes: Muninn for VS Code: New Markdown Note uses the native file dialog. Insert File Link connects existing files with ordinary relative Markdown.
  • Review diagrams: local, lazy-loaded Mermaid previews, gated by workspace trust.
  • Read code: fenced code uses the editor font, a language selector and theme-aware syntax colors. Long lines scroll within the block. Unknown languages and blocks over 20,000 characters remain editable as plain text.
  • Adjust the reading view: use Zoom out, the Zoom level percentage menu, Zoom in and Fit to width in the toolbar or More. Local zoom runs from 50% to 200% in 10-point steps, independently of VS Code zoom. Fit uses the full pane at 100% and stays responsive; choosing a level from the percentage menu, including 100%, applies it with your latest configured reading width. These controls affect only the current editor view, leaving Markdown and undo history unchanged.
  • Share a document: Export HTML in the toolbar/More menu, editor-title menu or Command Palette writes a standalone HTML snapshot, including accepted unsaved edits, through the native save picker. Open that file in a browser and choose Print → Save as PDF for PDF output. Print styles wrap code and keep headings with following content.
  • Use Source: open the same file in VS Code's Markdown text editor whenever you need the full source syntax.

Untouched files round-trip byte for byte in the regression corpus. Edits preserve surrounding source syntax; changes that cannot be mapped safely are rejected with a Source fallback. Conflicting external edits are preserved in a separate unsaved recovery document. Save and Source wait for pending rich edits. No proprietary note syntax or database is introduced.

Settings

Setting Purpose
muninn.toolbar.mode Deprecated; both legacy values are ignored. Visibility adapts to pane width
muninn.appearance.contentWidth comfortable, full, or 40–120 characters
muninn.images.destination Image import folder relative to the document; default images/
muninn.integrations.mermaid.enabled Enable diagram previews
muninn.integrations.mermaid.allowInUntrustedWorkspaces Explicit user-level permission to render in Restricted Mode; default false

The old muninn.editorAssociations setting is deprecated and has no effect. Configure defaults with VS Code's editor picker.

Remote images do not load automatically. Imported images are limited to 10 MiB. Image imports keep their original selection and ask you to retry if the document changes before they finish. Markdown HTML stays disabled. The extension makes no telemetry calls. Desktop VS Code 1.85.2+ is supported; browser/vscode.dev support is not advertised.

HTML exports embed local PNG, JPEG, GIF, WebP and SVG images up to 2 MiB each. Larger or unreadable images retain relative references when possible, with a warning; share those files alongside the HTML. Remote/data image sources and unavailable cross-provider assets become alt text. Mermaid is exported as readable source with a notice; code blocks and task markers remain plain text. No scripts or remote resources are included. Unapplied table-source drafts are not exported. Export does not save or rewrite the Markdown file. Direct PDF export is not provided; browser/OS print dialogs and PDF destinations vary. See the export decision, which implements the HTML workflow tracked in #275.

Development

Use Node 24 and your preferred editor or AI development environment. The contributor documentation contains the shared setup, architecture, development rules, and testing guide.

npm ci
npm run compile
npm run bundle
npm run coverage
npm test
npm run package
npm run test:e2e

F5 runs the checked-in compile/bundle task. Packaging produces a minified stable VSIX and third-party notices; the UI suite tests that exact archive.

Security policy · Security posture

License

GNU Affero General Public License v3.0 (AGPL-3.0-only). See LICENSE.

License — plain language

Using Muninn to edit files imposes nothing on those files, your employer's code, or any repository you open. Your markdown, and anything you write with Muninn, is yours. The AGPL governs copying, distributing, or modifying Muninn itself. If you distribute a modified Muninn, share it under the same license and keep required notices. If you serve a modified Muninn through hosted VS Code environments such as code-server, Codespaces, or Gitpod, offer users the source for that modified Muninn. Redistributing unmodified Muninn keeps the LICENSE and notices with the extension. Common-understanding summary, not legal advice; the LICENSE text governs.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft