ManuelWarland/MemCore

### Your AI finally remembers.
A single local database of the things worth keeping — decisions, corrections,
"we already tried that" — shared by every AI tool you use, searchable in
plain language, across every project.
No daemon. No cloud. No telemetry. One SQLite file you own.
🇫🇷 Version française
## You've had this conversation
You're deep in a project with an AI agent. It's flying. Then the context window
fills, or you close the terminal, or it's simply tomorrow — and you're back to
square one with someone who has no idea who you are.
You re-explain the constraints. You re-explain, again, that "we already tried
the buffered approach and it deadlocks." You spent an hour last Tuesday
arguing through a design trade-off; today the agent proposes the exact option
you threw out.
And then it gets worse — it starts making things up:
> You: Remember in the payments project, when we fixed the double-charge
> bug? What did we actually change?
> Agent: Yes — we added an idempotency key on the request, moved the retry
> logic behind a mutex, and set the timeout to 8 seconds.
None of that happened. You're not even in the payments repo right now. The
agent had nothing real to work from, so it produced something that sounds
right — and you only catch it because you remember. Most days, you don't.
Now multiply that by every tool on your machine. One agent doesn't know what
you told another. Each wakes up blank, every single time. You have become
the memory. That's the bug.
## MemCore fixes it
MemCore is one small local database of durable facts — the decisions, the
corrections, the "here's how this actually works", the "we ruled this out and
here's why". Every AI tool you run reads and writes the same store.
Ask before you re-explain:
memorysearch "why did we drop the queue-based design"
> project note, from three weeks ago: "queue design deadlocked under load on
> 2026-08-02, reverted to direct calls." — written in a different repo, found
> anyway.
And when there's nothing to find, it says so — a plain no match, not a
confident answer improvised to fill the silence.
Corrections that finally stick. Tell it once that the API returns cents, not
dollars; write it down; the next session — and the next tool — starts already
knowing.
A paper trail. Every write is logged with who and when. Overwrites keep the old
version. Nothing is ever silently lost.
## What it feels like
Coming back:
> You: back — where were we?
> (agent: memoryrecent, memorysearch)
> Agent: Last real change, 40 minutes ago: v1.0.84 shipped, replacement
> parts ordered, waiting on delivery. You were about to start the user guide.
> Nothing else moved.
Not a guess. Not a stale summary. The actual state, reconstructed from what was
recorded.
The cross-project question — answered straight:
> You: we standardised on the EU date format everywhere, right?
> Agent: (memorysearch "date format") Yes — feedback, global scope,
> still current. And there's a follow-up note: the CSV export is the one
> exception, it stays ISO-8601.
Onboarding a fresh agent to a codebase:
memorylist --scope my-project --type feedback
> Every lesson the last ten sessions learned about this repo, in one list —