Kage was always a document format memory with it's 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(Hook), also available and works with all the over coding agents.