Kept captures conversations from popular LLM providers and writes them to your filesystem as plain markdown.
Readable, grep-able, yours. One markdown file per conversation, indexed across every supported provider.
curl -fsSL https://kept.work/install.sh | bash
@kept inline if you want manual control over what gets saved.
Capture works against the same DOM and APIs you already use; nothing is scraped you didn't trigger.diff against last quarter. Continue any chat in-app against your own keys, or let the tools
you already trust do the work.
Everything below is in the public release on GitHub. No premium tier, no waitlist. If something is broken, open an issue.
kept-vault-server on npm — an MCP server that exposes your
vault to any MCP-aware client (Claude Desktop, Cursor, Cline, etc.) for read, write, and search.Download the desktop app, sideload the extension, type @kept in a chat.
The vault writes to your home directory; nothing else needs setup.
curl -fsSL https://kept.work/install.sh | sh
chrome://extensions required.Yes. The public release on GitHub is the full feature set; there's no premium tier and no gated build. MIT licensed. If you want to support the project, star the repo or send a friend a link.
Nothing leaves your machine by default. Conversations are stored locally in SQLite and as markdown on your filesystem. If you use Smart Recall or the knowledge graph against a cloud API (OpenAI, Anthropic, OpenRouter), those queries go to that provider — same as a normal API call. Pointing Kept at Ollama keeps everything on-device end to end.
The Web Store review queue takes time, especially for an extension that touches multiple AI sites. The extension is feature-complete; loading it unpacked is straightforward and the instructions are in the install section above. It'll go through the store eventually.
Two things. First: Kept's own agent can call any MCP server you connect, so the AI layer in Kept gets
access to the same tools you'd use in Claude Desktop, Cursor, or other MCP-aware clients. Second: Kept
ships kept-vault-server on npm, which exposes your vault over MCP — so you can plug your
archive into those other clients and read, write, or search it from there.
Not currently. The vendors don't expose write APIs for chat history, and we'd rather not ship a fragile DOM-injection workaround that breaks on every UI redesign. If a clean way to do it shows up, it'll be opt-in and clearly labeled. In the meantime, "Continue any chat in-app" runs the conversation forward against your own API key, against any provider you have one for.
The markdown vault is where Kept writes by default — its own directory under your home folder. "Obsidian export" is a separate, opt-in operation that copies the vault into a folder you point Kept at. The reconciliation logic preserves any edits you've made on the Obsidian side, so re-runs don't clobber your annotations. It's not full two-way sync; if you need writes to flow from Obsidian all the way back into Kept's index, that's roadmap.
Yes. The repo is on GitHub under MIT. Open issues, send PRs, or just star it to help with visibility. The desktop app is Rust + TypeScript; the extension is vanilla JS; the MCP server is TypeScript. The contribution guide is in the repo.
Download the desktop build for your platform, sideload the extension, and type
@kept in any supported chat. The vault writes to your home directory.