AI agents can already use tools and coordinate, but their memory is fragmented across project files, agent notes, local stores, databases, and vendor-specific systems. Move to a new tool and the context is gone.

UMP v0.1 is a shared format plus a simple way to read, write, update, and move agent memory across tools. The goal is memory that's user-owned, auditable, and extensible across agents and runtimes, instead of locked inside one vendor.

It's early (v0.1) and I'd love feedback on the format and where it breaks down. Repo and spec are linked from the site.

Sorry to be a debbie downer, but this reads like LLM slop rather than engineering work. I don't just mean the language on the page-- although that too (not an X it's a Y, over and over again)-- but the absence of the artifacts of ActualEngineering(tm) rather than just a flood of vibes.

For example, I would expect to see tables or figures showing task success rates on some benchmarks for agents augmented with and without this proposal, perhaps before and after fine tuning, or running against alternatives or to the extent that there are no alternatives against variations of this design that were considered and rejected.

Otherwise what reason is there to think that this design is better than some alternative or even any good at all? Perhaps it causes agents to hallucinate like crazy-- who knows if it hasn't been tested.

Work like that is what makes efforts like this worth sharing and worth reading about-- anyone can spend a few minutes and ask their favorite LLM to design such a framework and get something that looks "credible". But in a post LLM world credible alone is externally indistinguishable from anti-social time wasting slop.

> Injection-resistant by mandate

> Memory is attacker-controllable input. The spec requires a verify, filter, frame rehydration pipeline. Never string-interpolated into the prompt.

Uhhh... so who wants to tell them how LLMs work?

This seems way too complicated and unnecessary. Agents are perfectly capable of discovering memories on the FS, following agent instructions.

I guess this adds indexing and querying but most coding agents have good solutions for this already, and it works automagically for everything, not just memories.

What we could use instead is a file system layout standard, which could subsume memories and a lot more. I don't think that's needed either, but it would probably solve more problems than this.

The ratio of proofreading to grandiosity is impressive.

It is 2026.

Average people build their own harnesses, and imagine themselves the pioneers of industry. They propose protocols. They code, feverishly, into the night, driven by their vision for the future.

It used to be that 'idea guys' were limited by execution. We now feel the avalanche of these ideas, even maybe executed half-decently, fall upon deaf ears and zero market.

I can see the value in a protocol here, but the issue is these efforts are only as good as the industry adoption that they gain: who is using this?

MCP came from Anthropic, A2A from Google so they had big tech backing from day 1.

As a developer, I wouldn’t touch this without confidence I can get gains down the line from interoperability.

initial commit 2 days ago [0] added 5500 lines in a single shot. shows every sign of being entirely LLM-generated.

with apologies to Andy Warhol - in the future, everyone will have a universal protocol for agent memory that is on the HN front page for 15 minutes.

0: https://github.com/edihasaj/universal-memory-protocol/commit...

I would love to know how many countless others on HN, like me, find themselves reading about a very they have built and have been using for months talked about like it’s a revolutionary new idea.