Open any vault .md file — the language server starts automatically and VS Code switches the language picker to OFMarkdown.
That's it. Wiki-link completions, diagnostics, go-to-definition, and all other features activate as soon as the server finishes indexing your vault. The status bar shows indexing progress.
Generic Markdown files outside detected vaults stay in VS Code's normal Markdown mode. If you manually choose another language mode for a document, Flavor Grenade leaves that choice alone.
Language-specific VS Code settings can target OFMarkdown:
{
"[ofmarkdown]": {
"editor.wordWrap": "on"
}
}
Commands
Open the Command Palette (Ctrl+Shift+P / Cmd+Shift+P) and type "Flavor Grenade":
Flavor Grenade: Restart Server — Stop and restart the language server
Flavor Grenade: Rebuild Index — Re-scan the vault and rebuild the document index
Flavor Grenade: Show Output — Open the language server output channel for troubleshooting
Development Smoke Test
From the repository root, run bun install.
From extension/, run npm ci.
Open extension/ in VS Code.
Start the Run Extension launch configuration.
Edit code under the repository root src/; the server TypeScript watch task rebuilds ../dist/main.js.
Run Flavor Grenade: Restart Server in the Extension Host window.
Open a note inside a folder containing .obsidian/; confirm the language picker becomes OFMarkdown.
Open a non-vault Markdown file; confirm the language picker remains Markdown.
Confirm changed LSP behavior is visible without rebuilding the bundled server binary.
Requirements
VS Code 1.81.0 or later
An Obsidian vault or a folder configured with .flavor-grenade.toml
