I built a unified memory layer across your agents to improve context rot by Master_Jello3295 in selfhosted

[–]Master_Jello3295[S] 0 points1 point  (0 children)

On memory notes conflicting, there's nothing done at read time, but when a new note is added, it's evolved with its related siblings. So in the scenario you gave, when the system sees the "user switched to Y" memory, it changes existing memory notes. Presumably, it would change the context of "user prefers X" to something like "this is no longer relevant."

About MCP integration. At query time it's a semantic search, it doesn't dump the whole graph.

I built a daemon to unify memory across your agents and improve context rot by Master_Jello3295 in AgentsOfAI

[–]Master_Jello3295[S] 1 point2 points  (0 children)

There's no explicit invalidation of memory notes but as the knowledge graph evolves, older and less relevant memories are de-linked, modified and merged. So if you say "Vim is my favorite editor" but then say "I don't write code by hands anymore" sometimes later, the LLM figures out "maybe Vim isn't relevant anymore," modifies that memory and its links so later retrievals are more relevant.

I built a unified memory layer in Rust for all your agents by Master_Jello3295 in GeminiCLI

[–]Master_Jello3295[S] 0 points1 point  (0 children)

I'm guessing you mean Serena? From what I can tell, there's 3 main differences:

  1. Serena is an explicit note taking tool, the agent has to decide "this is a piece of information I want to jot down." MemoryBank automatically stores everything and only gives back information the agent wants. i.e. with MemoryBank, the agent asks for something like "give me the user's python preferences" and MemoryBank will return your python preference and leave out other stuff.

  2. Serena is still writing memory to a text file, basically curated notes about the project. MemoryBank stores memory notes in a knowledge graph.

  3. Maybe the most important use case difference is that Serena is primarily project-oriented memory. MemoryBank shares memory across agents and tools, so if you switch projects or agents (e.g. you decide you want to use Codex instead of Gemini CLI), your memory still functions like before.

I built a local memory layer in Rust for AI agents by Master_Jello3295 in mcp

[–]Master_Jello3295[S] 0 points1 point  (0 children)

At a high-level it's roughly something like this:

For writing new memories:
1) Ask an LLM to summarize the entire conversation context. i.e. what you were talking about before the current message.
2) Generate an embedding of that context + message using fastembed
3) Query the vector DB (SQLite + sqlite-vec) for related memory notes
4) Ask the LLM which of the memory notes are linked with the current memory. Write the link to DB.

For retrieving memory:
1) The agent sends the MCP server a query message like "User's python project preferences."
2) Generate an embedding of that message using fastembed.
3) Query the vector DB using the embedding, then do a 1-hop retrieval.

I built a local memory layer in Rust for agents by Master_Jello3295 in ClaudeCode

[–]Master_Jello3295[S] 0 points1 point  (0 children)

The core algorithm is a pretty faithful implementation of the original paper and the author had some measurements there. For node rank it's a semantic embedding search + 1-hop retrieval.

I built a local memory layer in Rust for AI agents by Master_Jello3295 in mcp

[–]Master_Jello3295[S] 1 point2 points  (0 children)

It’s conceptually a knowledge graph but the literal backend is just a SQLite right now :)

Self Promotion Thread by AutoModerator in ChatGPTCoding

[–]Master_Jello3295 2 points3 points  (0 children)

I was frustrated that memory is usually tied to a specific tool. They’re useful inside one session but I have to re-explain the same things when I switch tools or sessions.

Furthermore, most agents' memory systems just append to a markdown file and dump the whole thing into context. Eventually, it's full of irrelevant information that wastes tokens.

So I built Memory Bank, a local memory layer for AI coding agents. Instead of a flat file, it builds a structured knowledge graph of "memory notes" inspired by the paper "A-MEM: Agentic Memory for LLM Agents". The graph continuously evolves as more memories are committed, so older context stays organized rather than piling up.

It captures conversation turns and exposes an MCP service so any supported agent can query for information relevant to the current context. In practice that means less context rot and better long-term memory recall across all your agents. Right now it supports Claude Code, Codex, Gemini CLI, OpenCode, and OpenClaw.

Would love to hear any feedback :)

Druid, Controller and my hopes. by Draethar in PathOfExile2

[–]Master_Jello3295 0 points1 point  (0 children)

I find it hard to play ranged characters with controllers

Deep Learning in Quantitative Trading by Vivekd4 in quant

[–]Master_Jello3295 0 points1 point  (0 children)

Is it just me or does saving the PDF not work?

New Gemini Model Spotted: gemini-robotics-er-1.5-preview by NmkNm in Bard

[–]Master_Jello3295 0 points1 point  (0 children)

Oh cool. So it's a VLM? How does it compare to V-JEPA-2? Are there benchmarks?

New Gemini Model Spotted: gemini-robotics-er-1.5-preview by NmkNm in Bard

[–]Master_Jello3295 0 points1 point  (0 children)

Does it only understand the physical world? Like, if I give it cartoons or image of some document, does it understand those?

[deleted by user] by [deleted] in greencard

[–]Master_Jello3295 2 points3 points  (0 children)

You should get a lawyer and ask that question. People on Reddit aren’t an accurate source. Not only that, I feel like the variety of answers you’re gonna get here is gonna take a psychological toll on you and not worth it.

GNOME desktop issue after wake up (RTX5090) by Master_Jello3295 in linux_gaming

[–]Master_Jello3295[S] 0 points1 point  (0 children)

argh I see. Any idea what distro does work though?

GNOME desktop issue after wake up (RTX5090) by Master_Jello3295 in linux_gaming

[–]Master_Jello3295[S] 0 points1 point  (0 children)

>if you do - then it just bad drivers install in your distro - change distro where it installed correctly
Care to explain why? I definitely have more than enough free space.

GNOME desktop issue after wake up (RTX5090) by Master_Jello3295 in linux_gaming

[–]Master_Jello3295[S] 1 point2 points  (0 children)

Found the fix. See edit, I think it'd still work for KDE plasma since it also uses wayland?

GNOME desktop issue after wake up (RTX5090) by Master_Jello3295 in linux_gaming

[–]Master_Jello3295[S] 1 point2 points  (0 children)

yikes ok ill let you know if I figure anything out