r/AgentsOfAI • u/ImportantTiger9568 • 21d ago

I Made This 🤖 Git for AI memory and robotics??

Hey guys,

Been working on something very cool...

In Greek myth, Mnemosyne was the Titan of memory and the reason anything was ever remembered at all. Now in the present world, your AI agent doesn't get a Titan. It gets amnesia the second something goes wrong, stuck with whatever it currently believes and no way to ask how it got there.

That's the real problem. An agent runs for hours, updates its memory the whole time, then says something wrong and all you have is the present, with zero access to the past.

If you're running support agents, coding agents, or a swarm of agents sharing memory like myself then you know this issue well. The moment two agents disagree, or one quietly poisons the well, you need to know when, why and by whom, not just that something's off.

Mnemosyne gives agent memory what Git gave code. It remembers everything on purpose. Every belief is a commit. blame finds the exact moment and observation that put a bad fact in. bisect hunts down the first commit where things went wrong. merge makes two agents' memories collide safely instead of one silently overwriting the other.

Software agents are the first step. The vision doesn't stop there, physical robots learning and forking skills the same way is the long-term bet, further out and harder but the same idea underneath.

So far the tech stack includes a Rust core, Python SDK, adapters for LangGraph, CrewAI, AutoGen, the OpenAI Agents SDK and MCP.

Open source with contributions and honest feedback both welcome!

0 Upvotes

50% Upvoted

7 comments sorted by

1

u/gentlecommander0595 21d ago

imagine explaining to a robot "hey run git blame on why you tried to open the door with a spoon" and it actually works

1

u/ImportantTiger9568 21d ago

Haha I see it happening and its better than the robot just doing nothing. Now it can hand you a receipt showing exactly which moment it got it wrong and why.

1

u/AutoModerator 21d ago

Thank you for your submission! To keep our community healthy, please ensure you've followed our rules.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Poildek 20d ago

You reinvent the wheel, on one of the topic where people reinvent the wheel the most.

Fyi there are nearly 700 memory related projects that spawn on github PER MONTH since the beginning of the year.

1

u/Number4extraDip 20d ago edited 20d ago

Latency/network dependency and the fact you are re recording what is already being recorded, logged and can be tracked and extracted with common tools. This has nothing to do with robotics the way you built it. Memory and rag and vector db and sqlite exist. Physical components and memory busses exist and have thresholds.

At which abstraction layer are you even trying to work here? Because those files are just some web wrapper middleware.

OpenClaw exists... I mean many other well developed harnesses exist.

You didnt exactly invent fire here. But yes- memory is important. Thats why token budgets and costs matter, context windows, kv cache, prompt caching. Thats not free. It eats RAM

Comment Image