alive
Maintains continuity across fragmented Claude sessions by persisting project context, decisions, and code state—reducing ramp-up time and preventing loss of …
A personal context manager for Claude Code that persists your working context across sessions as plain files on your machine. Agents read them at session start and save what matters at session end, so decisions, research, people, and domain knowledge get structure instead of dying with the session. Context is organized into 'walnuts' — ventures, experiments, people, or life areas — each with files for identity, current state, and standing knowledge, so you don't re-explain yourself each time.
- Ask Claude to summarize your recent project decisions and architectural choices for onboarding new team members.
- Generate a personal knowledge base of your coding patterns and preferences to apply across multiple projects consistently.
- Automate context switching by retrieving your previous work history and technical decisions when resuming past projects.
Maintains continuity across fragmented Claude sessions by persisting project context, decisions, and code state—reducing ramp-up time and preventing loss of architectural decisions or progress.
Solo developers and small teams using Claude for iterative code projects requiring session-to-session state preservation.
https://github.com/alivecontext/alive
By alivecontext
How to Get It
claude plugin install alive@alivecontext
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
After installing, paste this into Claude:
Summarize my recent project decisions and architectural choices for onboarding new team members
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.
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 125 GitHub stars; 8 contributors; last commit 11d 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.
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
catalog_hygiene stale-eval refresh: Scored from trust signals (evidence-eval-v1): 125 GitHub stars; 8 contributors; last commit 11d ago; license MIT.