@RookieRicardoR: MemOS has made new progress. There are quite a few AI Memory solutions now, but many are still at the level of storing chat history. It looks like memory, but it's essentially adding a semantic search to markdown. @MemOS_dev has been working on a memory system for a while, from 1.0 all the way...

X AI KOLs Timeline Products

Summary

MemOS Local Plugin 2.0 update has been released, introducing the "Learn by Doing" feature, which allows the agent to convert key steps during task execution into reusable, scorable cognitive assets, thereby achieving continuous learning and memory in the local environment.

MemOS has made new progress again. There are quite a few AI Memory solutions now, but many are still at the level of storing chat history. It looks like memory, but it's essentially adding a semantic search to markdown. @MemOS_dev has been building a memory system for a while, going from version 1.0 to 2.0. Looking back, a consensus is gradually becoming clear: what truly determines whether an Agent is useful in the future is no longer the model parameters themselves, but whether it can continuously learn, accumulate experience, remember feedback, and reuse capabilities in your own local world. Recently, after the official release of MemOS Local Plugin 2.0, I studied its new features. The feature I think is most worth mentioning in this update is called "Learn by Doing". It doesn't just store conversations. When the Agent helps you complete a task, it breaks down the key steps in the execution process into learnable units, then converts them into scorable, attributable, and reusable cognitive assets. In simpler terms, it doesn't just remember what you said; it remembers how you and the Agent completed a task step by step. Let me give you my recent experience. When using OpenClaw to write a small tool, I explained the code style, naming conventions, and error handling writing style one by one in the first round. It took three or four rounds of revisions to get it right. Before, if I switched conversations or came back a couple of days later, all these things would be lost, and I'd have to explain everything from scratch again. After using this 2.0 update, when I started a new task the next day, it directly applied the writing style we had worked out in the previous round. Let's go through the new features of this update one by one: https://github.com/MemTensor/MemOS/tree/main/apps/memos-local-plugin...
Original Article
View Cached Full Text

Cached at: 05/21/26, 09:40 PM

MemOS has made another leap forward.

There are quite a few approaches to AI Memory now, but many just stop at storing chat logs on the surface — it looks like memory, but in reality it’s just adding semantic search to Markdown.

@MemOS_dev has been working on memory systems for a while, evolving from 1.0 all the way to 2.0. Looking back, a consensus is slowly becoming clear: the next thing that really determines whether an Agent is useful isn’t the model parameters themselves — it’s whether the Agent can continuously learn in your own local world, accumulate experience, remember feedback, and reuse capabilities.

Recently, after the official launch of MemOS Local Plugin 2.0, I took a deep dive into its new features.

The feature I find most worth talking about in this update is called “Execute to Learn.”

It doesn’t just store conversations. Instead, when the Agent helps you complete a task, it breaks down the key steps in the execution process into learnable units, then transforms them into cognitive assets that can be scored, attributed, and reused.

In simpler terms: it doesn’t just remember what you said — it remembers how you and the Agent completed a task step by step.

Let me share a recent personal experience. When I was writing a small tool with OpenClaw, in the first round I laid out the code style, naming conventions, and error handling approach one by one. It took three or four rounds of back-and-forth to get it right.

In the past, switching to a new conversation or coming back a couple of days later would basically lose all that context — I’d have to explain everything from scratch again. But with this 2.0 version, when I started a new task the next day, it automatically applied the same patterns we had refined in the previous session.

Let me walk through the new features one by one:

https://github.com/MemTensor/MemOS/tree/main/apps/memos-local-plugin…

Similar Articles

@berryxia: Guys, the MemOS 2.0 open-source project has been updated again! It has gained 9.3K Stars on GitHub ~ This time, 'AI memory' has been upgraded from an advanced clipboard to true 'execute and learn'. Previously, many memory solutions simply stored chat logs and added semantic search, making it look like memory, but it was actually just RAG...

X AI KOLs Timeline

MemOS 2.0 open-source project update introduces the 'execute and learn' mechanism, enabling the AI Agent to automatically deconstruct and distill experience when completing tasks, evolving hierarchically from raw trajectories to muscle memory, resulting in a dedicated assistant that understands you better as you use it.

@elliotchen100: Our open-source library EverOS recently underwent a major refactoring, transforming the developer experience from "pulling" to "solidifying". Previously, when working with AI memory, we often had to troubleshoot across databases, vector stores, index sync, and dependency environments. Where is the memory stored? Why isn't it recalled? Is the index broken? Many times it was not straight…

X AI KOLs Timeline

The EverOS open-source library has completed a major refactoring, storing original memory directly as Markdown files, supplemented by SQLite for state management and LanceDB for retrieval, significantly improving developer readability, modifiability, and fault recovery.

MemPalace/mempalace

GitHub Trending (daily)

MemPalace is a local-first, open-source AI memory tool that stores conversation history verbatim and retrieves it with semantic search, achieving 96.6% R@5 on LongMemEval without any API calls or LLM. It features a pluggable backend architecture, CLI interface, and supports Claude Code, Gemini CLI, and MCP-compatible tools.