Use case or problem
Many vaults are organized primarily by folder — one folder per project, topic, game, or area of life. At the same time, it’s common to reuse the same tag name across folders for a cross-cutting concept that applies no matter where the note lives (e.g. #toread, #todo, #mods, #reference).
Right now there’s no good way to see both dimensions together in Graph View. A flat tag merges every folder’s notes into a single node, so you can’t tell at a glance which folder a given instance came from. A nested tag (#project/toread) preserves that context, but only if you remember to type the folder prefix by hand every time — and even then, Graph View won’t connect it back to a general #toread node without a third-party plugin, so “which folder” and “what kind of thing” end up as two disconnected systems.
Proposed solution
Give tags a second, folder-based identity automatically — no manual “/” nesting required.
- The general tag node (e.g. #toread) keeps working exactly as it does today: one node per name, grouping every note with that tag across the whole vault.
- Additionally, for each folder that contains at least one note using that tag, show one small extra node with the same label — representing that tag as used specifically within that folder.
- This folder-scoped node connects to exactly two things: the folder it belongs to, and the general tag node with the same name.
- Folder-scoped nodes never link directly to each other, even when they share a name. #toread in /Projects/ and #toread in /Books/ only meet through the shared general #toread node — never through one another.
This keeps tags simple and flat to write everywhere, while making folder context visible in the graph automatically.
Current workaround (optional)
The closest workaround today is manually rewriting tags as nested paths (#folder/toread) plus installing a third-party plugin (e.g. graph-nested-tags) just to draw the parent-child edge. This means remembering the folder prefix every time, and folders still never appear in the graph as their own entity — folder structure and tag meaning stay two unrelated systems.
Related feature requests (optional)
Related but distinct: Enhanced Nested Tags and Search Functionality in Graph View — that thread asks for better visualization of tags you’ve already hand-written with “/” nesting. This request is about adding the folder as an automatic second identity, with no nested syntax required at all.