Kept

Your AI chats, saved as Markdown locally with no cloud

Mac

Productivity

Artificial Intelligence

Visit WebsiteSee on Product HuntGithub ⧉

Local Markdown is a great default. The next hard thing, I think, is deciding what should graduate out of the chat archive.

A raw AI conversation has a lot of dead ends and temporary context in it. The really valuable pieces are usually decisions, reusable examples, prompts that actually worked, and constraints you don’t want future sessions to forget. I’d love to see Kept make that boundary explicit: archive everything, but help people mark which parts are “memory,” which are just transcript, and which are stale enough to stop influencing future work.

Hi Tibor, congrats! the missing piece! markdown + obsidian-compatible was always going to win. when does the knowledge graph beat full-text search in practice? "where did i decide X" feels like full-text. "what path got me there" feels like graph. is that the split? good luck with your launch.

Local Markdown feels like the right default for AI chats because the valuable part is usually not the chat UI, it is the reusable context you want to move into notes, docs, or a repo.

The detail I’d be most curious about is export fidelity: do you preserve model name, timestamps, attachments, code blocks, and source links in a predictable frontmatter/schema? That would make it much easier for teams to treat chats as a durable knowledge base rather than another archive.

Local-first for AI chats just makes sense. The vendor lock-in is real, you have a great prompt and a week later it's gone inside some UI.

Did the same building a finance app, kept everything on-device instead of a server. The annoying part was syncing across devices without running my own cloud.

How are you handling that with a local vault? Or is it single-machine for now?

Claude people think that HTML is better. Not as easy to edit, of course. What’s your opinion?