Tags

Tags are registered, per-user labels — each has a name, a color, and an optional description, defined once and shared across every document that carries it. They attach to documents and folders.

Adding a tag

Open a document (or a folder). The tag picker in the metadata panel browses your registered tags on focus and narrows as you type. Typing a name that doesn’t exist yet offers “Create …” — pick a color in the modal and it’s registered and applied in one step.

Folder tags — inheritance

Tag a folder and everything inside it (recursively) carries that tag for search and filtering. Documents keep their own tags on top. Move a document into or out of a tagged folder and its effective tags follow — no rewrites.

Namespaces

A name like project:pack files the tag under the project namespace — namespaces are just name prefixes, so you create one by typing it. The settings page groups tags by namespace and can rename or archive a whole namespace at once.

Managing the registry

Settings → Tags lists every tag: recolor, edit descriptions, rename (renames propagate everywhere instantly), archive, unarchive.

Archiving a tag

Archiving hides a tag everywhere — pickers, documents, search — but keeps its assignments, so unarchiving restores it to every document that carried it.

Filtering

• File tree — the tag filter above the tree prunes it to matching documents (folder-inherited tags count), and the filter survives navigation.
• Search page — add tags to narrow semantic results.
• Command palette — type #tag to jump to tag-filtered results.
• Agents — search_documents({ tags: [...] }) or fs_find_by_tags via MCP; both match effective (inherited-included) tags.

API keys and profiles

An agent’s API key can carry a profile — a named bundle of tags that gets stamped onto every document the key writes. Configure profiles in Settings → Profiles and attach one when minting a key, so an agent can’t forget to label its project.