Search, links and tags
The local index: full-text search, backlinks that survive a rename, tags, and how the sidebar is sorted.
Search, backlinks and tags are served by a SQLite index inside the vault's .context folder. It is derived from your files, which means it can be deleted and rebuilt, and it never becomes a second source of truth.
Search
Full-text search uses SQLite FTS5 over note titles and bodies, with Unicode tokenization and diacritics folded, so AND, OR, NOT and NEAR queries work and results can be rendered with highlighted snippets. The index is updated on every write the bridge sees, including writes an AI or git made.
Backlinks
Every [[wikilink]] is one row linking the note that contains it to the note it resolves to, with unresolved links kept as rows with no target so they can be found later. Links are rewritten by docId rather than by path, which is why renaming or moving a note never breaks the links pointing at it.
Tags
Tags come from inline #tags and from the tags: property, and typing one suggests the tags already in the vault.
The sidebar
- Sort by name, including Z to A so the latest daily note sits on top.
- Give any folder its own sort from its right-click menu.
- Folders load their contents when they are opened, so a large vault does not pay for the whole tree up front.
When search looks wrong
The index can trail the files after an unusual event, such as a bulk change made while the app was closed. Rebuilding it re-reads the Markdown and reconstructs search, backlinks and tags from scratch. Nothing in your notes is at risk, because the index holds no original content.
This page is written from docs/specs/02-database-architecture.md and docs/RELEASE_NOTES.md in the repository. Those documents go further, and they are the ones that change first.
Read it on GitHubWas this page helpful?