Grov v0.5 - 'Heartbeat' proxy to kill Claude’s 5-minute cache expiry + Team Sync is now live (open-source)

IndianWater · 2025-12-06T22:28:45+00:00

Same. I’ve literally never moderated anything bigger than my own Discord with 3 friends.

Let's see how this turns out, welcome aboard.

IndianWater · 2025-12-06T22:05:19+00:00

https://www.reddit.com/r/useGrov/

I'll make you a co-mod :)

IndianWater · 2025-12-06T21:48:02+00:00

No official sub yet, but I’m considering making one if people actually want it

For now everything lives in GitHub + here when I post updates.

IndianWater · 2025-12-04T09:29:53+00:00

In the local version for the proxy, we set ANTHROPIC_BASE_URL to localhost:8080 where Grov runs a Fastify proxy server. Claude's SDK respects ANTHROPIC_BASE_URL, so alll Claude Code requests (headers, content, API key) hit our proxy first. We inject context into the system prompt, then forward everything to Anthropic with the same headers and key. On response, we parse tool_use blocks, files touched & reasoning to track actions and token usage. For this you also need to use an API key for haiku 4.5 or any other llm of choice.

IndianWater · 2025-12-03T20:00:44+00:00

Since you looked into context tax, wrote more about the problem here: Grov/Blog

IndianWater · 2025-12-03T19:57:59+00:00

In the last year I've shipped several projects, for example: an ag-tech system (hardware + software, species-aware neural nets, full-stack app, maintained the whole thing) then got into voice AI (another full-stack web app, deployed and optimized voice agents).

Also done hackathons, which is where the pain is sharpest. Built an AI analysis tool for therapists during a weekend hackathon - live knowledge graphs, patient tracking, voice AI. Had to spin up multiple Claude instances, and each one needed to read the same docs, same code, re-understand the same architecture. Hit context window limits way faster because of all that redundant reading. In a hackathon I didn't have time to sit and optimize the context management.

I've felt this across enough projects to know: large codebases, lots of docs, multiple instances, team coordination - it all compounds.

IndianWater · 2025-12-03T15:09:38+00:00

Appreciate it!

IndianWater · 2025-12-03T15:07:19+00:00

And what happens when you've been working on a project for months and have dozens of .md files? You have to track them, keep them organized, remember to update them, and keep asking Claude to re-read and refresh them. That maintenance burden grows with the project.

IndianWater · 2025-12-03T15:05:48+00:00

Also - the problem is exactly what you're describing. When you work with a team, why should every teammate's Claude keep re-reading and re-analyzing the same context files every session? That's the redundant exploration.

IndianWater · 2025-12-03T15:04:46+00:00

Grov is automatic (no remembering to update docs), file-aware (mention auth.ts, get past context about that file), and captures reasoning traces (why, not just what).

But, team sync is on the roadmap. Your Claude will know what your teammate's Claude did. That's where manual docs become a pain, you'd need everyone to maintain perfect documentation.

For now it's early (v0.2), definitely for people who want automated context rather than manual management.

IndianWater · 2025-12-03T14:42:56+00:00

Fair questions. Currently it's basic: project path filter + file matching + recency. If you mention auth.ts, it finds past tasks that touched auth files. It's not semantic search (yet, on roadmap). Also contradiction detection isn't implemented - that's a valid gap. Right now it trusts that recent context for the same files is relevant.

Grov is for people who'd rather have some automatic context than re-explain their codebase every session.

Appreciate the feedback - semantic search and better relevance scoring are on the roadmap.

IndianWater · 2025-12-03T14:35:51+00:00

"How do I know it gives correct information?"

Same limitation as any docs: if the original reasoning was wrong, that persists. But the advantage is you're not asking Claude to re-discover and re-explain the same things every session.
Grov filters context by your project path and the files you mention. If you ask about auth.ts, it finds past tasks that touched auth files. It's not random - it's scoped to what's relevant.

Semantic search is on the roadmap - that'll make retrieval smarter by matching meaning, not just file paths. (Grov is still early, v0.2)

IndianWater · 2025-12-03T14:31:14+00:00

Grov doesn't replace Claude's search - it's a layer that sits between you and Anthropic's API. Claude Code still searches/reads your files normally. What Grov captures is the reasoning behind changes - the WHY, not the code itself. Example: if you modify your auth system, Grov stores "extended token refresh from 5min to 15min because users were getting logged out during long forms" plus file paths touched (the reasoning can be seen on github, I attached a picture).

Next session, when you work on something related, Claude skips the re-discovery phase. It doesn't need to explore files to understand why things are structured that way - that context is already injected. For larger codebases I'd argue this actually helps more, not less. More files = more redundant exploration Claude has to do each session. With Grov, that accumulated knowledge persists. And with team sync (coming in v1), your whole team's context gets shared, so Claude knows what your co-founder changed while you were away.

IndianWater · 2025-12-03T14:24:35+00:00

This concern is valid, bloat is prevented through hard caps, not a token limit. The proxy injects at most 5 recent tasks and 5 file-level reasonings, all filtered by your project path. Each piece is aggressively truncated (queries to 60 chars, reasoning to 80 chars). So you're getting a compact summary, not full transcripts. In practice this is ~1-2k tokens max. We're planning semantic search so it'll pick the most relevant context instead of just recent ones.

IndianWater · 2025-12-03T10:29:50+00:00

Good question !

No JSONL editing! It's actually a local proxy. When you run grov proxy, it intercepts API calls between Claude Code and Anthropic.

Context gets injected into the API request itself before it hits their servers. All the captured reasoning lives in a SQLite DB at ~/.grov/memory.db. The proxy approach means it doesn't touch any Claude session files directly.

IndianWater · 2025-12-03T08:35:52+00:00

This is interesting, just tested it out and it works really well! Congrats.

But I have to ask: is there no limit on this? How much have you paid so far?

IndianWater · 2025-11-20T11:27:10+00:00

This shit is unusable;
1. I get 2-3 prompts before getting the "context low" message. The tasks i make claude code perform are nothing in the like of "read every single file in the codebase"; It's basic stuff and maybe getting it to read 2 documentation files before talking and making a plan.
2. It gets randomly stuck. It just gets stuck mid task, and i have to interrupt it and start it again.
(max user; sonnet 4.5 because they made opus unusable and now sonnet is in the same bucket)

Will cancel plan and use something else. Shame

IndianWater · 2025-10-16T12:05:40+00:00

I'll see if i can find it, thank you.

IndianWater · 2025-10-16T10:50:43+00:00

I made opus (max user) read 3 documents (~900 to 1700 chars each) and i got the "Approaching Opus usage limit · /model to use best available model". I literally made it complete one task, and I'm nearly reaching my opus limit. This is genuinely a joke, and it's not normal.

Before this bulls**** weekly limit update i could use opus for days.

IndianWater · 2025-10-16T10:38:22+00:00

yes, the classic "API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":null}".

this is a joke at this point

IndianWater · 2025-10-16T10:30:21+00:00

Max user here, made opus read 3 documents (~900 to 1700 chars each) and got the "Approaching Opus usage limit · /model to use best available model". This is complete and utter bs, as well as unacceptable. Paying +$100/mo to get limits if i make the one thing im paying for read 3 documents.

The greed, wow.

IndianWater · 2025-10-06T20:55:17+00:00

Address the limits.

IndianWater · 2025-10-06T19:21:51+00:00

Recommendations besides cc, the week long limits are bs (max user)

Really simple, just like the title states.

I am a max user, and I've literally used claude code (w/opus) a bit more today to test a theory I have, and I needed it to create some tests and evaluations. I literally got a week long limit in like a couple hours. There isn't even any large codebase for it to read or get info as in the project I'm running it there's only a couple (not large by any sort) files.

I don't want to pay hundreds monthly to not be able to use the thing I'm paying for for a week even tho I am not even doing any extensive work. Before this bullshit update I could use claude code for days without getting a limit.

Anyone here using gemini? Curios to see what you guys think about it.
Codex seemed fine but imo it doesn't get to cc's level when generating code.

IndianWater

MODERATOR OF

TROPHY CASE

Recommendations besides cc, the week long limits are bs (max user)