Mastodon

Connected Files & Obsidian

Connect folders of markdown files, edit them in place, and let their tasks, dates, and tags flow into your planner. Obsidian-friendly throughout.

Your notes might already live somewhere: an Obsidian vault, a folder of markdown in iCloud Drive. Finalist doesn't ask you to import them. Connect the folder and the files stay exactly where they are, editable in place, while their tasks, dates, and tags flow into your planner.

Connecting files

From the Notes home, choose Add Folder… to connect a whole folder (every markdown file inside, subfolders included) or Add File… for a single file. iCloud Drive folders keep syncing wherever they normally sync; Finalist reads and writes the files in place and never moves them. Got a huge vault? Long-press a subfolder and Unload it to skip it.

A connected folder takes its name from the folder on disk. An Obsidian vault stored in Obsidian's own iCloud space shows up as "Documents", because that's the real name of the folder Obsidian syncs into. To give it a friendlier label, choose Rename: long-press the folder in the Notes home, right-click or long-press it in the sidebar on Mac and iPad, or open the folder and pick Rename from its menu (the quicker route on iPhone). The same menu has Remove, which disconnects the folder or file from Finalist without touching anything on disk. Renaming only changes the name shown in Finalist; nothing on disk is touched. Once you've renamed one, its own screen prints the folder's full path on disk along the top, so you can always tell exactly which folder is connected.

Tasks inside your files

Finalist speaks the Obsidian Tasks dialect. A line like this in any connected file:

- [ ] Send the proposal 📅 2026-08-14 #work

becomes a real task in Finalist: it appears on August 14 on your Daily page, checkable right there, picked up by Smart Lists, carrying its #work tag into the tag cloud. Checking it off in Finalist writes the [x] back into your file. Scheduled dates, start dates, created dates, and priorities in the emoji syntax are understood too, as are Dataview-style inline fields like [due:: 2026-08-14]. The rest of the Obsidian Tasks fields (cancelled date, recurrence, the on-completion action) are kept out of the task title without changing what they mean to Obsidian. And when a task's #tag matches a tag in one of your Score goals, completing it earns that tag's points like any native task.

Markdown tasks can be moved to Someday like any other task. Because a line in a file has no identity of its own, moving one there adds an Obsidian Tasks id to the line, such as 🆔 k3x9qa (or [id:: k3x9qa] on a line already using inline fields), so Someday can find the task again after the file changes or on another device. Giving a markdown task a time, by dropping it into a timed slot on Daily or onto the Timeline, adds an id for the same reason: the time is kept in Finalist rather than the file, and the id is what lets it follow the line through edits and show up on your other devices. An id the line already has is used as is. If multiple connected task lines share an id, they stay visible on their days and cannot be moved to Someday until you give them unique ids in the files. Completed and tag-hidden lines also count when checking for duplicates. Finalist never adds one for any other reason and never removes one.

Steps: indented tasks

Break a task into steps the way you would in Obsidian, by indenting task lines under it:

- [ ] Launch the newsletter 📅 2026-09-20
    - [ ] Draft the first issue 📅 2026-09-16
    - [ ] Set up the signup form
    - [ ] Send a test to myself

Finalist reads the indentation and knows which line each step belongs to. Tabs and spaces both work, whatever indent size your vault uses. A note bullet or a blank line between steps doesn't break the chain; a heading or a paragraph of prose does, the same way it ends a list in Markdown.

On the day page, in Daybook and Broadsheet alike, steps sit nested under their task with a chevron to fold them and a count like "1/3" on the task, just as native subtasks do. Each step is a task in its own right: check it off, set its status, tag it, give it a date. The count on the parent tracks every direct step wherever it is.

Two things set markdown steps apart from native subtasks. A step can have its own date, and then it shows up on that day rather than under its parent, with a small pill naming the task it belongs to, so a project can be broken into steps with their own deadlines. And a step you give a time, by dropping it into a timed slot or onto the Timeline, leaves the nest for the calendar the same way. Steps without a date of their own take the file's date like any other line in a daily note, which keeps them together with their task.

Folding is per device and steps keep the order they have in the file; reorder them in the file.

Blocked by

Obsidian Tasks lets a line wait on others: ⛔ k3x9qa (or [dependsOn:: k3x9qa], several ids separated by commas) names the tasks that have to finish first. Finalist reads it the same way. While any of those tasks is still open, the waiting task shows a Blocked pill, dims, sorts below its neighbors on the day, and stays out of the Day Review. Check the blocker off, in Finalist or in Obsidian, and the waiting task comes back on its own. Done and cancelled both count as finished. An id that no line in your connected files carries doesn't block anything.

If your vault has more checkboxes than you want in your planner, Filter by tags in Settings under Markdown Files narrows what comes across: type one or more tags, separated by commas, and only task lines carrying one of them are picked up. Capitalization doesn't matter, and the tag has to be on the task line itself, not just in the file's frontmatter. Leave the field empty and every task comes across.

Task statuses beyond done

Extended statuses render with their own icons: [/] in progress, [-] cancelled, [>] forwarded, [<] scheduled, [!] important, [?] question. Change a task's status from its long-press menu with Set Status. In Settings under Markdown Files you decide, per status, whether it hides from outstanding views and whether it gets the strikethrough treatment.

[[Wiki links]] and standard [text](note.md) links navigate between your notes inside Finalist, on iOS and Mac. Your vault's internal links keep working; they just work here too.

Daily notes

A file whose name carries a date, the 2026-08-14.md an Obsidian daily note gets, belongs to that day as far as Finalist is concerned. The date in the name is enough, no frontmatter required, and it can sit anywhere in the name, so Standup 2026-08-14.md counts too.

Two things follow from that. Undated tasks inside the file inherit the day, so a bare - [ ] Call the bank written in Monday's note shows up on Monday. And the file itself appears in the Notes section of that day's Daily page, as a sticky-note card or a row, one tap from the file editor. Turn the section on in the Layout editor if you haven't already; it's off by default. Files pinned from their long-press menu keep showing every day, badged with a pin, the way pinned notes do.

If you'd rather your filenames stayed just filenames, turn off Use filename as due date in Settings under Markdown Files. Frontmatter dates keep working either way.

Frontmatter

Files can carry YAML frontmatter (tags, date), and Finalist reads and honors it: frontmatter tags merge with inline #tags, and a date puts the file on that day, in the Notes section and for the tasks inside it. A frontmatter date wins over a date in the filename. Edit the frontmatter directly with the </> button in the file editor, or just change tags and dates in the app and Finalist updates the file. The + Tag pill in the file editor offers two alphabetical lists, Finalist Tags (your native tags in their markdown spelling) and Markdown Tags (tags found in your other files), so the same tag stays one tag everywhere; Add Tag... lets you type a fresh one.

Pinning is not a frontmatter field. Pin a file the way you pin any note, from its context menu in the Notes tab or the pin button in the file editor. Pins are per device, so pin a file on each device you want it on.

The point of all this

Your notes stay portable plain text that works in Obsidian, in any editor, and in twenty years. Finalist adds the planning layer on top: the tasks inside your notes meet the rest of your day, one page at a time.

Related: Notebooks & Notes · Writing in Markdown · Lists