superbrain
Preserves institutional knowledge from Claude Code sessions automatically, eliminating manual documentation overhead and enabling teams to retain context acr…
Session memory for Claude Code. Auto-captures every session into a plain Obsidian markdown vault. Zero config. MIT. macOS + Linux.
- Ask Claude to retain project context across multiple coding sessions without manual note-taking.
- Generate an automatic searchable archive of all your Claude Code conversations and decisions.
- Find past debugging solutions and code patterns you discussed with Claude in previous sessions.
Preserves institutional knowledge from Claude Code sessions automatically, eliminating manual documentation overhead and enabling teams to retain context across projects without custom infrastructure setup.
Engineering teams using Claude Code who need searchable session history and cross-project context retention without managing external databases.
https://github.com/m3talux/superbrain
By m3talux
How to Get It
claude plugins install m3talux/superbrain
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:
Retain project context across multiple coding sessions without manual note-taking
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): 32 GitHub stars; 1 contributors; last commit 4d 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): 32 GitHub stars; 1 contributors; last commit 4d ago; license MIT.