Launching today
Greplica
Self updating wiki for coding agents
128 followers
Self updating wiki for coding agents
128 followers
Greplica gives your engineering team and every coding agent a shared memory of the codebase. It continuously extracts decisions, constraints, gotchas, failed approaches, and file-level context from coding sessions, then retrieves only what matters for the task at hand. Unlike static docs or siloed agent memory, Greplica stays grounded in the repo, keeps knowledge fresh, and works across developers, agents, clones, and forks. It is open source, runs locally, and offers a managed shared mode.
Congratulations on the launch 🎉🔥
Does this work only with Claude Code, or can a team share the same memory across Claude Code, Cursor, Codex, and Copilot?
@yashkhem Its built exactly for this use case. Completely agent agnostic
Anchoring facts to committed code handles the "what does this do" half. The half I'd worry about is "we tried X and it didn't work", because that isn't anchored in anything and it's the note that costs the most when it's wrong. One bad conclusion from one bad session becomes ground truth for every agent run afterwards, and it reads exactly as confident as a true one. What retires a fact, other than the code it points at moving?
The "what does this do" vs "we tried X and it didn't work" distinction is the sharper problem here, agreed. I hit a smaller version of this manually, a running status doc plus session handoff notes so context survives between sessions, but that only catches drift I remember to write down myself. Your harder case is the one with no code artifact to signal staleness at all. Does anything actually retire one of those "we tried X" facts, or does it just sit there until a human notices it's wrong?
Can this also be used by product managers for data analytics? Will it be more efficient?
By giving them documentation of existing tables?
@kritin_garg Yes, that will work well too
ShotoAI
something i always wanted my coding agents to do
@whatsuppiyush Try it out!!
Great stuff, this is a much more realistic way to make context available to new developers and coding agents.
@nikunj_kothari Yes, this will lead to faster onboarding
Very interesting. Definitely needed for teams shipping real products at inference speed.
@umang_malik1 yes, just like us