markdown.preview.frontMatter setting not applied in inline editor preview

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The markdown.preview.frontMatter user setting is ignored by the inline editor preview (the “Preview” / “Markdown” toggle in the editor tab header). Frontmatter is rendered as visible plain text even when set to “hide”. The “Open Preview to the Side” command correctly hides it, so the setting works — it’s just not applied in the inline preview path.

Steps to Reproduce

Set “markdown.preview.frontMatter”: “hide” in user settings
Open any .md file containing YAML frontmatter delimited by —
Click the “Preview” button in the top-right of the editor tab to switch to inline preview mode
Observe frontmatter is rendered as visible text
Now use Cmd+K V to open preview to the side — frontmatter is correctly hidden

Expected Behavior

The inline editor preview should respect markdown.preview.frontMatter: “hide” and hide YAML frontmatter, consistent with “Open Preview to the Side”.

Screenshots / Screen Recordings

cursor-bug.png
cursor-bug.png3800×1010 466 KB

Operating System

MacOS

Version Information

Version: 2.6.19 (Universal)
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

n/a

For AI issues: add Request ID with privacy disabled

n/a

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report. The repro steps and screenshots are clear.

This is a confirmed bug. The inline preview toggle Preview/Markdown uses a different rendering engine than the side preview, and right now it doesn’t handle YAML frontmatter. It just renders it as plain text.

As a workaround, use the preview with Cmd+Shift+V. Like you noticed, it handles frontmatter correctly.

I’ve flagged this with the team. No ETA yet, but your report helps us prioritize it.

7

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.