Obsidian Daily Note

Why this exists

If you work in the terminal all day, the friction of switching to Obsidian to log one line is just enough that you do not do it. The session ends, the detail is gone, and your daily notes have a week-long gap.

I log everything through this: finished automation runs, client calls, reminders for next week. One line to Claude mid-session, and it lands in the right dated file in my vault. The discipline became sustainable the moment it stopped costing a context switch.

How it works

1. It finds your vault once Config file first, then it looks for a .obsidian folder and reads your daily notes settings from it. No config and no vault in sight? It asks once and saves the answer.
2. It builds the right dated path Your notes folder, your date format. _Notes/2026-06-11.md or Daily/11-06-2026.md, whatever your setup uses.
3. It appends, never overwrites New note gets a date heading. Existing note gets your text appended as a titled section at the end. Existing content is read first and never touched.
4. It confirms what happened Full file path, created or appended, and the section title used.

Step by step (for first-time users)

1. Open Claude Code anywhere Inside the vault is easiest (it auto-detects .obsidian), but any folder works once the config is saved.
2. Type /obsidian-daily-note plus your text Example: /obsidian-daily-note Pinterest session done, 144 pins posted.
3. First run only: confirm the vault It asks for the vault path and notes folder, then offers to save them so it never asks again.
4. Done The entry is in today's note under a section heading. Open Obsidian tonight and your log is already written.

Section title logic

Honest take

What it does well: Removes the one friction point that kills daily logging: the context switch. It also respects your existing setup instead of imposing one, reading your date format and notes folder from Obsidian's own settings when it can. The append-only rule means there is no scenario where it eats an existing note.

What it does not do: It is not a journaling app. No prompts, no templates of its own, no mood tracking. It also only touches daily notes; it will not file things into other notes in your vault (on purpose, the blast radius of "Claude writes anywhere in my vault" is not worth one saved command). Your text goes in as you wrote it; this is a logger, not a ghostwriter.

When to use it: Every time something worth remembering happens mid-session: a deploy finished, a client said yes, a bug pattern you want to recall. If you already keep daily notes, this makes them complete. If you never managed to keep them, this is the version of the habit that survives.