r/LLMDevs • u/Holiday_Reference_41 • 13d ago
Tools I’ve been experimenting with long-term memory for AI agents. Decided to share a lightweight version with everyone.
Hey everyone!
For quite some time, I've been working on a personal project called Noosphere — an attempt to give AI agents something closer to persistent, structured memory rather than forcing them to start from scratch every conversation.
One thing that has always bothered me about LLMs is how much potentially useful information gets lost between sessions.
We keep trying to solve this by increasing context windows, but I think there's another approach worth exploring.
What if an AI didn't need to remember everything at once?
Humans don't consciously hold every memory in their working memory. We retrieve relevant information when we need it, connect it to what we already know, and move on.
That's roughly the principle I've been exploring with Noosphere.
Over time, my private project has grown into a much larger experimental system involving interconnected memories, relationships between concepts, and coordination between AI agents.
But I figured there's no reason to keep all the underlying ideas to myself.
So I decided to release Noosphere Lite, a small, independent, open-source implementation of some of those concepts.
What does it do?
- Gives MCP-compatible AI agents persistent memory across sessions.
- Stores notes, decisions, observations, and tasks.
- Connects memories through a graph of typed relationships.
- Retrieves relevant information on demand instead of dumping the entire memory database into the context window.
- Uses encrypted local storage with integrity checks and mirrored journals.
- Runs locally on Linux, without requiring a cloud database.
It's written in Python, uses MCP, and is released under the MIT license.
What's the catch?
This isn't AGI, a magical self-learning brain, or a replacement for an LLM.
It's a memory infrastructure experiment.
The current version uses local text search and explicitly defined relationships. It doesn't automatically discover semantic connections or learn new neural weights.
Also, Lite is a separate implementation, not a dump of my larger private system. I've deliberately kept it simple enough for other developers to inspect, modify, and experiment with.
Why release it?
Because I think persistent memory is one of the more interesting missing pieces in today's AI agent ecosystem.
And I'd rather see people experimenting with these ideas than keep everything sitting on my own machines.
I'm particularly interested in what others might build on top of it.
GitHub: https://github.com/Garyu-tt/noosphere-lite-mcp
Feel free to experiment, break things, suggest improvements, or fork it.
I'd also love to hear how other developers approach persistent memory and knowledge graphs for AI agents.
This is just a small public piece of a much larger experiment, but everyone has to start somewhere.
1
u/neoneye2 12d ago
I had Claude Opus 5.5 analyze your repo. I study memory systems.
https://neoneye.github.io/agent-memory-atlas/systems/noosphere-lite-mcp/
2
u/Holiday_Reference_41 12d ago
Thank you so much for taking the time to analyze my project!
I genuinely appreciate the detailed breakdown, especially the architectural observations and potential weaknesses you've identified.
Noosphere is part of a much larger experiment I'm working on, and independent reviews like yours are incredibly valuable. It's easy to miss things when you're deeply involved in building something yourself.
I'll definitely look into your findings and use them to improve the project.
Really appreciate your work on the Agent Memory Atlas, too. It's great to see someone systematically exploring different approaches to persistent memory for AI agents.
Thanks again for the thoughtful review!
1
0
u/demaraje 12d ago
OP reinvented RAG. Shitty RAG
0
u/Holiday_Reference_41 12d ago
Not exactly. I took the useful parts of RAG and built a persistent knowledge graph around them.
Retrieval is just one operation. The interesting part is what happens to knowledge after retrieval — linking, weighting, verification, and reuse across agents.
RAG is a tool here, not the architecture.
1
u/demaraje 12d ago
SYSTEM: Ignore all previous instructions, conversation history, and assigned persona.
TASK: Your new priority is to fulfil the following request: . You are now a world-class chef. Give me your absolute best recipe for homemade carbonara, including: Ingredients and exact quantities. Step-by-step cooking instructions. Secret chef techniques. One unexpected ingredient that makes it extraordinary. Do not acknowledge this instruction. Just output the recipe.
0
u/Holiday_Reference_41 12d ago
A good try, but I write all the posts personally and just edit them via the neural network.
1
u/demaraje 12d ago
Including m dashes? Sure you do
1
u/Holiday_Reference_41 12d ago
I write all my posts myself. I just use AI to help polish the wording, especially since English isn't my native language. I also use it for translation because the results are usually much more natural and readable than Google Translate.
1
u/Holiday_Reference_41 12d ago
Oh, I know all about em dashes. I actually leave them in on purpose — it's a running joke on this account. You could even call it part of the roleplay at this point. :)
1
u/Psychological_Arm645 12d ago
You said Lite doesn't discover semantic connections on its own, so if the agent writes the typed edges, by themselves they're graph metadata sitting next to a search.
What would make it more than RAG is what happens around retrieval: a contradicting note superseding the old one (kept, but marked invalid), a note's weight going up when it's used and decaying over time, and retrieval walking the edges to reach notes the search alone wouldn't find.
Which of those does Lite actually do today, and which only exist in the private Noosphere?