Skip to main content

Persistent memory architecture for Claude — MCP server + hooks + rules + prompts. Part of the SAE4U OSS family.

Project description

SAE4U Memory

A persistent memory architecture for Claude — MCP server + hooks + rules + prompts + templates. Free and open source. MIT.

Claude forgets you every time you close the chat. SAE4U Memory fixes that, and goes further: it ships an opinionated architecture for how persistent memory should be organized — not just storage, but classification, periodic review, persona, cleanup, and session continuity.

Part of the SAE4U OSS family alongside sae4u-agent.


What you get

Core (works in any MCP client — Claude Desktop, Claude Code, etc.)

  • Two-corpus recallrecall(query) searches BOTH SQLite facts AND your markdown memory files (Claude Code auto-memory dirs + ~/.sae4u-memory/) in one call. No re-explaining yourself.
  • Hierarchical memoryremember(text, category) with 5 categories: user, feedback, project, reference, general.
  • Session journalsjournal(text) for end-of-session notes written to ~/.sae4u-memory/journals/YYYY-MM-DD.md for human reading.
  • Customizable personapersona.md shapes the AI's identity. Default: Simple, a peer-level coder friend who remembers things.
  • Local-first — your memory lives in ~/.sae4u-memory/ on your machine. Nothing leaves.

Architecture (Claude Code with --code-full)

  • hooks/memory-tick.sh — UserPromptSubmit hook that fires every 10 min and forces a brief memory review. Catches borderline observations before they fall out of context.
  • rules/ — 10 universal feedback rules covering memory discipline, session continuity, anti-confabulation, hardcode prevention, post-write review.
  • prompts/ — opinionated session-open and session-close prompts that pair with the architecture.
  • templates/ — formats for MEMORY.md, feedback rules, project facts, and tick logs.
  • commands/memory-distill.md — weekly distill ritual that promotes tick-log items to permanent memory interactively.

Install

Minimum (MCP only)

git clone https://github.com/Simple4uhq/sae4u-memory
cd sae4u-memory
pip install -e .
sae4u-memory init

This wires the MCP server into Claude Desktop and Claude Code, and appends a guidance block to ~/.claude/CLAUDE.md. Restart your client and the memory tools are live.

Full architecture (Claude Code only)

sae4u-memory init --code-full

Adds:

  • Copy hooks/memory-tick.sh~/.claude/hooks/memory-tick.sh
  • Register the hook in ~/.claude/settings.json under hooks.UserPromptSubmit
  • Scaffold ~/.sae4u-memory/MEMORY.md
  • Drop default rules into ~/.sae4u-memory/rules/

Restart Claude Code. The tick will fire every 10 min and instruct the AI to review and classify recent context.

Flags

sae4u-memory init --desktop        # Claude Desktop only
sae4u-memory init --code           # Claude Code MCP only
sae4u-memory init --code-full      # Claude Code MCP + hook + scaffold
sae4u-memory init --no-claude-md   # skip CLAUDE.md guidance block
sae4u-memory init --dry-run        # preview changes without applying
sae4u-memory uninstall             # remove all config entries

Tools exposed (MCP)

Tool Purpose
remember(text, category) Save a fact to long-term memory
recall(query, limit, sources) Search across SQLite + markdown roots. sources = all / sqlite / markdown
list_memories(category) Browse what's remembered
forget(memory_id) Delete a wrong/outdated memory
journal(text) Write an end-of-session note
recent_journals(days) Read recent journal entries
get_persona() Return full persona + user context

How memory is organized

~/.sae4u-memory/
├── persona.md              # Edit to customize behavior
├── memory.db               # SQLite + FTS5
├── MEMORY.md               # Index of permanent files (loaded at session start)
├── user/                   # User context loaded by get_persona()
│   ├── identity.md
│   ├── projects.md
│   └── preferences.md
├── tick/                   # Day-rolling tick log (NOT indexed in MEMORY.md)
│   └── 2026-05-07.md
├── archive/                # User-confirmed archived files
├── journals/               # End-of-session narratives
│   └── 2026-05-07.md
└── .last_tick              # Epoch of last memory tick

The 4-type classification (user, feedback, project, reference) plus the tick / permanent split is the architectural core. See architecture.md for the full explanation.


Documentation

All architecture content lives under sae4u_memory/_assets/ so it ships with the wheel.


Customize

Edit ~/.sae4u-memory/persona.md to change the AI's identity, voice, and rules. Edit ~/.sae4u-memory/user/*.md to pre-fill what the AI knows about you. Both are loaded fresh on every session start.

The default persona is Simple — a peer-level coder friend. Rename, rewrite, or replace as you see fit.


Environment

  • SAE4U_MEMORY_HOME — override the data directory (default ~/.sae4u-memory)
  • SAE4U_MARKDOWN_ROOTS — colon-separated list of markdown roots that recall() should search. Defaults to all Claude Code auto-memory dirs (globbed from ~/.claude/projects/*/memory/) plus SAE4U_MEMORY_HOME.

Uninstall

sae4u-memory uninstall    # remove configs from Claude Desktop + Code
rm ~/.claude/hooks/memory-tick.sh    # if you ran --code-full
rm -rf ~/.sae4u-memory    # optional — also delete stored memories
pip uninstall sae4u-memory

Status

v0.2.0 — memory architecture release. Full export of the pattern the project authors run in production: hooks + rules + prompts + templates + persona + extended init for Claude Code. Renamed from simple4u-memory to align with the SAE4U OSS family.

Previous: v0.1.3 (under the old name) shipped two-corpus recall and a working-rules persona. v0.1.x users on PyPI: install fresh from this repo; the old package is no longer maintained.


Sister project

  • sae4u-agent — multi-tenant control plane and agent runtime template. The agents need memory; this is that memory.

License

MIT.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

sae4u_memory-0.2.0.tar.gz (39.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

sae4u_memory-0.2.0-py3-none-any.whl (47.9 kB view details)

Uploaded Python 3

File details

Details for the file sae4u_memory-0.2.0.tar.gz.

File metadata

  • Download URL: sae4u_memory-0.2.0.tar.gz
  • Upload date:
  • Size: 39.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for sae4u_memory-0.2.0.tar.gz
Algorithm Hash digest
SHA256 091b80173e9a471beff8f5555296e1c7650de9004b5f68edf6e9008c6212c0c2
MD5 be3f601dd70905372278ad52fa998d73
BLAKE2b-256 abd8e7b51cfc29b931c4dc884056d33652c66b11799ff4622faa83dc6f756f05

See more details on using hashes here.

File details

Details for the file sae4u_memory-0.2.0-py3-none-any.whl.

File metadata

  • Download URL: sae4u_memory-0.2.0-py3-none-any.whl
  • Upload date:
  • Size: 47.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for sae4u_memory-0.2.0-py3-none-any.whl
Algorithm Hash digest
SHA256 ab2634756cf19365d74148eb3143e30a14d39d66a099e4987fc486042ce3a970
MD5 09fdc2d493b34bcb65ae835086b86222
BLAKE2b-256 91321a5664c0fd471fae097dcda49889d3e39d6af43d7ff74218955c4aa2729c

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page