FRESH

Hacker News

Show HN: Persistent memory for Claude Code sessions

21 points by tonyystef

by tonyystef

1 subcomments

I kept watching Claude Code spend 10 minutes re-exploring files it already analyzed yesterday. Same patterns, same architecture, every session starting from zero.
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!

by jatins

1 subcomments

What value does it provide over, say, just asking Claude to keep state in a markdown file that it can access across sessions?

by uptownhr

0 subcomment

I also built something similar. Utilizes ZEP for building a temporal graph that keeps track of facts.
https://github.com/Zabaca/temporal-bridge

by henryquillin12

2 subcomments

How do you ensure each memory is still relevant?

by smcleod

1 subcomments

I see it requires an ANTHROPIC_API_KEY, does that mean it does not work with Claude Max plans?