Configure Markdown Workspaces

When to use it

Use this page when completion, diagnostics, or Markdown flavor detection look incomplete and you suspect VS Code opened the wrong folder.

Most workspace problems start with the root folder. Flavor Grenade reads notes, docs, attachments, configuration, and local paths relative to that folder, so opening the right one matters more than tweaking settings first.

Steps

Start with the folder tree before changing configuration.

A single `.obsidian/` folder or Flavor Grenade project config file should identify the content you want indexed. Keep generated output and unrelated repositories outside that active workspace when they should not affect your notes or docs.

Open the folder that owns `.obsidian/` or the project config marker, not a parent folder that happens to contain several projects.

Use `.obsidian/` for Obsidian vaults or project config for a configured Markdown project. Supported config marker names are `.flavor-grenade.toml`, `.flavor-grenade.json`, `.flavor-grenade.jsonc`, `.flavor-grenade.yaml`, `.flavor-grenade.yml`, and `.editorconfig` with Flavor Grenade directives.

Keep generated output and unrelated assets outside the indexed boundary when they should not show up in completion or diagnostics.

TOML version:

YAML version:

1. Open the intended root Open the folder that owns `.obsidian/` or the project config marker, not a parent folder that happens to contain several projects.
2. Keep markers explicit Use `.obsidian/` for Obsidian vaults or project config for a configured Markdown project. Supported config marker names are `.flavor-grenade.toml`, `.flavor-grenade.json`, `.flavor-grenade.jsonc`, `.flavor-grenade.yaml`, `.flavor-grenade.yml`, and `.editorconfig` with Flavor Grenade directives.
3. Confirm indexed files Keep generated output and unrelated assets outside the indexed boundary when they should not show up in completion or diagnostics. TOML version: YAML version:

DocsProject/
  .flavor-grenade.yaml
  docs/
    README.md
    decisions/
      0001-use-language-server.md
  CHANGELOG.md

[core.markdown]
flavor = "auto"
structured_profiles = "auto"

core:
  markdown:
    flavor: auto
    structured_profiles: auto
    overrides:
      - path: docs/decisions
        flavor: commonmark
        structured_profiles: [madr]

Expected result

Flavor Grenade can see the files, headings, tags, embeds, structured documents, and attachments that belong to the current workspace.

Once the root is right, completion, diagnostics, navigation, references, and rename should all agree about the same local targets.

Common failure mode

Opening a parent folder can make local paths ambiguous. Opening only one loose file can leave Flavor Grenade without enough context for workspace-wide features.

If the extension feels half-awake, check the folder first. It is often seeing too much workspace, or not enough.