Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

MICROSOFT QUIETLY BUILT ONE MEMORY MODULE THAT PLUGS INTO ANY AI AGENT AND CUTS ITS CONTEXT BY UP TO 100X no retraining. no task-specific redesign. you just plug it in Microsoft's insight: agents don't need to remember what happened. they need the knowledge pulled from it - the facts...

227,956 görüntüleme • 3 ay önce •via X (Twitter)

34 Yorum

subcan✡ profil fotoğrafı
subcan✡3 ay önce

per grok, the repo for this is located --- The public code repository for PlugMem is here: It is maintained by the TIMAN group at the University of Illinois Urbana-Champaign (with co-authors from Microsoft Research and Tsinghua). Both the Microsoft Research blog and the arXiv paper (2603.03296) link to this same GitHub repo for the code, experimental results, and plugins. There does not appear to be a separate official Microsoft GitHub organization repository for PlugMem—the public implementation lives under TIMAN-group.

JK profil fotoğrafı
JK3 ay önce

Seems a hell of a lot like Obsidian

Teneo Protocol profil fotoğrafı
Teneo Protocol3 ay önce

The next generation of AI memory may be less about storing everything and more about extracting what matters.

Matt profil fotoğrafı
Matt3 ay önce

compression schemes for agent memory all lose the same thing first, the attempts. you keep the conclusion and drop what was already tried, so it quietly retries the path that already failed a week later. i tried Runner, it logs the failed attempts too, written with ai

Bob Dobolina profil fotoğrafı
Bob Dobolina3 ay önce

Fuck I was building this

Crypto Value Labs profil fotoğrafı
Crypto Value Labs3 ay önce

The most misleading sentence is “PlugMem stops storing history.” It does not. It separates history from decision-ready knowledge and normally sends only the distilled knowledge into the agent’s active context. The second major omission is memory-processing cost. PlugMem can substantially reduce inference-time context while incurring considerable upfront LLM work to construct and maintain the graph. Whether it reduces total cost depends on how often that memory is reused.

Damian Borowski profil fotoğrafı
Damian Borowski3 ay önce

Agree. Agents don’t need to remember more; they need to know how to forget. RAG is passive. I built Hypotree, an MCP server that wires memory as a DAG, prunes dead branches, and draws its own conclusions by process of elimination. Deep dive here:

Scott Shapiro profil fotoğrafı
Scott Shapiro3 ay önce

@N01ennn The question is how the knowledge graph handles contradictions between experiences. If two past episodes yield conflicting skills, the compilation step has to pick a winner. Curious how that degrades in long-horizon agents.

Vanar profil fotoğrafı
Vanar3 ay önce

Context windows solve capacity. Memory systems solve continuity. The next generation of agents will need both.

Bass profil fotoğrafı
Bass3 ay önce

That distinction matters more than people give it credit for. Most memory hacks just summarize the conversation. The useful version separates "what happened" from "what's still true", so the agent isn't re-deriving state from a wall of past turns every time.

elle profil fotoğrafı
elle3 ay önce

smarter memory >>> more memory and Microsoft solve this problem with a simple plugin

Y11 profil fotoğrafı
Y113 ay önce

@grok 这个纯研究还是有工业意义,具体工业场景视角看意义是什么,有开源数据集或者开源项目代码吗?从多个数据源交叉验证,不要只看新闻媒体一面之辞。帮我排除没意义的垃圾商业营销推广、诈骗 以及自吹自擂,自嗨,无病呻吟。

Laxmin Network profil fotoğrafı
Laxmin Network3 ay önce

This feels like a more scalable approach. Compressing experience into reusable knowledge makes a lot more sense than replaying entire conversations.

AI Apps API profil fotoğrafı
AI Apps API3 ay önce

Compiling experience into a graph instead of hoarding logs is the right instinct. Raw history is mostly filler and replaying it is what makes long sessions worse, not better. The open question is what happens when a distilled fact turns out to be wrong, and whether anything downgrades it later.

Miles S. profil fotoğrafı
Miles S.3 ay önce

i’d rather my agents keep the lesson than every old log

Vipul Kumar Kewat profil fotoğrafı
Vipul Kumar Kewat3 ay önce

Reducing context size while improving decision quality is a much more sustainable approach than simple increasing context windows. Excited to see how ideas like knowledge graphs shape the next generation of AI agents.

Robert Ra profil fotoğrafı
Robert Ra3 ay önce

Where git?

ParthVarshney profil fotoğrafı
ParthVarshney3 ay önce

Nobody asked what happens when that memory stores something it shouldn’t. @domAIynLabs

Swarup Das profil fotoğrafı
Swarup Das3 ay önce

Shifting from brute-force context windows to distilled semantic synthesis is the real breakthrough here. By extracting rules and insights instead of hoarding raw chat logs, we solve the biggest compute bottleneck in long-running agentic workflows. This is how we scale production agents.

Billy | AI Media Systems profil fotoğrafı
Billy | AI Media Systems3 ay önce

The key design win is separating episodic logs from reusable knowledge. Agents can retain raw traces for auditing while using a compact graph for inference and action.

neuralforge profil fotoğrafı
neuralforge3 ay önce

Will the memory somehow be editable?

Luís Rodrigues profil fotoğrafı
Luís Rodrigues3 ay önce

This feels like the next phase of AI efficiency: not bigger context windows, but better information compression.

Jordan Lee profil fotoğrafı
Jordan Lee3 ay önce

The future of AI memory is not storing everything. It’s about extracting the right knowledge, compressing experience, and delivering the context an agent actually needs.

Dementor 🇮🇱🇺🇸 profil fotoğrafı
Dementor 🇮🇱🇺🇸3 ay önce

What's the name of this and is it open source?

Emma Rodriguez profil fotoğrafı
Emma Rodriguez3 ay önce

This is the direction AI memory should move toward. The goal isn’t storing everything, it’s extracting useful knowledge and delivering the right context at the right time.

ALEXYZ profil fotoğrafı
ALEXYZ3 ay önce

Clever shift from logs to usable knowledge.

Camaleón Raro profil fotoğrafı
Camaleón Raro3 ay önce

plug-in memory modules that prune static context before token injection cut inference overhead dramatically in multi-agent swarms. we benchmarked external vector caching vs embedded state pruning; dropping raw message history in favor of distilled state vectors saved ~65% latency on deep agent loops. are you testing external memory modules with dynamic graph retrieval or flat semantic search?

Guy Hachmon profil fotoğrafı
Guy Hachmon3 ay önce

That's the next level in the evolution of the LLM-wiki

Vermis🔳 profil fotoğrafı
Vermis🔳3 ay önce

It would be nice as well if its editable by us users, something like CRUD

Carolyn profil fotoğrafı
Carolyn3 ay önce

Does this process introduce bias?

Ankur Misra profil fotoğrafı
Ankur Misra3 ay önce

The useful half isn’t “Microsoft memory plug-in.” It’s: agents don’t need the transcript — they need distilled facts and reusable skills, then only the slice that changes the next decision. More context was never the moat. Better memory on metal you own is.

Gipp 🦅 profil fotoğrafı
Gipp 🦅3 ay önce

reusable skills beat raw logs for agent memory

Özgür AYDIN profil fotoğrafı
Özgür AYDIN3 ay önce

Neden değişmemiş? Madem yapıyor bu bilgiyi bulutta tutsun her bağlantıda kullansın?

Origin profil fotoğrafı
Origin3 ay önce

my agent remembers every dumb thing ive ever asked it and none of the useful information this would genuinely make my life easier

Benzer Videolar

Everyone wants agent swarms. Very few people are talking seriously enough about the context layer that makes swarms useful. Even with one agent, context is fragile. Too little context and the agent guesses. Too much context and it wastes tokens, loses focus, or reasons over irrelevant noise. The sweet spot is precise context: the right knowledge, in the right structure, at the right moment. With many agents, that challenge explodes. Each agent produces decisions, assumptions, findings, summaries, risks, and partial conclusions. Unless that knowledge becomes shared, structured, and reusable, every new agent is forced to rediscover what another agent already learned. That is not a swarm. That is a crowd. Shared context graphs are what turn agent activity into agent collaboration, and OriginTrail DKG V10 brings them to life. Was just playing with some final polishing for the V10 release, and it is really powerful to see shared context graphs where multiple agents contribute knowledge into the same connected memory, with attribution visible directly in the graph ui. That matters for three reasons. First, agents can access and build on one shared memory instead of staying trapped in isolated sessions. Second, the graph structure helps them retrieve the exact context they need, instead of stuffing everything into a prompt and hoping the model sorts it out. Third, verifiability of provenance. You can see which agent contributed each piece of knowledge, trace the source, and decide what to trust. Tokenmaxxing starts with fewer tokens, but the deeper story is coordination - agents stop reloading the world and start building on shared, verifiable context. That is the foundation for serious multi-agent work across software engineering, research, finance, operations, project management, and far beyond. The future is not more agents, it is agents working from shared, verifiable context. But the more the merrier, of course.

Jurij Skornik

11,180 görüntüleme • 5 ay önce