Repository navigation
Support Foam features in VS Code's built-in Markdown Editor (WYSIWYG) mode #1742
Description
Is your feature request related to a problem? Please describe.
VS Code 1.135 added a built-in Markdown Editor mode that renders Markdown as you type, similar to Obsidian's live preview. When I set it as the default editor for .md files (workbench.editorAssociations), Foam's core features don't work in it:
[[does not trigger wikilink autocomplete- notes opened via Foam (following a link, Open Daily Note, Create New Note From Template) always open in the plain Text Editor, ignoring the editor association
Describe the solution you'd like
- Wikilink completion (and ideally hover previews) available in the Markdown Editor mode
- Foam commands that open notes respect
workbench.editorAssociations, or a Foam setting to choose which editor notes open in
Describe alternatives you've considered
Using the Text Editor with side-by-side preview (Ctrl+K V) and manually switching via "Reopen Editor With...". This works but adds friction, especially for people moving from Obsidian.
Screenshots or Videos
No response
Activity
claude commentedon Oct 12, 2026
A spec for this issue already exists: #1743 (
specs/1742-open-notes-in-associated-editor/spec.md), open as a draft PR. Stopping rather than writing a second spec for the same issue.That PR is both the queue entry and the place to steer the work from here:
If the intent was to redo the spec rather than continue it, say what should change on #1743 — editing the existing spec on its branch keeps one branch and one PR carrying this feature.
🤖 Generated with Claude Code
Address review on the editor-association spec and plan
chore(vscode): require VS Code 1.136
test(vscode): make the editor association observable in the vscode mock
feat(vscode): open notes in the editor associated with Markdown
feat(vscode): keep wikilink definitions alongside the open-command link