The Markdown preview in the Cursor3 Agent window causes formatting issues in Markdown files

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The Markdown preview in the Cursor3 Agent window causes formatting issues in Markdown files with YAML front matter.

Steps to Reproduce

For example, Skill.md or other types of Markdown documents.
The original formatting is

---
name: apple-notes
description: Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders.
---

# Apple Notes CLI

In Preview mode, if you switch to another file and then switch back, the formatting is automatically reformatted to:

---

## name: apple-notes
description: Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks Clawdbot to add a note, list notes, search notes, or manage note folders.

# Apple Notes CLI

It’s not just front matter; for example, xxx/** is also automatically formatted as xxx/**, which clearly doesn’t match my expectations.

I’ve already uninstalled the Markdown plugin and only installed the Prettier plugin, and the IDE shouldn’t be affecting the Agent Window.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.13
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, this is a known issue. Inline preview uses a WYSIWYG engine that re-serializes the markdown when you switch modes or tabs. Because of that, --- frontmatter separators get interpreted as horizontal rules, and ** in glob patterns gets interpreted as bold formatting. The content then gets written back to disk with no warning.

Workaround: use the classic side-pane preview with Cmd+Shift+V instead of the in-place toggle. This won’t affect the file contents.

More details in this thread, it describes the same issue: Bug Report: Preview Mode Strips Content and Formatting When Switching Back to Markdown Mode

The team is aware and your report helps with prioritization. Let me know if there’s anything else.

A post was merged into an existing topic: Bug Report: Preview Mode Strips Content and Formatting When Switching Back to Markdown Mode