​ 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   submitted by   /u/Cold_Cauliflower_230 [link]   [comments]