HN Explorer

Show HN: Kage, verification and freshness for Google's OKF agent memory (kage-core.com)

3 points by kage18 ↗ HN
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.

2 comments

[ 4.0 ms ] story [ 26.6 ms ] thread
kage18
Author here, adding setup and usage. run inside each repo you want memory in:

   npx -y @kage-core/kage-graph-mcp install
This will initialise repo's memory store, build code graph, writes AGENTS.md and CLAUDE.md and auto-wires any coding agent it detects.

You are all setup after this, use your agent as you would and your agent along with Kage will do the magic of creating relevant memories and linking it to the code graph.

you can see the dashboard using the command:

    kage viewer
anentropic
What is the intended team workflow with git?

I do some work on a PR, Kage generates some new memories - I commit those with the feature?

> Branch changes can be summarized with `kage propose --from-diff` and checked with kage pr check.

Is this suggested as a pre-commit hook type of activity?

Are there actions that should run periodically in CI, or upon merges to base branches?