Show HN: Persistent memory for Claude Code sessions

(github.com)

10 points | by tonyystef 6 days ago ago

4 comments

  • tonyystef 6 days ago

    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!

  • jatins 40 minutes ago

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

  • henryquillin12 6 days ago

    How do you ensure each memory is still relevant?

    • simgt an hour 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...