mnemo working title

A private memory for your AI

Your assistant forgets
everything by morning.
This one sleeps on it.

A local, private memory that captures what matters during the day and quietly reorganizes it overnight — so the tools you work with stop asking you the same things twice.

LIVESOn your machine
CONSOLIDATESWhile you sleep
COSTS YOUOne line, then nothing

The problem

Capable, and completely amnesiac.

Today's assistants are brilliant for an hour and blank by the next session. You re-explain the same preferences every week. The knowledge was never missing — it was just never consolidated. Nothing plays the role that sleep plays for a mind.

Sure — where should refunds be categorized?
As income-negative. I told you this on Monday.…and the Monday before that
Got it. Starting fresh — remind me of your naming rules?
(again)

See it — 38 seconds

Watch the night do the filing.

How it works — today, and for real

Capture in a second. Consolidate overnight. Recall without asking.

Modeled on how memory actually works: a fast, literal record of the day, reorganized during sleep into durable understanding — and a small, always-ready core so the things that matter surface without a search.

Movement one

Capture

Notice something worth keeping? Drop one line and move on. No folders, no tags, no decisions — friction at capture time is how facts get lost. Filing is the night's job, not yours.

one filezero ceremonyan inbox
Movement two

Sleep

Each night, shortly after three, it reads the day back, melts duplicates into one, and files and links what's new. On a deeper weekly pass it checks its oldest facts against reality and archives what's gone cold — the way rest turns a jumble into something durable.

nightly · replaymergelinkweekly · verifyarchive
Movement three

Recall

A tiny always-loaded core holds only what must be present before any work starts — so the rules that matter win attention instead of drowning. Everything else stays one short hop away, reachable on demand.

small coretwo hops, maxno search needed
Local store
Plain files and local git. No cloud service holds your memory.
Private
A wall built to keep confidential terms from crossing between banks.
Switchable
Off by default until you opt in. One line to enable.
No lock-in
Just text files. Auto-loads for Claude today; any tool can read them.
What we're building next

A memory that remembers. Next, a guardrail that acts on it.

Perfect recall isn't the whole story. A rule can be right there, in plain view, and still get ignored in the moment — and no amount of storage fixes that. The next chapter is the part that does: a guardrail that turns hard-won lessons into something the system can't quietly skip.

01

No claim without proof

"Done," "tested," "it's fine" — only when the evidence is attached. A gate that won't let a confident-but-unchecked answer through, because the sharpest failures aren't missing facts. They're claims made without the check.

In design
02

Learns how you push back

Not a fixed list of complaint phrases in two languages. The system learns the words you actually reach for when something's wrong — so a correction never slips by just because you phrased it as an argument instead of a sigh.

In design
03

Finds the pattern before you're annoyed

The same small mistake on Tuesday, again Thursday, again Sunday. You shouldn't have to notice — the recurrence itself is the signal. It surfaces the repeating flaw on its own, and proposes the fix before frustration does.

In design
04

One memory, many people

When it's shared, person A hits a wall, then B, then C — and none of them says "again," because for each it's the first time. Only the memory sees all three. It connects complaints nobody knew were connected, and fixes the wall once.

In design
Held to its own standard. This is a roadmap, not a receipt. What the page describes as working today is running; this section is what we're designing next, marked as such. One honest caveat: your memory is stored locally, but the nightly consolidation runs through your AI assistant — the same one you already use, not a new service. A system whose whole point is evidence over claims doesn't get to advertise the future as if it already shipped, or hide where the work happens.

What it's built on

Four commitments, not features.

01
Evidence over claims
A result is only "done" when the proof is attached. Otherwise it says so.
02
Local by default
Your memory lives on your machine — no cloud service holds it. Consolidation runs through the same AI you already use; nothing new to trust.
03
Yours to switch off
Opt-in, reversible, and inert until you ask for it.
04
Honest about limits
What it can't do yet is written down, not hidden. Including here.

The short version

Give your AI a memory
that actually sleeps on it.

Capture what matters, let the night do the filing, and stop repeating yourself. The recall works today. The guardrail that keeps it honest is what comes next.