claude-memory-kit
Maintains conversation context across sessions without external databases, reducing setup overhead while enabling audit trails for compliance-sensitive work.
Your Claude Code agent remembers across sessions. Multi-project, sandbox experiments audit-driven promotion. Zero deps. v4.1,
- Ask Claude to recall previous audit findings when reviewing code changes across projects.
- Generate compliance reports that reference historical security decisions made in prior sessions.
- Automate promotion workflows by tracking which experiments passed sandbox security checks.
Maintains conversation context across sessions without external databases, reducing setup overhead while enabling audit trails for compliance-sensitive work. Simplifies multi-project workflows where state persistence matters.
Teams running Claude Code agents on isolated experiments requiring session continuity and audit compliance without infrastructure dependencies.
https://github.com/awrshift/claude-memory-kit
By awrshift
How to Get It
claude plugins install awrshift/claude-memory-kit
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Recall previous audit findings when reviewing code changes across projects
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 27 GitHub stars; 1 contributors; last commit 8d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 27 GitHub stars; 1 contributors; last commit 8d ago; license MIT.