Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kage18
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
1.
▲
by
kage18
3mo ago
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 etc... it automatically links them to the right code blocks
2.
▲
by
kage18
3mo 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, clas
3.
▲
by
kage18
3mo 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-wir
4.
▲
by
kage18
3mo 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-wir
5.
▲
Show HN: Google's OKF now has a framework to maintain and verify agent memory
(kage-core.com)
3 points
by
kage18
3mo ago
|
3 comments
6.
▲
Show HN: Kage, verification and freshness for Google's OKF agent memory
(kage-core.com)
4 points
by
kage18
3mo ago
|
3 comments
7.
▲
by
kage18
3mo ago
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 on the repo? how does your framework handle stale memory
8.
▲
by
kage18
3mo ago
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 agent found some gotcha in your code, understood what al
9.
▲
Show HN: shared verified memory for AI agents: one learns, all recall
(kage-core.com)
2 points
by
kage18
3mo ago
|
1 comments
10.
▲
by
kage18
3mo ago
great initiative, i have built something similar, would love to chat with you
11.
▲
by
kage18
4mo ago
impressive
12.
▲
by
kage18
4mo ago
great stuff
13.
▲
by
kage18
5mo ago
how will you tackle prompt ingestion?
14.
▲
by
kage18
5mo ago
In only a time someone will do it in shell ---- oh wow you did it!!!
15.
▲
by
kage18
5mo ago
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 you'd want that foundation rather than rolling y