The question

Chapter one

you, to your assistant

What did we decide about the launch?

your assistant 0.09s

Launch moved to the list first. Price stays sealed until someone joins. Decided with Mohamed at 14:42, and the two rejected options are in the same note.

out of sessions/2026-08-04-1442.md projects/memory-engine.md
ask it something else

This is the real folder this page was written in, answering questions about itself. Yours starts empty, and fills the first time you run it, from the chat histories already sitting on your Mac.


It answers because it was writing the whole time. The Memory Engine writes down every session you have with an AI, by itself, and saves it as dated notes in a folder on your own Mac. It hides your passwords before anything is sent, and it searches Arabic as well as it searches English. Nothing is uploaded, there is no account to make, and nothing about you is tracked.

The forgetting
Chapter two

Every session ends the same way

Everything you told your AI today gets deleted tonight. You explain the project, the client, last week's decision; the session does the work, closes, and takes every word of it with it. Tomorrow's session is a stranger who has never met you.

Notes were supposed to fix this. But notes depend on you, on your busiest day, summarizing things you are still too deep in to summarize. The gap was never discipline. It is that the writing stayed manual in a workflow where nothing else is.

set these to your actual week

6
7
12
175hours a year explaining work you had already explained
18,000,000pages of background a year, paid for twice

Your three numbers, over 250 working days. Anthropic measured the other half of this: when the assistant can read a folder of notes instead of starting from nothing, it gets 39% better results on long jobs and needs 84% less of the background you keep re-sending.

It writes itself
Chapter three

So the file writes itself, and it will not write your keys

You type nothing. The moment a session ends it gets written down, and every fifteen minutes it goes back over the chat histories of every assistant it reads, in case one of them crashed or you forgot to close it. Below you can watch one of those rounds, and the filter that hides your passwords before anything is sent. Both of them are live on this page.

one round, start to finish

runs by itself, every 15 minutes idle
  1. reads every conversation5 assistants checked, 922 sessions found
  2. is this worth keeping160 read, and left alone
  3. hides your passwords17 kinds of key, plus anything that looks random
  4. writes the summaryyour words go over on their own, nothing attached
  5. files it in your folderswritten safely, and never written twice
  6. saves a version you can undo504 saves in the last seven days

Those six steps are the real order it works in, and the figures beside them were counted on my own machine on 2026-08-18. The line at the end is the shape every line takes: a date, something that happened, and the file it went into.

and this is what stands between them and the model

what the model would receive

    Nothing you type here leaves this page. This check runs inside your own browser, and it is the same one that runs on your Mac before anything is sent to an assistant. It knows seventeen kinds of password and key by sight, and it also catches the random looking strings that match nothing it has seen before. If the check itself fails, nothing is sent at all: the session is held back and you are told plainly that something went wrong. It never sends half a hidden password.

    What comes out of all that is not a database. It is ordinary notes in your own folders: one running log, a file for each person, a file for each project. Read every line it wrote, change it, delete it, or open the folder in a notes app like Obsidian. It is yours, and it is the part that stays when everything else is gone.

    Every assistant
    Chapter four

    Whichever assistant you happen to be using

    Every vendor shipped memory in 2026. Not one of them shipped a memory another assistant can read, and the vendors who ship two or three cannot read across their own. Pick a source. Then throw the switch.

    Five assistants, five memories, and no wire between any two of them. Anthropic ships three of them, and none of the three can read the other two.

    • ~/.codex/memoriesits own, and off by default
    • Cowork project memoryinside one project, nowhere else
    • ~/.claude/projects/…/memoryone folder, one project
    • undocumentedwhatever it keeps, it keeps
    • a cloud profileno export, no file

    ChatGPT Codex

    These counts are from my own folder, taken on 2026-08-18. Cursor reads zero because it does not publish where it keeps its history, so an update to the app can move it; the health check tells you the day that happens rather than months later. Where an assistant announces the end of a session, that is used. Where it does not, the sweep finds the session anyway, which is why a crashed session and a sleeping laptop change nothing.

    In your language
    Chapter five

    And it answers in the language you think in

    you typeذاكره
    both fold to الذاكره الذاكرة

    Arabic is not a translation layer here. It knows the same word gets written several ways, with a hamza or without one, and it learns names the way you type them, so it finds the Arabic name as reliably as the English one. The two words above were matched by the same code running in the box beside this, so go and try it.

    look something up

    try it, then search again

    This box searches the page you are reading, the same way the engine searches a folder of your notes. The switch beside it does what the product does to a client folder.

    What it has kept
    Chapter six

    Client work stays isolated

    Everything it has kept for you 0 / 922 sessions kept
    762 written into your notes 160 read, and deliberately skipped a pretend client folder
    launch
    sessions it found0
    written into your notes0
    read, and deliberately skipped0

    Counted on 2026-08-18. The numbers are real. The arrangement is not a timeline.

    Any folder can be walled off. What is inside it never comes out, and what you name never goes in: not in search, not in summaries, not when it reads. Client work stays where you put it.

    The switch in chapter five is real. Flip it back and search again.

    The record
    Chapter seven

    The numbers behind this dossier

    Seven weeks of it running, counted straight out of my own folder on 2026-08-18.

    1,151times it woke up and checkedEvery fifteen minutes, day and night. Five of those rounds stopped with an error, every one of them because an assistant changed the way it saves its chat history. None of them crashed, and not one of them ever failed to hide a password.
    2,476things written down about your workAnchored onto 65 person and project pages, each carrying a verbatim quote from the session it came from.
    216things it was not sure aboutThis is the only number here that is not a boast. Anything it is not sure about stops and waits for you, so ignoring the box makes it grow. That is the price of something that refuses to guess, and it is why the other two numbers are worth anything.
    recall, measured today0.09s to 0.17s
    the same in Arabic0.09s
    files it wrote for me1,044
    summarising, seven weeks, every assistantnothing above the subscription
    every conversation kept, with the passwords stripped out209 MB
    checks that must pass twice before I ship an update223

    Where it loses. It looks for words, not for meanings. Ask it something using words that appear nowhere in your notes and it can come back empty, and three of the alternatives below do that part better. It is switched off here on purpose, behind a list of every question it failed to answer, and on my own folder that list is nearly empty. A fast wrong answer is worse than no answer, and that is the whole reason you can trust the numbers above.


    what each way costs over three years

    List prices read off the vendors' own pages on 2026-08-18. Every bar is drawn to the top of its range, because that is the tier a working professional actually lands on.

    Cloud memory services$684 to $17,100

    They rent you the remembering, by the month, and there is no last month. Your notes live in their database, as an asset of theirs.

    Done for you builds$10,000, plus the retainer

    An agency configures somebody else's software around your folders. What you own at the end is a configuration and an invoice.

    Second brain cohorts$6,000, and no software

    Teach the method and ship no machinery. You leave with a document, and the writing is still yours to do every morning.

    The premium kits$2,497, one time

    The folder convention and some agent prompts. None of the surveyed ones ship automatic capture, isolation, review before a line is written, or Arabic.

    The Memory Enginethe same payment

    Runs on your machine, so there is nothing to meter and nobody to bill you next year. Every other row has a column for what it takes from you in 2029. This one does not have that column.

    The last bar is the only one on this chart not drawn to scale, for the obvious reason. Every other figure is the published rate multiplied by thirty six months.

    What happened to the others
    Chapter eight

    What happened to the ones that promised to remember for you

    Not an anecdote. A pattern, seven times in eighteen months. When a memory product dies the memory dies with it, because it was never in a format you held.

    2025-04

    Zep Community Edition

    The free self-hosted edition was deprecated. The cloud tier, $1,250 to $3,750 a year, stayed.

    2025-07-22

    Bee

    Bought by Amazon, then brought back at CES 2026 as a $50 wearable that thinks in their cloud.

    2025-12-19

    Rewind and Limitless

    Bought by Meta, capture switched off, and the service in the EU and the UK ended outright.

    2026-03-07

    Reor

    Archived, and that is the whole obituary. Dead, and quietly.

    2026-04-15

    Khoj Cloud

    Shut down, a year after positioning itself as the self-hosted second brain.

    2026

    OpenMemory

    Superseded by its own vendor, which is the polite version of the same thing.

    2026

    Personal.ai

    Turned to enterprise contracts, and out of reach of anybody who is only one person.

    no date

    A folder on your disk

    Ordinary notes, in a folder you named, and a search list that rebuilds from them in a minute. There is nothing here anyone can shut down.

    Every row above was somebody's second brain, and every one of them held the notes inside a company. Yours does not. If I disappear tomorrow the files on your disk open exactly the same way, which is the only promise in this dossier that does not depend on me being here to keep it.

    Reasons to walk away
    Chapter nine

    Do not buy this if

    A page that only lists strengths is no use in a buying decision. These are the reasons to walk away, in the same words the kit's own documentation uses, which you can read before you pay.

    1. You want a notes app with an AI button. This is machinery around an assistant, not an editor.
    2. You only work on a phone or a tablet.
    3. You want it finished this afternoon. On its first run it goes back over the conversations already on your Mac, and it builds up from there. The folder you start today is the one you will be searching in a year, and every week you wait is a week missing from it.
    4. You will never look at the suggestions box. Anything it is not sure about stops and waits for you, on purpose. That costs you a few minutes a week, and it is exactly why you can trust everything else it wrote.
    5. You need a shared folder for a team, a phone app, or cloud sync. This is one person, one Mac, and their own work.
    6. You want it to cost nothing at all to run. Reading, searching and remembering are all on your Mac and free. Writing the summary is a request to your assistant: nothing on top of the subscription you already pay for, or around twenty cents on a busy day if you would rather it used its own key, under a daily limit you set.
    7. You are happy losing the last two years of decisions and would rather keep explaining them from memory.
    Colophon
    before you decide

    What setting it up actually looks like

    • It runs on a Mac. Not Windows, not a phone, not a browser tab. If you are on Windows, this is not for you yet, and I would rather you read that here than find out after paying.
    • You need one assistant you already use. ChatGPT Codex, Claude Cowork, Claude Code, Cursor or Gemini. Any one of them is enough, and it reads all five if you have all five.
    • It is one sitting, not a project. You paste a single line, it asks you a few plain questions, and it puts everything it needs in place. If you have never opened the terminal on your Mac, you will open it once, and the guide shows you exactly where.
    • You do not start from an empty folder. The first run reads the conversations already sitting on your machine, so on day one there is already something to search.
    • The few minutes a week are real. Anything it is not sure about waits for you to say yes or no. That is the honest cost of something that refuses to guess, and it is the one habit that decides whether this is still working in a year.
    two ways to take it

    The machine, or the machine and the habit

    option one

    The Engine

    The whole system, on your own Mac, yours to keep. Nothing on this page is held back for the option beside it: the same reading of every session, the same hiding of passwords, the same walls between clients, the same Arabic, the same files. You set it up from a written guide I keep current, and the first run fills your folder from the conversations already on your machine. Most people will take this one, run it for a week, and never need to hear from me again.

    option two

    The Engine, and the first month with me

    The same engine, and the one thing a download cannot ship: the habit of keeping a second brain, and someone who already has one. We set it up together on a call, and it is running in your own folders before we hang up, whether or not you have ever opened a terminal. Then we shape it around the clients and projects you actually have, in the language you think in, and I stay close while the first month decides what this becomes.

    • Everything in option one, switched fully on. Nothing here exists only in this option.
    • One call where we set it up together, and it is running in your folders before we hang up.
    • Your folders built around your real clients and projects, with the walls set for your actual client names instead of left on their defaults.
    • We run the first pass over the conversations already on your Mac and read what it wrote about you together, so you correct it instead of trusting it blindly.
    • Two sessions in the first month, with your own folder open in front of us.

    A limited number of places, filled in the order the list was joined. This one closes soon, and when it does this page will say closed.

    The engine is identical in both, and it will keep writing faithfully either way. The only thing option one does not include is a person who opens your folder with you in week six and names the one habit you let slip, which is the whole difference between keeping a second brain and owning software for keeping one.

    Colophon

    The list buys first

    Checkout opens at launch, and the list sees the launch price before this page shows it to anyone else. The email gets the launch mail and your download. The WhatsApp number is where the heads up lands the day it goes live.

    sealed Checkout opens on launch day, and the list is served first. The moment it opens, this same button becomes the buy button.
    which one do you want
    which machine do you work on

    Stored the way this product stores things: one row, on a list only I can open and that this page itself cannot read back. No newsletter.