Imagine needing an export button to access your own memory 🤔
That started feeling a little ridiculous to us.
Your meetings happen in real life. Your decisions, ideas, customer context, and follow-ups are yours.
But somehow, once a notetaker captures them, they often just stay there. If you want them somewhere else, you export. Download. Move files around. Or, if you’re a power user, build a workaround.
People are literally doing this today just to get their meeting history into Obsidian, Claude, or a folder they control.
So we built Local Folder in Krisp.
When your meeting ends, Krisp can automatically save the transcript and recording to a folder on your computer.
From there, use it however you want.
Obsidian. Claude. Local AI. Client folders. Your own scripts and workflows.
Your notetaker can take the notes.
It doesn’t need to keep them.
Replies
The export button is the tell. If getting your data out is a feature and not the default, it was never really yours. (I build transcription, we run our own servers for the same reason.)