Show HN: Google's OKF now has a framework to maintain and verify agent memory

3 pointsposted 5 hours ago
by kage18
(kage-core.com)

4 Comments

kage18

5 hours ago

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 for creating relevant memories and linking it to the code graph.

you can see the dashboard using the command:

    kage viewer

brijs

4 hours ago

what about having a distributed memory shared across team?

kage18

4 hours ago

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.

user

an hour ago

[deleted]