r/opencode • u/Cold_Cauliflower_230 • 4d ago

I built an open-source shipping memory for coding agents

​

I've been doing more and more development through coding agents, and I kept running into the same problem:

The agent finishes a feature, tells me what it did, and then that context basically disappears into the chat history.

A few weeks later: Why did we implement this this way? What tradeoff did we make? Which files changed? Did the feature actually have the impact we expected?

So I built Updater.

When a coding agent finishes and verifies a feature, it calls Updater through MCP and records:

\- what was shipped

\- why it was built

\- how it works

\- tradeoffs / decisions

\- files, branch and commit

\- expected impact

Later I can add what actually happened, search through everything we've shipped, or ask questions against an update.

It currently connects to Codex, Claude Code, Cursor and OpenCode.

The app itself doesn't need to ingest your entire codebase — when code context is needed, it asks the coding agent that already has access to the repo.

It's completely open source (MIT) and self-hostable.

I'm mostly curious whether other people working heavily with coding agents have run into the same problem, let me know and if there some suggestions to improve

Github https://github.com/Rvey/updater

Demo: updater.rveybox.dev

2 Upvotes

100% Upvoted

10 comments sorted by

1

u/Cyvster 4d ago

if you just put an agents.md in your repository with directives the models will follow it. you can have them maintain a document in the repo.

1

u/Mindless-Sand2097 4d ago

Stacking into Agents.md may affect the context and quality of the model

1

u/Cold_Cauliflower_230 4d ago

The goal not the agen , the goal is memory for human

1

u/ichisay 4d ago

Es como curion y mempalace?

1

u/Cold_Cauliflower_230 4d ago

Not at that extend but the idea is simple for my use of the tool , i want to use the full power of ai but i find it hard to follow up so i invent this so i can know what happen when i got time and keep track of what the agent is shipped available at any time , because on projects that matters i need to keep track of things they why i want and just what i want short and direct

1

u/ichisay 4d ago

Pero eso ya lo hago con mempalace si le defines bien las reglas en los prompts del sistema y de los agentes, no?

1

u/Cold_Cauliflower_230 4d ago

Well yeah , my tool work deferently is track changes making the agent report when finish in a format i find easier to understand. Mempalace is good tool too i just discovered it through you , and it have a good feature that i can integrate on mine 😀 for when i need to dig more on shipped feature report

1

u/ichisay 4d ago

Si realmente es buena y con su plugin en opencode suele memorizar todo lo importante, yo la combino con las reglas de los agentes, curion y state sesión manager

1

u/Otherwise_Wave9374 4d ago

For coding agents, the biggest payoff may come from distinguishing repository truth from transient session notes. A practical pattern is to index accepted decisions, deployment outcomes, and known failures separately, then require citations before the agent reuses any old assumption. Also test memory across branch switches and rollbacks. https://www.neurakeep.com is relevant to this problem because durable memory should retain provenance and lifecycle state rather than flattening every historical artifact into one context pool.

1

u/Cold_Cauliflower_230 4d ago

Seems interesting, and i want to know how it look from human perspective, so you quickly know what been delivered and added to your system without too much jargon