Why even with the AGI claims the frontier labs have made, the way we interact with social network and the way we use your devices still the same.why in this world do we still have to type a text to a friend or search for the meme/emoji, why is there no change!!!why do I to still have to click through my desktop to get things done!!!Ideally, I would just want to speak!!! and expect my things to...
'kage propose --from-diff' is a supplementary tool that you can use to create a feature summary packet.
'kage pr check' runs validation and graph-freshness, and blocks on hard-stale memory your diff invalidated. You can run 'kage pr check' in your CI as well, that's what Kage is doing it in it's own repo.
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.
npx -y @kage-core/kage-graph-mcp install
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 viewerrun inside each repo you want memory in:
npx -y @kage-core/kage-graph-mcp install
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 viewerKage 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....
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...
Have you thought on making it collaborative memory across your teammates working on the repo? how does your framework handle stale memory, when someone changes the code that breaks the memory store?
you have worked on some feature in your codebase, you discussed something with your agent, your agent found some gotcha in your code, understood what all your code has and how to run the new feature. Done.
now what?? you teammate comes in starting from the bottom?! why??
this is the reason I've created Kage, it saves all the important things that you are doing with your agents. Whenever you or your teammates are using your agent again, you feel like you talking to an agent who knows it all, like an evolving teammate.
The interesting question is what Cursor adds on top — their UX and context management decisions are where differentiation actually lives.