Show HN: Google's OKF now has a framework to maintain and verify agent memory
kage-core.comKage was always a document format memory with its own memory standards... and was betting on file based memory + git native. It's good to see that Google also thinks the same and released OKF(Open Knowledge Format) and Kage has adopted OKF with open arms.
Though Google has released the Memory standard and how to structure the memory, it doesn't do verification, when and how memories are created. That's where Kage comes in, Kage as a framework works with your agent, understand what to save, when to save, how to save, it also help the agent to recall relevant memory/maintain it's freshness.
Kage is focused on maintaining your repo's memory for you and give you best experience when coordinating and working with teammates on the same repo. Just install Kage and let you agents do the memory maintenance job itself using Kage.
Best support with Claude Code(Hooks), also available and works with all the over coding agents. Author here, adding setup and usage. run inside each repo you want memory in: You are all setup after this, use your agent as you would and your agent along with Kage will do the magic for creating relevant memories and linking it to the code graph. you can see the dashboard using the command: what about having a distributed memory shared across team? The memory is a collaborative and shared across team as it sits in git alongside the code. Kage also helps manage these memory by reindexing/linking memories based on edits and new memories. It tells you frequency usage of memory, classifies them into HOT, COLD, STALE, based on usage and usefulness.
This will initialise repo's memory store, build code graph, writes AGENTS.md and CLAUDE.md and auto-wires any coding agent it detects. npx -y @kage-core/kage-graph-mcp install
kage viewer