claude-memory-kit

Featured

Persistent memory for Claude Code agents with an agent-audit-ritual architecture. User only talks; the agent captures, audits, proposes promotions, and writes. Memory lives in layers — a hot cache (MEMORY.md) held under three size caps, per-session handoffs (context/handoffs/), topical knowledge articles (knowledge/concepts/), and canonical rules (.claude/rules/) — plus multi-project isolation via projects/<name>/ and an experiments/ sandbox. /close-session runs the end-of-session audit ritual. Zero external dependencies.

AI & Automation 34 stars 7 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Claude Memory Kit v5 Persistent memory for Claude Code agents. Layered memory, agent-driven promotion, zero manual file editing. The v5 **lean core**: two operators, per-session handoffs, memory that fails loudly instead of rotting quietly. ## Two core invariants 1. **User only talks. Agent captures, proposes, writes.** Every architectural decision passes this test. 2. **Every memory entry carries a `[YYYY-MM-DD]` date tag.** This is what lets `/close-session` detect cross-session repetition and propose promotions. ## What's new in v5 - **Session close is `/close-session`, not `/close-day`.** The ritual: capture dated patterns → audit for 3+-date repetition → promote on your "yes" → replace the MEMORY.md header (current state, never a chronicle) → write a per-session handoff. - **Per-session handoffs replace the rolling next-session-prompt.** One immutable note per closed session in `context/handoffs/<topic>-YYYY-MM-DD.md`; the SessionStart hook injects the newest one. No rolling file to freeze while looking authoritative. - **Three independent MEMORY.md caps, hook-enforced: 180 lines / 32 KB / 3000 chars per line.** Line count alone lies — content densifies into ever-longer lines while `wc -l` stays flat. Any tripped cap opens the next session with an audit prompt. - **Stale-reference detector.** Every session start, file paths mentioned in memory are checked against disk; anything moved or missing is flagged. - **The daily journal (`daily/` + `/close-day`) moved to o...

Details

Author: awrshift
Repository: awrshift/claude-memory-kit
Created: 6 months ago
Last Updated: today
Language: Python
License: MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

claude-mem-persistent-memory

Persistent cross-session memory for coding agents: captures the session, compresses it and re-injects what is relevant later, with ~75% fewer tokens. Apache-2.0 upstream, permissive.

17 Updated 2 days ago

CarlosCaPe

AI & Automation Listed

claude-mem

Persistent filesystem memory across sessions — maintains memory/ with decisions.md, context.md, glossary.md and sessions/YYYY-MM-DD.md, loads and summarizes state at session start, appends decisions and open threads at session end, compacts monthly, and refuses secrets and transient noise. Use when the user says "remember this", "what did we decide about X", "pick up where we left off", or when starting or closing a session on a long-running project.

15 Updated 2 weeks ago

alebgl77

AI & Automation Listed

memoir

Memory lifecycle management for Claude Code agents. memoir handles what built-in memory doesn't: hot/cold layering, weight evolution, decay, archiving, merging, and autonomous self-maintenance across sessions. Use when the user wants to set up or maintain a memory system, asks about "memoir", mentions memory lifecycle/organization, says "/memoir", or when a session is ending and memory maintenance is due. Also use when the user gives behavioral feedback ("from now on, don't do X") or when important insights about the user's identity/values emerge that should outlast this session.

1 Updated 1 weeks ago

Sevan7-Kalo10