More than one vault
Above your folder list there is a dropdown showing the vault you are in. Open it to switch to another, rename one, or add a folder you have not used yet. It is free, with no cap.
Each vault keeps its own daily-note folder, date format, default folder for new notes and attachment folder, because those are facts about that folder rather than about you. Your font, reading width and preview settings stay the same everywhere.
Every vault also keeps its own version history, so a note called
Daily/2026-09-01.md in one vault can never show you versions of the note with
the same name in another.
Adding a folder never changes it. Removing a vault removes it from this list and nothing else: every file stays exactly where it is. Version history is kept too, so adding the same folder back restores it.
Pointing a vault at a code repository
This works, and TypeFire will tell you what to expect when you do it. Your
version history and search data live outside the repo, so nothing of ours ever
appears in git status.
Editing a note changes that note, as you would expect. Starring or tagging one adds a single line to the top of the file, so it will show up as a change. You are shown exactly what that looks like when you add the folder.
Folders with no markdown anywhere inside them are dimmed and start collapsed, so a repo opens with its docs legible and its source quietly out of the way. Nothing is hidden: the tree is a true picture of the folder you chose.
If a vault is not reachable
An unplugged drive, a volume that has not mounted, a folder that moved. TypeFire says so plainly and offers to find it again. It never quietly switches you to a different vault, because the next thing you capture would land somewhere you did not choose.
Documentation for TypeFire 5.1.0. Updated 2026-09-15.