Use Tags and Tag Completion

When to use it

Use this page when tags are part of how your vault groups projects, people, topics, or status.

Completion helps keep nested tag spelling consistent. References help you see where a tag already appears before you rename, split, or retire it.

Flavor Grenade treats tags as part of the same flavor-aware Markdown surface as links, headings, images, embeds, and attachments. Tags in normal prose participate in completion, references, highlights, semantic tokens, and diagnostics where relevant. Tags inside examples or generated regions stay inert.

Steps

Work in a vault folder so tag suggestions come from more than the current note.

Start with a tag prefix that already exists in more than one note, then try a new nested tag so the difference is easy to see.

Type `#project/` and select a known nested tag from your vault.

Semantic tokens should make recognized tags look like tags in editors that support semantic highlighting. If the text still looks like ordinary prose, check the cursor position and surrounding Markdown syntax.

Run references on the tag to inspect notes that share the same project or topic.

Use document highlights when you only need repeats inside the current note. Use references when you want the vault-wide list. Code lens may also surface useful reference information near supported Markdown structure.

Tags inside code fences and comments are examples, not real tag usage.

1. Type a tag prefix Type `#project/` and select a known nested tag from your vault. Semantic tokens should make recognized tags look like tags in editors that support semantic highlighting. If the text still looks like ordinary prose, check the cursor position and surrounding Markdown syntax.
2. Find tag references Run references on the tag to inspect notes that share the same project or topic. Use document highlights when you only need repeats inside the current note. Use references when you want the vault-wide list. Code lens may also surface useful reference information near supported Markdown structure.
3. Keep tags outside opaque examples Tags inside code fences and comments are examples, not real tag usage.

#project/flavor-grenade
#project/flavor-grenade/docs

Expected result

The tag suggestion or reference list reflects tags found in indexed vault notes.

That makes tag cleanup less dependent on memory and more grounded in the notes you already have. The same tag should behave consistently across completion, references, highlights, hovers, and semantic tokens.

If you use folding, document symbols, or selection ranges while cleaning up a long note, they should help you move by Markdown structure instead of scanning every line. Those editor features do not change tag meaning, but they make large tag cleanup safer and faster.

Common failure mode

A tag typed before indexing finishes may not have vault-wide suggestions yet.

If a tag is missing from completion, confirm it appears in normal Markdown, outside code fences or comments, and that indexing has finished.

If you are cleaning up a tag family, check references before changing the spelling. That gives you a list of notes that use the old tag and helps you decide whether the tag is truly obsolete, just misspelled, or still useful in another part of the vault.

Do not expect tags inside frontmatter, code, math, comments, or template blocks to behave like prose tags unless your editor and vault conventions expose them as normal Markdown content. Flavor Grenade avoids those regions to prevent examples and metadata from becoming accidental vault-wide tag usage.