SAE4U Memory
Provides persistent memory for Claude with hierarchical categorization, cross-corpus recall, session journals, and customizable persona, enabling memory continuity across sessions.
README
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 recall —
recall(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 memory —
remember(text, category)with 5 categories:user,feedback,project,reference,general. - Session journals —
journal(text)for end-of-session notes written to~/.sae4u-memory/journals/YYYY-MM-DD.mdfor human reading. - Customizable persona —
persona.mdshapes 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 forMEMORY.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.jsonunderhooks.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.
docs/architecture.md— 5 concepts, file layout, the 4 types, what NOT to savedocs/tick-protocol.md— how the 10-min hook works, what gets written wheredocs/persona-customization.md— what's editable, what's loaded at session startdocs/episodic-bridge.md— optional pattern for users with a remote dev boxprompts/session-open.md— paste this at session startprompts/session-close.md— paste this at session endcommands/memory-distill.md— weekly cleanup ritualrules/— 10 universal feedback ruleshooks/memory-tick.sh— the UserPromptSubmit hook itselftemplates/— MEMORY.md, feedback rule, project fact, tick log
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 thatrecall()should search. Defaults to all Claude Code auto-memory dirs (globbed from~/.claude/projects/*/memory/) plusSAE4U_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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.