What is MemMini
Every AI tool you open is learning you — your voice, your judgment, your projects. Right now that version of you lives inside someone else’s product: scattered across tools, hidden from view, impossible to carry with you. MemMini moves it into plain-English files in your repo, where any AI can read it and no vendor owns it.
What you get, and how it runs
Section titled “What you get, and how it runs”Three words make the rest make sense. MemMini is the framework — open-source, nobody’s mind. Fork it and you get your mind: your voice, judgment, and knowledge in one portable repo. Your mind runs on surfaces — Claude Code, Codex, a chat app, any tool you use — and you bring it up on each by just asking. The full model: Framework, mind, surfaces.
The problem it solves
Section titled “The problem it solves”AI assistants start every session from zero. They repeat mistakes, re-learn your preferences, and can’t build on prior context — so you keep re-explaining things the AI should already know. A plain context file seems like the fix, but you can’t tell if the model is even reading it, and the more you add, the less any single rule lands.
MemMini treats your context as something to engineer, not dump: written for how models actually read, checked against what the AI actually does, and split so the always-on part stays small.
Simple by default, deep when you reach for it
Section titled “Simple by default, deep when you reach for it”Two people open an AI agent. One says “just do X for me” and wants a good result, not a settings page. The other has opinions about everything — git, autonomy, what gets reviewed — and wants every dial in reach. Most tools pick one and lose the other: too simple insults the power user; too complex scares everyone else.
MemMini refuses the trade. The defaults work out of the box — say “run X for me” and a sensible version of you handles it. The depth is still there, but as a knob you reach for, never a wall you hit: every place MemMini decides something for you, you can see the decision and turn it. You start by using it; you find the knobs by reading on.
The biggest knob is how much the agent does on its own. By default it does the safe, reversible work and stops before anything it can’t take back. Turn it toward “just run it” and it acts; turn it toward “show me, ask first” and you approve each step and watch the work happen. Same system — you set the trust.
Stop reading here and you have enough to start. Everything below is a knob, not a requirement. The idea in full: Simple by default.
The two layers
Section titled “The two layers”MemMini separates how to think from what is true.
| Layer | Directory | When it loads | Holds |
|---|---|---|---|
| Intelligence | context/ | every turn (budget-bound) | who you are, how you work, behavioral rules |
| Knowledge | wiki/ | on demand (retrieved) | facts, concepts, contracts, procedures — a linked graph |
Intelligence biases the model toward your voice and judgment on every reply. Knowledge is a library it walks only when a topic comes up — so the deep material never weighs down the lean, always-on you.
The compile step
Section titled “The compile step”You edit small source files; a build assembles them into the artifacts an AI consumes.
context/who.md ┐context/how.md ├─► scripts/compile-context.sh ─► CONTEXT.md (inject into the AI)wiki/INDEX.md │ ENFORCEMENT.md (route in your platform)skills/*/SKILL.md┘CONTEXT.md is the portable “mind.” ENFORCEMENT.md carries the rules a platform
should enforce deterministically rather than hope the model self-applies. You never
hand-edit those two — you edit the sources and recompile. (Full source→artifact
model: Repo layout.)
How work hands off
Section titled “How work hands off”That builds the mind. Here’s how it gets used once more than one agent — or just more than one session — is on the job.
You ask; the agent runs it as a few small steps: Drafting → Up for review → Live. What matters once there’s more than one of them is where the job lives — one shared to-do list inside your repo, not in any single agent’s head. A job one agent hands to the next survives the handoff, you can see whose move it is, and nothing reads as done until the agent receiving it confirms — no work slips through the crack between two agents. That’s be the boss, not the bus: agents pass work through your repo while you watch where it is and give the yeses; no server, no platform.
Walk one job end to end in How work flows here.
For the curious: that shared to-do list is the coordination bus — a plain
.coord/ ledger in the same git as everything else.
The loop
Section titled “The loop”MemMini gets sharper each session without you babysitting it:
- Capture — after a session it records what changed to
.learnings/raw.md. - Distill — between sessions it reviews captures and drafts updates to your files.
- Verify — it checks the change actually moved the AI’s behavior.
- You approve — by default, changes to who you are wait for your yes; routine work doesn’t. That gate is the knob from up top: tighten it to approve everything, loosen it to let more run.
See both flows up close — remember and improve — in How your mind gets smarter.
That’s the whole idea: write yourself in sentences, prove the rules work, own the result.
- Your first outcome — ask in plain words, get a result (no setup)
- Quickstart — pick your level — make it permanent
- Write your first rule — change who the version of you is
- How work flows here — how a job goes from ask to live, and who says yes