Tags

A tag is a word with a # in front of it, written wherever it belongs — in a task, in a sentence, in the front matter at the top of a note. mdai indexes every one of them across the whole vault.

Writing a tag

Notes from the site visit #client/acme #site-visit

- [ ] Send the revised drawing #client/acme @2026-09-20

What counts as a tag:

• Letters, digits, _, - and / after the #. Letters means any alphabet — #učenje, #Träume and #проект are tags.
• / lets you nest: #client/acme is one tag, and it reads as a path.
• The # must come after a space, a tab, or at the start of the line. This is what keeps https://example.com/#pricing from becoming a tag called pricing.

Tags in front matter

If a note starts with a front matter block, its tags: key is read too, in either shape:

---
title: Site visit
tags: [client/acme, site-visit]
---

---
title: Site visit
tags:
  - client/acme
  - site-visit
---

The rest of the front matter is deliberately not searched for inline tags — in YAML a # starts a comment, and a comment you wrote is not a tag you meant.

The Tags panel

View → Toggle Tags. The panel has two views, one behind the other:

1. All tags — every tag in the vault with the number of times it occurs.
2. One tag — click a tag and you get the places it appears: the file, and the line of text around it. Click a place and the note opens there.

The All tags button takes you back to the list.

An empty vault says “No tags in this vault.” If a tag has just lost its last occurrence, opening it says “No files carry this tag any more” rather than showing you a stale list.

It is the same tag everywhere

The Tags panel and the Tasks panel read tags with the same rule — one piece of code, not two. A tag the panel counts is a tag the task carries, and there is no third interpretation hiding anywhere.

Related

• Tasks — tags on tasks, with dates
• Search — for finding text that is not a tag