Mat Silverstein

I created the #5 most installed claude desktop extension, but I really truly didn't mean for this truncation...

Now paying Granola $18/mo to upload my meeting audio to their servers. So I built my own thing. It's 7 MB. Everything runs locally. Works with @tobi's QMD for super fast search, PARA method second brain setup for organized people, projects, entities, @obisidan, CLI, claude code, codex, Claude Desktop. Before a call with Biff it pulls your last 12 conversations, shows you pricing came up 5 times in 2 weeks, and reminds you that you owe Biff a doc from Friday. After the call it asks if you got what you came for. You just ask "what did Biff say about pricing last week" and it pulls from your transcripts. No API key needed, use your existing subs. The meeting prep feature came from messing around with @garrytan's gstack skills. His /office-hours pattern forces you to be specific instead of accepting vague answers. I stole that idea and applied it to meeting prep and post-meeting debrief. It's called Minutes. Rust, whisper.cpp, Tauri. MIT licensed. First real release on github.

how to use obsidian + claude code to build a 24/7 personal operating system and build your startup: 1. write everything in markdown (daily notes, projects, beliefs, people, meetings) 2. link your notes together so they mirror how your brain actually thinks. 3. install obsidian cli so claude code can read your entire vault + the relationships. 4. stop reexplaining projects every session. use reference files instead. 5. build custom slash commands: /context → load your full life + work state /trace → see how an idea evolved over months /connect → bridge two domains you’ve been circling /ideas → generate startup ideas from your vault /graduate → promote daily thoughts into real assets 6. keep a strict rule: human writes the vault. agents read it, suggest, execute. 7. let claude aka clode surface patterns you’ve been unconsciously circling for years. 8. delegate from inside your notes. one sentence in obsidian → agent handles the rest. 9. treat writing as leverage.the more you write, the more context your agents have. 10. understand this:markdown files are the oxygen of llms. i really enjoyed seeing how to use obsidian thanks to @internetvin vin uses ai like a thinking partner wired into his life’s work. 99.99% of people won’t do this because it requires reflection + setup. but once the vault exists, the agent stops being generic. it starts thinking in your voice. episode is live on @startupideaspod (more there) this one is different. send this tweet to a friend. im still processing how game changer obsidian + claude code is, maybe you too watch

Now paying Granola $18/mo to upload my meeting audio to their servers. So I built my own thing. It's 7 MB. Everything runs locally. Works with @tobi's QMD for super fast search, PARA method second brain setup for organized people, projects, entities, @obisidan, CLI, claude code, codex, Claude Desktop. Before a call with Biff it pulls your last 12 conversations, shows you pricing came up 5 times in 2 weeks, and reminds you that you owe Biff a doc from Friday. After the call it asks if you got what you came for. You just ask "what did Biff say about pricing last week" and it pulls from your transcripts. No API key needed, use your existing subs. The meeting prep feature came from messing around with @garrytan's gstack skills. His /office-hours pattern forces you to be specific instead of accepting vague answers. I stole that idea and applied it to meeting prep and post-meeting debrief. It's called Minutes. Rust, whisper.cpp, Tauri. MIT licensed. First real release on github.