MemPalace, Milla Jovovich, and what 'built by' means in 2026

On April 6, 2026, Milla Jovovich — yes, that Milla Jovovich — pushed an AI memory system to GitHub under her own account. Within 48 hours it had 7,000+ stars, a claimed 100% on LongMemEval, a 660k-view X thread calling her a grifter, and Ben Sigman (her co-founder, CEO of Bitcoin Libre) publicly admitting “the dev community tore it apart.”

I ship with Claude Code every day. I have an opinion. It’s not the one you’ve read ten times already.

What MemPalace Actually Is

Strip the celebrity layer and the repo is a real thing. MemPalace is an MIT-licensed, offline AI memory system. ChromaDB for vectors, SQLite for the graph, optional local Llama. A 19-tool MCP server that plugs into Claude Code, ChatGPT, Gemini, whatever speaks MCP. The core idea is almost boring in its correctness: instead of asking an LLM to summarize what’s “worth remembering” (Mem0, Zep, Letta), store conversations verbatim and let vector search do the work. No extraction tax. No hallucinated summaries. A “Palace” architecture with rooms/wings/closets maps the method-of-loci onto retrieval, and the README claims this structure alone improves recall by 34% over flat storage.

Then there’s AAAK — “AI-Authored Abbreviation Kit” — a lossy compression dialect pitched at 30x token reduction, readable by any text LLM without a decoder. Two Claude Code hooks auto-save every 15 messages and fire an emergency dump before context compaction. pip install mempalace, done.

If you’ve been building with Claude Code, every one of those design choices hits. The save-on-precompact hook alone is the kind of thing you build after the third time you lose a session you needed.

The Benchmark Table

System	LongMemEval	Cost	Notes
MemPalace (raw)	96.6%	$0	Zero API, local only
MemPalace (hybrid + Haiku rerank)	100% → 98.4%	~cents	Revised after scrutiny
MemPalace (AAAK mode)	84.2%	$0	Regresses vs raw — README now admits this
Mem0	~85%	Paid	LLM-extracted memories
Zep	~85%	Paid	Graphiti-style KG on Neo4j
Letta	N/A	$20–200/mo	Agent-managed

The 96.6% raw number is real and reproducible from the repo. The 100% was not. A community note on Sigman’s X post — now pinned everywhere — states the 100% used “targeted fixes for the 3 failing questions” plus LLM reranking, with a held-out score of 98.4%. The LoCoMo 100% similarly used top-k=50 exceeding the session count; the honest no-rerank number was 88.9%.

To the team’s credit, the README now says this out loud. “We’d rather be right than impressive” is the current commit message energy, and they’ve thanked the critics by name in the acknowledgments. That’s not nothing.

The Controversy Timeline

• April 5–6: Repo goes live. Sigman tweets. Jovovich posts an Instagram reel (“why not create a virtual Memory Palace?”). Claim: first-ever 100% on LongMemEval.
• April 7: HN front page. r/ContextEngineering picks it up. 7k stars in 48 hours, eventually 23k+ per Cybernews.
• April 7: The 660k-view X thread lands. An AI commentator digs the git history, finds Jovovich has 7 commits across 2 days, alleges a ghost dev named “Lu,” calls the whole thing a paid-op. “I can spot a grifter from miles away.”
• April 7: Brian Roemmele deploys MemPalace to his 79-employee “Zero-Human Company.” The meme loop completes.
• April 8: Sigman concedes publicly: “The dev community tore it apart.” The 100% claim gets revised to 96.6% raw. Cybernews runs the “devs aren’t buying it” piece. Community notes stack up on Sigman’s posts describing Jovovich’s involvement as “conceptual or promotional.”
• April 8–10: README rewrites. Honest benchmark caveats. Named thanks to critics. Open issues for ChromaDB pinning, a shell injection in the hooks, a macOS ARM64 segfault.

Two different things happened here, and most commentary collapses them into one. The benchmark criticism was correct and the team corrected it. The “Milla didn’t really build it” criticism is where it gets interesting, and where I disagree with roughly everyone.

The Part Where I Have Skin in the Game

I’m a solo founder. My co-founder writes code I can’t write. I run an SEO/AEO agency and I ship production systems — Telegram CRMs on n8n, content pipelines in LangGraph, cold outreach enrichment in Python — and a huge percentage of the actual keystrokes come from Claude Code. On my best days I am an architect, a reviewer, and a taste function. On my worst days I’m a guy pasting stack traces into a chat window. Both of those days ship.

So when I read “Jovovich only has 7 commits, therefore she didn’t build it,” I recognize the shape of the argument immediately, because it’s the same argument people use to tell me I’m not really a developer.

Here’s the thing. In 2026, “built by” is a spectrum, and the git-blame view of authorship is a 2015 artifact. If the standard is “whoever hit the keys owns the work,” then half the production software shipping right now is ghost-written by Anthropic’s inference servers and we should all update our LinkedIn. That’s obviously absurd. The keys are not where the value is anymore. The value is in knowing what to build, why, for whom, and when to stop.

Did Milla Jovovich personally write the AAAK tokenizer? Almost certainly not. Did she have the lived frustration of a power user who organized files for months and watched AI fail to retrieve them, then read about the method of loci and connect it to vector search? By every account — hers, Sigman’s, the Instagram reel, the RT interview where she calls herself “the architect” — yes. That is a real contribution. In the vibe-coding era, it might be the contribution. Sigman engineered. Claude Code implemented. Jovovich specified and taste-tested. A “Lu” may or may not have helped — the X thread’s allegation is unsourced and the team hasn’t confirmed it, and honestly, if there was a fourth contributor who should be in the README, that’s a credit problem, not a legitimacy problem.

The part that actually bothers me is the marketing. “First-ever 100% on LongMemEval” with asterisks you only learn about after the dev community beats it out of you — that’s the grift shape, and it’s the part Sigman owns. Not the git history. The overclaim.

What MemPalace Tells Us About Vibe-Coding in 2026

Three things, and they matter if you’re building anything right now.

1. The floor has moved, and the new floor is still higher than most people’s ceiling. A working actress with a side interest built, in collaboration with an engineer and an AI, a memory system that beats Mem0 and Zep on the headline benchmark. Not by a little. By ten points. The ChromaDB + SQLite + local Llama stack is not exotic — it’s the kind of thing a competent solo builder could have assembled in 2024. Nobody did. The combination of Claude Code and a clear product vision from a non-engineer is doing something the pure-engineer market wasn’t doing, and the 23k stars are the market telling you so.

2. Benchmarks are marketing now. Treat them that way. This is the uncomfortable part. LongMemEval is a 500-question eval with known failure modes — the fact that “targeted fixes for 3 failing questions” moves you from 98.4% to 100% tells you the test is saturated and the delta at the top is noise. Every vendor in this space — Mem0, Zep, Letta, MemPalace — is going to publish a benchmark graph where they’re on top. Your job as a builder is to run your own data through the tool and see if it remembers what your actual users actually said. I’ll probably do this with MemPalace for a client project next week; I’ll write it up.

3. “Built by” is going to keep breaking people’s brains, and the people who adapt first will win. If your identity as a builder depends on being the person who types the code, 2026 is going to be a long year. If your identity is I find problems worth solving and I ship, the tools are the best they have ever been. Milla Jovovich, of all people, just demonstrated the upper bound of that second category at Hollywood celebrity scale. The lesson for B2B founders in DACH and EU isn’t “hire an actress.” It’s “the bottleneck was never the code.”

What I’d Actually Use It For

Concretely, if I were shipping MemPalace into a project this week — and I’m considering it for curtain.lt’s sales AI — here’s what I’d do:

• Skip AAAK for now. The README itself says it regresses. Raw mode is the real product.
• Run it in MCP mode against a test corpus of real customer conversations (I have Slack and n8n logs to spare) and measure retrieval on questions my team actually asks in practice. Not LongMemEval questions. Real ones.
• Use the PreCompact hook. This one is worth the install on its own if you live in Claude Code.
• Keep an eye on open issue #110 (the shell injection in the hooks) before putting it anywhere near production data. MIT license plus “first week of public exposure” equals “read the code before you trust it.”
• Not bet a client deliverable on it until v3.1 ships with the honest benchmark table baked in and the critical issues closed.

The Bottom Line

MemPalace is a real tool with a real contribution, launched with overclaimed benchmarks by a team that corrected them under fire. The critics who forced the correction did open source a favor. The critics who decided that a non-engineer “architect” is automatically a fraud are fighting the last war.

In 2026, the interesting builders are going to be the ones who can hold two ideas in their head at once: this tool is genuinely useful, and the marketing around it was dishonest. Both. At the same time. Without collapsing into hype or dismissal.

That’s the muscle worth building. The code, increasingly, builds itself.

If you’re a founder, CTO, or operator trying to figure out what vibe-coding means for your business — not as a slogan but as an operating model — that’s the conversation we have at areza.digital every week. We help European businesses ship production AI systems where the code is increasingly the cheap part. Book a 30-minute discovery call →

---

Sources:

• MemPalace repo: github.com/milla-jovovich/mempalace
• Cybernews: “Milla Jovovich creates MemPalace AI memory tool with ‘perfect score’ on benchmark, but devs aren’t buying it”
• Bitcoin News: “Resident Evil Star Milla Jovovich Builds AI Memory Tool With Engineer Ben Sigman”
• mempalace.tech origin story and benchmark notes
• RT: Jovovich interview on the architect framing
• Community notes on Sigman’s X launch thread (held-out 98.4%, LoCoMo 88.9%)

Written by Nikita Janockin, founder of areza.digital — a human with a strong opinion, drafted with Claude Code, as is everything else around here. Last updated April 10, 2026.