Gulper

Your vault should run itself. Here’s how to get there in one step.

This setup is built to remove friction for people who live in Obsidian: engineers, tinkerers, and anyone whose notes, tasks and kanban boards all sit in one vault. The quickest way to see what it can do is to install a single launchd job and watch your vault commit itself to git, without you lifting a finger.

Two quiet workhorses

Everything rests on two tools. launchd is macOS’s built-in scheduler. It starts jobs at set times, and it knows when your Mac sleeps and wakes. fswatch watches your files and reports the moment one is created, edited or deleted. Between them they answer the two questions every automation has to answer: when should something run, and what just changed?

Start here: automatic git commits

Load one launchd job that checks the vault every few minutes and runs git add and git commit only when something has actually changed. It takes about five minutes to set up, and from then on every edit is versioned and every mistake can be undone. It’s the clearest proof that the vault can look after itself.

Then build on it

• Watch the kanban board. fswatch sees a new card the second it lands, and a script links it, files it or turns it into a note.
• Assemble the morning brief. Scripts gather your tasks, tickets, mail and news into a single note before you sit down.
• Catch up after the lid closes. When the Mac wakes, launchd runs any jobs it missed while it was asleep, so nothing slips through.

The goal is less clicking, less remembering, and a system that’s already done the boring parts by the time you open it.

Interesting plist generator I came across https://launched.zerowidth.com