https://github.com/TonyStef/Grov
Hi HN, I'm Tony.I built Grov (https://grov.dev/) because I hit a wall with current AI coding assistants: they are "single-player." The moment I kill a terminal pane or close a chat session, the high-level reasoning and architectural decisions generated during that session are lost. If a teammate touches that same code an hour later, their agent has to re-derive everything from scratch or read...
If this is a deal-breaker for you, in the near future I'll let teams use our API key, so you can just install it and run it normally without having to set anything up other than connect to your team. If you have any other questions you can find my email in the repo.
Hope this helps.
Example: My cofounder debugged the payment flow last week. When I touch payment code today, his reasoning is automatically injected into my session.
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 :))
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.
https://github.com/TonyStef/Grov
I noticed that if I take >5 minutes to read and/or understand claude's response, Anthropic's prompt cache expires. The next message forces a full context rebuild, which costs ~1.25x (write) vs ~0.1x (read) and hits rate limits faster.So I updated Grov, my open source tool to include a "heartbeat" mode, (--extended-cache) that sends a minimal token (just a .) every 4 minutes during idle...
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!