Keel

The markdown-on-disk approach is underrated. Most "local AI" tools still phone home for context storage, which defeats the point. One thing I'm curious about: how does Keel handle memory across different models? If I switch from Claude to Ollama mid-project, does the context transfer cleanly or do you lose the thread?

Memory that belongs to the user is a great trust signal — most AI tools make it feel like the data is theirs, not yours. How granular is the control? Can users edit or delete specific memories, or is it all-or-nothing? Curious how you've approached that UX

Hey Medha — 'the day the model gets deprecated, my brain goes with it' should be on the homepage. As a fellow solo founder, looking forward to the Windows build.

@medhaforcebewithyou congrats for the launch l 🚀
As a user, where can I actually see what the assistant remembers about me, and can I delete things if I want to?

Hey Product Hunt 👋I built Keel because every AI tool I tried had the same problem: my context lived inside someone else's product. The notes, the history, the slowly-built understanding of my projects - all trapped behind one vendor's login. The day that model gets deprecated or that company changes direction, my brain goes with it.Keel flips that. Your memories live on your disk, in plain markdown, in a folder you own. You can open them in any editor, back them up, version-control them, move them between machines. The model is the part that's interchangeable - Claude today, GPT tomorrow, a local Llama on a flight. The assistant changes; your context doesn't.A few things worth knowing:It's a real desktop app for Mac and Windows (Electron + React + TypeScript).Bring your own API key. No telemetry. No account. No cloud sync (yet).It's a v1 beta - Apple Silicon only, no Windows/Linux yet, no mobile.It's a one-person project. I'll read every comment here today; I can't promise to build every feature (yet).Would love your feedback. Thanks for taking a look.