Why don’t you just resume the previous session with Claude so it keeps the context?

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...

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 :))

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.

The API key powers Grov's features (Haiku for reasoning extraction + drift detection). It does work with claude max plans, for example I use it with my claude code instances, and I am a max user, but you just have to use an API key for the fundamental features of Grov.

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.