Loc: your own PC|Index: one file|Cloud: optional, yours

Claude fixed its own memory. Only you hold the keys.

Every conversation you've had with Claude Code, searchable by meaning, in a single file on your own disk. No third-party repo, no subscription. Secrets are blacked out before anything is saved. Want it on your phone too? Switch on a cloud copy that only opens with your password.

2 ways to run it 3 read-only tools ~900 tokens per recall
recall_search · local index● offline

    Example memories for this demo. Try “stripe”, “backup” or “why”.

    The crew: tap one to say hello.

    The viral one vs. the one we built

    A celebrity memory repo went viral. We built our own instead.

    MemPalace launched in April 2026 with a famous co-creator, a palace metaphor and record benchmark claims. It's local-first and MIT-licensed, which is good. Then people read the code. So we asked Claude to keep the good idea and build something we could read end to end.

    MemPalacerecall (ours)
    Whose codeA third-party repo you install and trustUnder 1,000 lines of Python that Claude wrote for you, which you can read in one sitting
    What Claude can do47 tools, including writes and deletes3 tools, all read-only: search, open a session, list projects
    SecretsStores everything word for wordKeys, tokens and passwords are redacted before saving, and again before showing
    Tool outputSaved as-isSkipped. That's where leaked keys and hidden instructions sit
    Benchmarks“100%” claim withdrawn. Critics say the 96.6% mostly measures ChromaDB's default embeddingsNo leaderboard. Real numbers from real use, below
    BackupsUp to youEncrypted daily, on a second disk and off-site
    On your phoneRuns where you install itOptional cloud connector on your own account, read-only, behind your password
    Sensitive workEverything gets indexedExcluded by name. A health project stays out entirely

    MemPalace facts are from its own README and published reviews as of October 2026. It is open source, runs locally, and its “store everything” idea is sound. This page is about choosing what you trust with your history.

    Measured on a real machine, day one

    Small numbers, on purpose.

    3,272messages from past sessions, searchable on day one
    ~900tokens per search, about the same as Claude reading one small file
    0network calls to search on your PC. The model runs on your CPU
    5.9 MBfor a full encrypted backup of your entire memory
    39secrets caught and blacked out on the first pass
    13automated tests, including restoring with the wrong passphrase
    5 minto index everything the first time. Seconds after that
    1.0000match between the cloud's search model and your PC's, measured on real memories

    How a memory gets made

    From conversation to recall in five steps.

    1. Read

      Picks up every Claude Code session from the transcripts already on your disk.

    2. Filter

      Keeps only what you and Claude actually said. Drops tool output, file dumps and web pages.

    3. Redact

      Blacks out API keys, tokens, passwords and private keys.

      sk-ant-… →

    4. Index

      Keyword search plus meaning search, merged, in one SQLite file.

    5. Recall

      Claude asks. Results come back marked as history, not instructions.

    Two ways to run it

    Your memory stays yours. You choose where.

    “Nothing leaves” is a slogan. Pick a mode and here is the full list for it.

    Your conversation historyOne file on your own disk
    stays
    The search modelDownloaded once, runs offline on your CPU
    stays
    Secrets and keysRedacted before they're ever stored
    never saved
    Sensitive projectsExcluded from the index entirely
    never saved
    The few results Claude readsPart of your chat, like anything else you send Claude
    to Claude
    Encrypted backupsOnly to your own storage bucket, and unreadable without your passphrase
    your bucket
    C:

    Live index

    The working copy. Catches up on new conversations each time you search.

    D:

    Daily encrypted backup

    On a second physical disk, so it survives a Windows reinstall. The newest 14 are kept.

    S3

    Off-site, kept forever

    Uploaded with a key that can only add files. If it leaks, it can't read, list or delete anything.

    Pick this if privacy matters most and you only need memory at your desk.

    One afternoon, start to finish

    Research to pocket-sized in a single session.

    1. Question

      “Is this viral repo safe with all our data?”

      Claude read the repo, the site and the reviews. Verdict: interesting idea, oversold, too much access.

    2. Build

      Its own version

      Index, redaction and a read-only search server. The first search found a decision by meaning, not by keyword.

    3. Audit

      Scanned its own index for leaks

      39 secrets redacted. The only remaining match was a placeholder string.

    4. Protect

      Encrypted backups

      Public-key encryption, so daily backups need no password. Only restoring asks for one.

    5. Off-site

      Upload-only cloud copy

      A dedicated cloud user that can only add files, checked with AWS's own permission simulator.

    6. Remember

      Saved as a skill

      After any reinstall, “rebuild recall” brings it all back, problems and fixes included.

    7. Go mobile

      A cloud copy behind your password

      A redacted copy on the owner's own Cloudflare account, read-only, for Claude on the phone. The cloud's search model matched the PC's at 1.0000.

    Get your own

    Skip the repo. Ask Claude.

    You don't need to install a stranger's memory system. Give Claude Code the first prompt, review what it builds, and add the second whenever you want it on your phone.

    1 · Local only

    Build me a private, local, read-only memory search over my Claude Code transcripts: redact secrets before storing, skip tool output, keyword plus meaning search in SQLite, a 3-tool read-only MCP server, and encrypted daily backups that only need my passphrase to restore.

    2 · Add the cloud, optional

    Add an optional cloud connector to my recall memory: a read-only MCP server on my own Cloudflare account, holding a redacted copy pushed from my PC with a push-only sync key, protected by OAuth and a password stored only as a salted hash, accepting only Claude apps, and using the same embedding model as my PC.