I’m working on Greplica ( https://github.com/autoloops/greplica ) — a lightweight graph-memory layer for coding agents. The idea is simple: capture claims, components, flows, and code anchors from engineering sessions, and let the agent query that graph across sessions instead of starting blind. In our internal usage it reduces agent’s exploration by 2.5x (fewer files read) and reduces token cost by up to 40% on bug fixes/modifications. Would love to know how you folks are solving the problem of coding agents having amnesia. We are currently in the tokenmaxxing era but costs are ballooning already, we saw Uber. On the other hand, soon there will be many types of coding agents including open weight ones that can code alongside devs. Shouldn’t all engineering teams start maintaining a context layer of their repo so that agents can work more efficiently on it? Would love to get any feedback on this approach and would mean a lot if someone is willing to try it! submitted by /u/Ok-Insect-6726
Originally posted by u/Ok-Insect-6726 on r/ClaudeCode
You must log in or # to comment.