G
Show HN
Show HN: Persistent memory for Claude Code sessions
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!

Why don’t you just resume the previous session with Claude so it keeps the context?
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.

Alright sounds nice - I guess for teams it makes sense then but as a soll developer, claude resume currently works well:)
I also built something similar. Utilizes ZEP for building a temporal graph that keeps track of facts.

https://github.com/Zabaca/temporal-bridge

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

1. Automatic capture with structured extraction: Grov uses Haiku to extract reasoning_trace (conclusions + insights) and decisions (choice + why) from each session. You don't write anything, it captures automatically.

2. Intelligent injection by file match: When you edit src/auth/login.ts, Grov queries past sessions that touched auth files and injects only that context. A markdown file would be read entirely every time, wasting tokens. (next version will also include semantic search)

3.Team sync: Automatically syncs to a team dashboard. When dev A explains the auth system, dev B's Claude knows it automatically while doing related work.

Technically this was the core idea of Grov, for my coding agent to know the reasoning behind why my cofounder's coding agent chose to implement xyz in such way.

[dead]
How do you ensure each memory is still relevant?
  • simgt
  • ·
  • 16 hours ago
  • ·
  • [ - ]
That thing is 15kLOC of Typescript vibe-coded over the span of two days. At this point you're better off asking an AI if you have a question about what the code does...
The repo history shows about two weeks of development. If you can't be bothered to do basic due diligence before critiquing, your opinion is just as 'vibe-based' as you claim the code is.
  • simgt
  • ·
  • 14 hours ago
  • ·
  • [ - ]
Fair enough, my comment was unnecessarily harsh.
  • ·
  • 14 hours ago
  • ·
  • [ - ]
Appreciate it.
Currently we match by:

File paths: If you're touching src/auth/, we inject memories that touched auth files. Recency: Most recent memories first, limited to top 10

Semantic search is on the roadmap but not implemented yet. Right now it's straightforward file matching + recency.

(Appreciate the question, really have to start working on this; not the first time someone asked :))