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.
Hey Product Hunt!
Kushal here, co-founder of Greplica.
Today we are launching shared, self-updating wikis for developer teams.
Internal documentation is always boring, but with coding agents now writing a 100% of the code it is more important than ever. CLAUDE .md files can only store so much information - the real secrets of the codebase that your agent learns in its runs get lost in a new session. Any and all internal documentation goes stale - unless agents are managing it.
Greplica helps you move beyond the stale markdown file that no one in the team updates to a living, managed wiki that constantly saves the tribal knowledge of your team that you want your agents to know. All its facts are anchored in committed code and constantly updated to ensure nothing is incorrect. A multi-tier retrieval algorithm finds the most relevant context for each prompt and gives that as extra guidance to the LLM.
Open source as always - please try it our Github repo. We are in the comments all day. If you want to chat more, please feel free to book time here.
Super exciting - congrats on the launch! A self-updating wiki for coding agents is a genuinely clever idea.
Congrats on the launch, Kushal. We're a small team and do a bunch of stuff with coding agents daily and the thing you're describing is a real problem. Anchoring facts to committed code so they expire on their own is the part I like, because it's the only version of this that doesn't turn into another doc nobody updates. Adding Greplica to my list!
Can I see exactly what it has learned and remembers, and edit or expand it if necessary? For example, in the form of concise documentation or something similar.
Anchoring facts to committed code is the part that convinced me — it gives stale knowledge a natural expiry date, which hand-written docs never have. I maintain around ten repos on my own and my claude.md files rot faster than the code does. What I couldn't tell from the page: how does Greplica sit next to an existing claude.md or agents.md — does it replace them, feed them, or end up competing for the same context window?
@kushal_patil Congrats on the launch! with multiple clones and forks feeding the same wiki, how do you handle two forks that genuinely diverge in approach?
Kushal, the quiet way teams forget why their own code works the way it does has bitten me more times than I can count, and this speaks straight to that.
Really nice concept for Greplica: Self updating wiki for coding agents. Rooting for you today—congrats! 🚀
Very interesting. Definitely needed for teams shipping real products at inference speed.
Congratulations! Turning all those little codebase lessons into something reusable is a great idea. That tribal knowledge usually gets lost way too easily.
Great stuff, this is a much more realistic way to make context available to new developers and coding agents.
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?
Can this also be used by product managers for data analytics? Will it be more efficient?
Code graphs usually capture what calls what. Pulling decisions, failed approaches, constraints, and workflows from actual coding sessions feels much more useful. Kudos to the team!
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?
About Greplica on Product Hunt
“Self updating wiki for coding agents”
Greplica launched on Product Hunt on July 30th, 2026 and earned 172 upvotes and 29 comments, placing #7 on the daily leaderboard. 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.
Greplica was featured in Open Source (68.7k followers), Developer Tools (516.7k followers), Artificial Intelligence (474.9k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 228.3k products, making this a competitive space to launch in.
Who hunted Greplica?
Greplica was hunted by Kushal Patil. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Greplica stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Kushal Patil