
Vault OS
Your vault works the night shift
I built vault-os because my Obsidian vault was a graveyard.
Every day I'd capture notes, ideas, and voice memos. By evening,
nothing was processed. By morning, I'd forgotten what mattered.
So I automated the entire pipeline:
→ Telegram bot routes captures to daily notes by tag (#idea,
#signal, #link) — including voice notes transcribed locally
by whisper.cpp (no audio leaves your machine)
→ At 23:00, a 12-phase nightly agent wakes up. It reads the
day's captures, calls Claude API, synthesizes the thinking,
carries over unfinished tasks, and writes tomorrow's morning
brief automatically.
→ You wake up. The brief is there. Claude worked the night shift.
I used this system daily for 3 months before open-sourcing it.
It's MIT licensed, Windows-native, and built around Obsidian.
GitHub: https://github.com/sabahattink/vault-os
Happy to answer questions about the architecture or how to
adapt it to your own vault structure.
About
I built vault-os because my Obsidian vault was a graveyard. I'd capture notes all day, then wake up the next morning with no memory of what mattered. Nothing was processed. Nothing connected. I was manually writing morn

Comment