Personal memory layer
Stop explaining yourself to your tools.
You already save what you like. We make it something any model can answer from.
What it holds
Everything you already collect.
One memory, three domains, and the specific things each of them keeps. This is a real profile shape, not a diagram of one.
How memory works
You don’t store files. You store associations.
Encoding
You keep what you stopped on. Saving is already a judgement.
Consolidation
Episodes fade. The shape they share is what stays.
Retrieval
A cue arrives, and the related material comes with it.
Why a layer
A brilliant stranger, every time.
A task that takes ten or twelve prompts today should take two or three with a memory connected. That is the number we are trying to move.
Join the waitlistEvery session opens cold
You re-explain your stack, your conventions, and the thing you said you hated last week. Then you correct the output back toward yourself, one prompt at a time — and the window closes and takes all of it.
Chat history is not memory
A transcript is a pile of episodes. What you need is the pattern underneath them: the traits that recur across everything you have ever approved of.
Nobody fills in a form about their own taste
Ask someone how they like things and you get platitudes. Watch what they save for a month and you get the truth. So we never ask — no naming, no tagging, no describing.
Corrections are the compounding part
Anyone can analyse the same screenshots. Nobody else has the fifty times you said “no, not like that.” That record is yours and it gets better the longer you use it.
Where context comes from
The habit already exists.
You like, bookmark and save every day, then do the retrieval by hand. We capture the output of something you already do.
What we’re building
One memory. Every model you use.
Many saves in, one profile out, read directly by whatever agent you already work in. The layer underneath does not know or care what kind of thing you collected.
The first vertical
Design taste is the wedge, not the ceiling.
Taste is real and almost impossible to write down, and images are self-contained to capture. It ships first for those reasons — not because the layer stops there.
Design taste
Spacing, palettes, type, the components you keep reaching for.
What you read
Threads, highlights, papers, the arguments you kept.
How you build
Naming, error copy, test patterns, the stack you default to.
How you write
Tone, structure, the phrases you actually use.
Roadmap
Where the line has reached.
The layer had to work before capture was worth building, and capture has to be frictionless before retrieval means anything.
The layer
Browser capture
One-command setup
Import your saves
Retrieval unasked
Beyond design
$MEMORY
The people who use it cover the cost of running it.
Fees generated by $MEMORY go to the cost of running True Memory. Holding it earns free usage.
Planned, on the Robinhood chain. No sale is open and no date is set. Nothing here is an offer or investment advice — True Memory works without a token.
Start now
Your AI forgets you. Give it a memory.
Opening in small batches so the first profiles get looked at properly.