Viewing profile — kage18

Yusss, you install Kage and then you work with your agent as you regularly do, it automatically captures memories from your live session like decisions, gotchas, runbook, bug fixes…

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…

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, w…

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, w…

Kage 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 r…

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 …

Love to see people creating such projects, i'm truly passionate about Coding Agent Memory myself. Have you thought on making it collaborative memory across your teammates working o…

Sharing and collaborating memory with your agents and teammates it's a big hassle, you have worked on some feature in your codebase, you discussed something with your agent, your a…

[dead]

[dead]

[dead]

[flagged]

great initiative, i have built something similar, would love to chat with you

[flagged]

[flagged]

[flagged]

impressive

great stuff

how will you tackle prompt ingestion?

In only a time someone will do it in shell ---- oh wow you did it!!!

Makes sense architecturally. The Claude Code SDK is well-designed for agentic use — sub-agents, hooks, session management all work cleanly. If you're building an IDE on top of it y…