Markdown Editor: "Toggle Editor Mode" shortcut only works Preview → Markdown, not back

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

What happens
The new Markdown Editor has Preview / Markdown buttons in the top-right corner. The command markdownEditor.toggleMode (“Markdown Editor: Toggle Editor Mode”, ⌘⇧V by default) only works in one direction:

  • Preview → Markdown: works. The file reopens in the plain Text Editor.
  • Markdown → Preview: does nothing. The command requires markdownEditorActive, which is false in the Text Editor. With the default ⌘⇧V, the key press falls through to VS Code’s markdown.showPreview and opens the old Markdown Preview instead.

“View: Reopen Editor With… → Markdown Editor” doesn’t work as a way back either. The file’s saved mode is still “raw”, so the Markdown Editor immediately sends it back to the Text Editor. Right now the only way back to Preview is clicking the Preview button.

Expected
One shortcut that toggles both ways. For example, markdownEditor.toggleMode could also be enabled in the Text Editor when the file is a Markdown file in raw mode, and switch it back to the rich view.

Steps to Reproduce

  1. Open a .md file in the Markdown Editor (Preview mode).
  2. Press ⌘⇧V (or run “Markdown Editor: Toggle Editor Mode”). It switches to the raw editor.
  3. Press ⌘⇧V again. Instead of switching back to Preview, it opens the old Markdown Preview (or does nothing if the command is rebound).

Operating System

MacOS

Version Information

Cursor version: 3.21.13 · OS: macOS 26.6.2

Does this stop you from using Cursor

No - Cursor works, but with this issue

10

Hi @alal5, thanks for the report!

You’ve got it right: the Toggle Editor Mode command is only available while the rich Markdown editor is the active editor, so once you’ve switched to the plain text view the shortcut no longer matches and the key press falls through to the built-in Markdown Preview. Reopen Editor With hits the same thing, because the file’s saved mode is still “raw” and the Markdown editor hands it straight back to the text editor.

This is a known issue we’re already tracking, and I’ve added your report to it.