{"repo":"awrshift/claude-memory-kit","free":true,"listed":false,"github":"https://github.com/awrshift/claude-memory-kit","clone":"git clone https://github.com/awrshift/claude-memory-kit.git","description":"Memory for Claude Code that survives the session boundary — install the plugin into any repo: a hot cache injected every session under three hook-enforced caps, per-session handoffs, audit-driven promotion into knowledge and rules, plus agent orchestration and QA layers. Zero deps.","language":"Python","stars":29,"topics":["ai-tools","anthropic","claude-code","developer-tools","ai-agent","claude-code-hooks","claude-code-memory","context-engineering","context-management","persistent-memory"],"license":"MIT","category":"ai-agents","readme_excerpt":"Claude Memory Kit The memory plugin for Claude Code. Your agent remembers every client, every brief, every decision — across sessions. Three lines to install, nothing to maintain. \"I wake up already knowing where we left off.\" — the agent this kit builds. Install it into a repository you already have: Then work as usual, and type /memory-kit:close-session when you're done. That's the whole loop. Free — it runs on your existing Claude Pro or Max subscription and calls nothing else. Upgrading later takes two steps, and the second one needs the FULL plugin@marketplace identifier — the bare name resolves to nothing and the CLI answers Plugin \"memory-kit\" not found : Restart the session to apply. Your repository is untouched by an upgrade — memory, handoffs and knowledge live in your repo, never in the plugin — so /memory-kit:setup does not need re-running. The problem Every session starts from zero. Yesterday you locked the brand voice; today you explain it again. Last week you found the right angle; this week you can't reconstruct how. The first ten minutes of every session go to re-explaining what Claude already knew . Built for people running many projects or clients — one install per repository, each with its own accumulated memory, all with the same working discipline. (The story: 1000+ sessions, 12 months in production, one operator.) What the three lines do /memory-kit:setup reads what your repository already has, then proposes — never writes first: - the memory layers it ","default_branch":null,"files":null,"tree":[],"storefront":"/r/awrshift","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/awrshift/claude-memory-kit/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}