Re:Show HN: Persistent memory for Claude Code sessions
by tom1337 on Monday December 08, 2025 @06:57PM
(#46199437)
Why don’t you just resume the previous session with Claude so it keeps the context?
Re:Show HN: Persistent memory for Claude Code sessions
by tonyystef on Monday December 08, 2025 @07:14PM
(#46199600)
Resume keeps one session alive. Grov gives you knowledge from all past sessions (yours + your team's), filtered to what's relevant right now. It's really built for teams using coding agents to build software together.
Example: My cofounder debugged the payment flow last week. When I touch payment code today, his reasoning is automatically injected into my session.
So I built grov. It runs a local proxy that intercepts Claude Code's API calls, captures reasoning from each session (via LLM extraction), stores it in SQLite, and auto-injects relevant context into future sessions.
In testing: baseline task took 10-11 min with 3+ explore agents launched. With context injection: 1-2 min, zero explore agents. Claude just reads the files directly because it already knows the codebase patterns.
How it works:
-Run grov init
- Run grov proxy (keep it running)
- Use Claude Code normally
- Grov captures what Claude learns, injects it next session
It's local-only (SQLite), nothing leaves your machine. Currently ~250 npm downloads with no promotion, which pushed me to share it here.
Still early (v0.2.2). Would love feedback from Claude Code users. Please report bugs!