user_id, agent_id,
-## Why EverOS
-
-EverOS is an open-source Python framework for self-evolving long-term
-memory across agents and platforms. It gives makers one portable memory
-layer for every agent they use - Claude Code, Codex, OpenClaw, Hermes,
-and more - so context, decisions, files, and trajectories can follow the
-work instead of staying trapped in one tool.
+## How EverOS Is Different
-EverOS stores conversations, agent trajectories, and files as readable
-Markdown, then syncs local SQLite and LanceDB indexes for fast retrieval.
-Agents can reuse past cases and skills, improve from repeated workflows,
-and become more proactive over time.
-
-The system is built around three boundaries:
-
-1. **Memory content stays readable** - Markdown is the durable source of truth.
-2. **Runtime state stays local** - SQLite tracks state and LanceDB handles vector, BM25, and scalar-filter search.
-3. **Algorithms stay modular** - [EverAlgo](https://github.com/EverMind-AI/EverAlgo) owns memory algorithms; EverOS owns runtime, persistence, online flows, and offline evolution.
+| Title | +EverOS | +Other Agent Memory Libraries | +
|---|---|---|
| Markdown source of truth | +✅ Canonical .md files that are readable, editable, diffable, and Git-versioned |
+❌ Usually API, vector, graph, dashboard, or database state | +
| Direct file editing | +✅ Edit .md files; cascade watcher syncs |
+❌ Usually SDK, API, dashboard, or backend update paths | +
| Local three-part stack | +✅ Markdown + SQLite + LanceDB; no MongoDB, Elasticsearch, or Redis required | +❌ Often depends on managed services, vector DBs, graph DBs, or server stacks | +
| User + agent tracks | +✅ User episodes/profile and agent cases/skills are separate first-class surfaces |
+❌ Usually centered on chat history, profiles, entities, facts, or retrieval records | +
| Orthogonal retrieval | +✅ Search by user_id, agent_id, app_id, project_id, and session_id |
+❌ Usually app, namespace, tenant, thread, or graph scoped | +
| Knowledge Wiki | +✅ Coming next: editable, source-backed Markdown knowledge pages built from memory | +❌ Usually retrieval, graph, dashboards, or generated summaries instead of editable source-backed pages | +
| Dreaming / Reflection | +✅ Coming next: Reflection that runs when the system is idle or offline to connect signals, compress history, and improve profiles and skills between sessions | +❌ Usually online read/write APIs, retrieval records, or summaries rather than idle-time memory consolidation | +
@@ -665,9 +710,34 @@ Explore stored entities and relationships in a graph interface. Frontend demo; b
## Watch EverOS
EverOS 1.0.0 is the first release of a larger memory-system roadmap.
-Watch this repository for upcoming work on Wiki-style memory, Dreaming,
-deeper offline evolution, benchmark releases, and more real-world agent
-integrations.
+Watch this repository for upcoming work on deeper idle-time and offline evolution,
+benchmark releases, and more real-world agent integrations.
+
+
+
+
+Most memory systems stop at chat history, opaque profiles, or vector recall.
+EverOS keeps memory local, Markdown-native, auditable, and self-evolving: raw
+memory stays readable, derived knowledge becomes a wiki, and Reflection turns
+repeated experience into more useful long-term behavior.
If EverOS is useful to your agent stack, starring the repo helps more
builders discover it.
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 1a382d599..c2b3cc75c 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -1,6 +1,6 @@
|
+Knowledge Wiki + +Turns scattered episodes, files, facts, and agent traces into source-backed +Markdown pages for people, projects, topics, decisions, and workflows. Memory +becomes something users can read, correct, link, version, and open in their +existing Markdown tools. + |
+
+Dreaming / Reflection + +Runs when the system is idle or offline to revisit stored memory, connect weak +signals, compress noisy history into durable patterns, and improve profiles and +skills. The agent gets better between active sessions, not only while you prompt +it. + |
+
-
+
-- [EverOS 1.0.0 亮点](#everos-100-亮点)
-- [为什么选择 EverOS](#为什么选择-everos)
+- [EverOS 1.0.0](#everos-100)
+- [EverOS: One Memory For All](#everos-one-memory-for-all)
+- [EverOS 的差异](#everos-的差异)
- [快速开始](#快速开始)
- [架构概览](#架构概览)
- [存储布局](#存储布局)
@@ -39,7 +40,7 @@
-## EverOS 1.0.0 亮点
+## EverOS 1.0.0
> [!IMPORTANT]
>
@@ -48,8 +49,24 @@
> 多模态摄取、用户记忆与 Agent 记忆作用域，以及由
> [EverAlgo](https://github.com/EverMind-AI/EverAlgo) 支撑的模块化算法。
>
-> **欢迎 Watch 这个仓库。** 下一阶段我们会继续推进记忆系统方法，
-> 包括 Wiki 式知识层和用于更深层离线进化的 Dreaming。
+> **即将推出：** Knowledge Wiki 会把记忆整理成可编辑、可溯源的
+> Markdown 知识页。Reflection（也称 Dreaming）会在系统空闲或离线时
+> 连接信号、压缩历史，并持续改进 profile 和 skills。
+
+
+
+
+[](#readme-top)
+
+
+
+
+## EverOS: One Memory For All
+
+EverOS 是面向 agents 和 makers 的本地记忆操作系统。它提供一层可携带的
+统一记忆层，让记忆穿过 coding assistants、apps、devices 和 workflows。
+目前它会把对话、文件和 Agent 轨迹保存为可读 Markdown，并同步本地 SQLite
+和 LanceDB 索引，用于快速检索和自进化复用。
| Title | +EverOS | +Other Agent Memory Libraries | +
|---|---|---|
| Markdown source of truth | +✅ 标准 .md 文件：可读、可编辑、可 diff、可 Git 版本化 |
+❌ 通常是 API、vector、graph、dashboard 或 database state | +
| 直接文件编辑 | +✅ 编辑 .md；cascade watcher 同步 |
+❌ 通常需要 SDK、API、dashboard 或 backend update path | +
| 本地三件套 | +✅ Markdown + SQLite + LanceDB；不需要 MongoDB、Elasticsearch 或 Redis | +❌ 常依赖 managed service、vector DB、graph DB 或 server stack | +
| 用户 + Agent 双轨 | +✅ 用户 episodes/profile 与 Agent cases/skills 是分离的一等记忆表面 |
+❌ 通常围绕 chat history、profiles、entities、facts 或 retrieval records | +
| 正交检索作用域 | +✅ 按 user_id、agent_id、app_id、project_id 和 session_id 检索 |
+❌ 通常按 app、namespace、tenant、thread 或 graph 来组织 | +
| Knowledge Wiki | +✅ 即将推出：由记忆形成可编辑、可溯源的 Markdown 知识页 | +❌ 通常是 retrieval、graph、dashboard 或 generated summaries，而不是可编辑、可溯源的知识页 | +
| Dreaming / Reflection | +✅ 即将推出：在系统空闲或离线时运行，用来连接信号、压缩历史，并在 session 之间改进 profiles 和 skills | +❌ 通常是在线读写 API、retrieval records 或 summaries，而不是空闲态记忆整理 | +
@@ -651,8 +696,30 @@ Claude Code 的持久记忆插件。自动保存并回忆过去 coding sessions
## 关注 EverOS
EverOS 1.0.0 是更大规模记忆系统路线图的第一个发布版本。Watch 这个仓库，
-即可持续关注 Wiki 式记忆、Dreaming、更深入的离线进化、benchmark releases，
-以及更多真实 Agent 集成。
+即可持续关注更深入的空闲态和离线进化、benchmark releases，以及更多真实 Agent 集成。
+
+
+
+
+许多记忆系统停留在聊天历史、黑盒 profile 或向量召回。EverOS 的差异在于：
+记忆保持本地、Markdown-native、可审计、可自进化；原始记忆仍然可读，
+衍生知识沉淀为 wiki，Reflection 则把重复经验转化为更有用的长期行为。
如果 EverOS 对你的 Agent stack 有帮助，Star 这个仓库也会帮助更多 builders
发现它。
|
+Knowledge Wiki + +把分散的 episodes、files、facts 和 Agent traces 整理成有来源的 Markdown +知识页，覆盖 people、projects、topics、decisions 和 workflows。记忆不再只是 +向量召回结果，而是用户可以阅读、修正、链接、版本化，并用现有 Markdown 工具打开的知识层。 + |
+
+Dreaming / Reflection + +在系统空闲或离线时运行，重新审视已存储记忆，连接弱信号，把嘈杂历史压缩成稳定模式， +并持续改进 profile 和 skills。目标是让 Agent 在活跃 session 之间也能变得更好， +而不是只在你 prompt 它时才进步。 + |
+