@seclink: 盛大集团创始人陈天桥近年来在 AI 领域(尤其是“AI长期记忆”和“脑科学与 AI 交叉”方向)进行了深度布局。 他主张通过模拟人类大脑的记忆与认知机制,解决大语言模型(LLM)的“遗忘”和上下文受限问题,使 AI Agents 具备连贯…
摘要
盛大集团创始人陈天桥旗下EverMind团队开源了EverMemOS(EverOS),一个类脑智能记忆操作系统,旨在通过模拟人类记忆机制解决大语言模型的遗忘和上下文受限问题,为AI Agents提供长期记忆基础设施。
查看缓存全文
缓存时间: 2026/06/28 09:58
盛大集团创始人陈天桥近年来在 AI 领域(尤其是“AI长期记忆”和“脑科学与 AI 交叉”方向)进行了深度布局。
他主张通过模拟人类大脑的记忆与认知机制,解决大语言模型(LLM)的“遗忘”和上下文受限问题,使 AI Agents 具备连贯、可进化且个性化的长期记忆。
旗舰开源项目:EverMemOS(智能记忆操作系统)
EverMemOS 是由陈天桥旗下的 EverMind 团队推出的一款旗舰级开源、企业级智能记忆系统,被定位为未来 AI Agents 的“数据与记忆基础设施”。
- 类脑级记忆生命周期(Engram-Inspired) EverMemOS 的设计灵感来源于人类大脑的记忆编码、巩固与提取机制,包含三个核心阶段:
情境痕迹形成(Episodic Trace Formation):将实时的对话流转化为 MemCells。MemCells 是记忆的原子单元,用于捕获情境线索、事实以及有时效性的预测信号。
语义整合(Semantic Consolidation):将分散的 MemCells 提炼并组织成更高维度的、具有主题性的语义结构 —— MemScenes。在这个过程中,系统会持续自动演化并更新用户画像(User Profile)。
重构式回忆(Reconstructive Recollection):在 AI 需要决策时,通过 MemScene 引导的 Agent 检索机制重构上下文,帮助下游模型完成长周期的连贯推理。
- 五层技术架构 EverMemOS 将长期记忆的读写流程分层管理:
代理层(Agentic Layer):处理主动的记忆过程,如记忆提取、向量化、检索和重排序。
记忆层(Memory Layer):管理核心存储和情境记忆,专注于 MemCells 的提取与生存周期管理。
检索层(Retrieval Layer):负责多模态检索和对检索结果进行重排序,包括 BM25 + 向量检索的混合搜索以及 RRF(倒数排序融合)等。
业务层(Business Layer):处理上层的业务逻辑与数据操作。
基础设施层(Infrastructure Layer):兼容 MongoDB、Elasticsearch、Milvus、Redis 等主流数据库与缓存组件。
- 性能与生态集成
Token 优化:充当智能注意力过滤器,在部分场景中可将上下文窗口的 Token 消耗降低多达 70%,同时在 LoCoMo 等长期记忆基准测试中达到了 SOTA 性能。
开源生态与插件:MCP(Model Context Protocol)支持:提供了 evermemos-mcp 插件,支持将 AI 编码助手(如 Claude Code、Cursor、Cline 等)接入 EverMemOS 记忆库。
Agent 框架集成:支持 OpenClaw 插件,使智能体能够自动捕获对话、调取历史记忆;同时支持 Live2D 虚拟角色记忆交互等应用。
GitHub 地址:
EverMind-AI/EverOS
Source: https://github.com/EverMind-AI/EverOS
Table of Contents
Why Ever OS
EverOS is a Python library and local-first memory runtime for agents and makers. It gives one portable memory layer across coding assistants, apps, devices, and workflows from day one. It stores conversations, files, and agent trajectories as readable Markdown, then syncs local SQLite and LanceDB indexes for fast retrieval and self-evolving reuse.
| 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 | ✅ Editable, source-backed Markdown knowledge pages with taxonomy, CRUD APIs, and topic search | ❌ Usually separate from memory, trapped in a dashboard, or not tied back to source files |
| Reflection | ✅ Offline memory evolution that merges episode clusters and refines profiles and skills between sessions | ❌ Usually retrieval-only memory with little background consolidation or long-horizon improvement |
Quick Start
Goal: play with the memory visualizer first, then start EverOS, write one real memory, and search it back.
0. Prerequisites
- Python 3.12+
- No API keys are needed for
everos demo. - To run the real server-backed memory flow, create two provider keys before
everos init:
| Capability | Provider | Used for | Fill these .env slots |
|---|---|---|---|
| Chat + multimodal | OpenRouter | LLM / MULTIMODAL | EVEROS_LLM__API_KEY, EVEROS_MULTIMODAL__API_KEY |
| Embedding + rerank | DeepInfra | EMBEDDING / RERANK | EVEROS_EMBEDDING__API_KEY, EVEROS_RERANK__API_KEY |
You can use other OpenAI-compatible providers by changing the matching
*__BASE_URL fields in .env.
1. Install
uv pip install everos
# or: pip install everos
2. Play With The Demo
Run this before configuring API keys or starting the server:
everos demo
The command asks for one memory and one recall question, then opens a full-screen terminal UI. This is an educational visualizer: it is hardcoded, local to the CLI, and does not connect to the EverOS server. Its job is to make the memory lifecycle visible: conversation -> memory sphere -> recall -> source proof -> confetti. See docs/everos-demo.md for the demo scope and TUI source layout.
The sphere moves through ingest, extraction, indexing, recall, source reveal,
and a confetti burst after the first memory lands. Press r to replay and q
to quit.
For the looping showroom view used in README media, run:
everos demo --cinematic
If your shell is not interactive, or you want a copyable preview, use:
everos demo --plain
3. Configure
Generate a starter .env file, then fill the four API key slots shown in the
generated comments. With the default setup, paste your OpenRouter key into the
LLM / MULTIMODAL slots and your DeepInfra key into the EMBEDDING /
RERANK slots.
everos init
# or, from a source checkout:
cp .env.example .env
everos init writes ./.env by default. Use everos init --xdg to
write ${XDG_CONFIG_HOME:-~/.config}/everos/.env instead.
4. Start EverOS
everos server start
Keep the server running, then open a second terminal and check it:
curl http://127.0.0.1:8000/health
Expected response:
{"status":"ok"}
everos server start searches for .env in this order: --env-file <path> →
./.env (cwd) → ${XDG_CONFIG_HOME:-~/.config}/everos/.env → ~/.everos/.env.
The endpoint stack is OpenAI-protocol compatible (OpenAI / OpenRouter / vLLM /
Ollama / DeepInfra) - override *__BASE_URL in the generated .env to point
at any of them.
Now make the demo real. In the second terminal, run:
everos demo --live
Live demo mode connects to the running server and performs the real
/health -> /api/v1/memory/add -> /api/v1/memory/flush ->
/api/v1/memory/search flow before opening the same memory sphere UI. Use
--server-url <url> if your server is not on http://127.0.0.1:8000.
5. Try Your First Memory
Add a tiny conversation:
TS=$(($(date +%s)*1000))
curl -X POST http://127.0.0.1:8000/api/v1/memory/add \
-H 'Content-Type: application/json' \
-d "{
\"session_id\": \"demo-001\",
\"app_id\": \"default\",
\"project_id\": \"default\",
\"messages\": [
{\"sender_id\": \"alice\", \"role\": \"user\", \"timestamp\": $TS, \"content\": \"I love climbing in Yosemite every spring.\"},
{\"sender_id\": \"alice\", \"role\": \"user\", \"timestamp\": $((TS+10000)), \"content\": \"My favorite coffee shop is Blue Bottle in SOMA.\"}
]
}"
Force extraction for the local demo:
curl -X POST http://127.0.0.1:8000/api/v1/memory/flush \
-H 'Content-Type: application/json' \
-d '{"session_id":"demo-001","app_id":"default","project_id":"default"}'
Search it back:
curl -X POST http://127.0.0.1:8000/api/v1/memory/search \
-H 'Content-Type: application/json' \
-d '{
"user_id": "alice",
"app_id": "default",
"project_id": "default",
"query": "Where do I like to climb?",
"top_k": 5
}'
You should see the Yosemite memory in the response. If the result is empty on the first try, wait a moment and retry; Markdown is written synchronously, while the local index catches up in the background.
First memory unlocked. You just gave EverOS a fact, flushed it into durable Markdown-backed memory, and searched it back through the local index. That is the core loop. Want to see the source of truth? Open
~/.everosand inspect the generated Markdown files.
For annotated responses and the Markdown files EverOS creates, see QUICKSTART.md.
Optional: Ingest Multimodal Files
To ingest non-text content (image / pdf / audio / office documents)
through /api/v1/memory/add content items, install the optional
extra:
uv pip install 'everos[multimodal]' # or: pip install 'everos[multimodal]'
This pulls in everalgo-parser (with the [svg] bundle for SVG
support via cairosvg) and wires up the multimodal LLM client
(EVEROS_MULTIMODAL__* fields in .env, defaults to
google/gemini-3-flash-preview via OpenRouter).
Office document support requires LibreOffice as a system dependency.
The parser shells out to soffice (LibreOffice’s headless renderer) to
convert .doc / .docx / .ppt / .pptx / .xls / .xlsx to PDF
before feeding the result into the multimodal LLM. Without LibreOffice,
office uploads return HTTP 415 with a clear error message; PDF / image
/ audio / HTML / email parsing is unaffected.
Install on the host before serving office documents:
brew install --cask libreoffice # macOS
sudo apt-get install -y libreoffice # Debian / Ubuntu
For Contributors
git clone https://github.com/EverMind-AI/EverOS.git
cd EverOS
uv sync # creates ./.venv and installs deps
source .venv/bin/activate # or prefix commands with `uv run`
everos demo --plain # try the local educational demo; no API keys needed
everos init # paste OpenRouter + DeepInfra keys into .env
everos --help
make test
Use Cases
Now that you have had your first successful EverOS moment, explore what people are building with persistent memory across agents, apps, and community integrations.
Use cases show what persistent memory makes possible in real products and workflows. Some examples are packaged in this repository; others point to external demos or integrations you can study and adapt.
Reunite - Find With EverOSParents describe what they remember. Children describe what they recall. Reunite uses semantic memory to surface the connections. |
Hive OrchestratorBrowser-native hive-mind for CLI coding agents - Claude Code, Codex, Gemini, and OpenCode collaborate as real PTY processes via a team protocol. |
AI Coding Assistants With EverOSUniversal long-term memory layer for AI coding assistants, powered by EverOS. |
AI Data TechnicianAn agentic AI system that learns from scientist interaction to inspect, analyze, and classify high-dimensional time series data - with persistent memory that improves across sessions. |
Rokid AI Assistant With EverOSConnect to EverOS within Rokid Glasses enabling long-term memory for all of your smart activities. Coming soon |
Creative Assistant With MemoryCreative assistant with long-term memory, so your creative context stays available across sessions. Coming soon |
|
|
|
Earth Online Memory GameEarth Online is a memory-aware productivity game that turns everyday planning into a living quest log. |
Multi-Agent Orchestration PlatformGolutra presents a multi-agent workforce for engineering teams, extending the IDE model from a single assistant to coordinated agents. |
Your Personal Tasting UniverseRecord, visualize, and explore your tasting journey through an immersive 3D star map. |
EverOS Open HerBuild AI that feels. Open-source persona engine - personality emerges from neural drives, not prompts. Inspired by Her. |
Browser Agent For Personal MemoryRuminer brings persistent memory to a browser agent so it can carry personal context across web tasks. |
EverMem Sync With EverOSOne command to connect any AI coding CLI to EverMemOS long-term memory. |
|
|
|
MCO - Orchestrate AI Coding AgentsMCO equips your primary agent with an agent team that can work together to solve complex tasks. |
Study Buddy With Self-Evolving MemoryStudy proactively with an agent that has self-evolving memory. |
Alzheimer’s Memory AssistantEmpowering individuals with advanced memory support and daily assistance. |
Memory-Driven Multi-Agent NPC ExperienceAn iOS sci-fi mystery game where players explore and uncover the truth. |
Mobi CompanionAn iOS app where users create, nurture, and live with a personalized AI companion called Mobi. |
AI Wearable With MemoryA context-native AI wearable that listens to everyday life and converts conversations into memory. |
|
|
|
Legacy OpenClaw Agent MemoryArchived pre-1.0.0 plugin reference. New integrations should use the current EverOS API. |
Live2D Character With MemoryAdd long-term memory to a real-time Live2D character, powered by TEN Framework. |
Computer-Use With MemoryRun screenshot-based analysis with computer-use and store the results in memory. |
Game Of Thrones MemoriesA demonstration of AI memory infrastructure through an interactive Q&A experience with A Game of Thrones. |
Claude Code PluginPersistent memory for Claude Code. Automatically saves and recalls context from past coding sessions. |
Memory Graph VisualizationExplore stored entities and relationships in a graph interface. Frontend demo; backend integration is in progress. |
Documentation
- docs/everos-demo.md — Demo scope and TUI source layout
- docs/how-memory-works.md — Markdown, SQLite, LanceDB, and recall flow
- docs/use-cases.md — Full use-case gallery and integration examples
- docs/engineering.md — Contributor engineering reference: build, test, CI, conventions
- docs/migration-to-1.0.0.md — Legacy API migration notes
- CHANGELOG.md — Release notes
- CONTRIBUTING.md — How to contribute
Star Us
If EverOS is useful to your agent stack, please star the repo. It helps more builders discover the project and gives the memory ecosystem a stronger signal to keep improving.
Star History
EverMind Ecosystems
EverMind is an open-source ecosystem for long-term memory, self-evolving agents, and memory evaluation.
| EverMind Open-Source Ecosystem | |
|---|---|
| Memory Runtime | EverOS - the local memory operating system and research-backed runtime for agent and user memory. |
| Algorithm Engine | EverAlgo - stateless extraction, ranking, parsing, and memory operators that power EverOS. |
| Hypergraph Memory | HyperMem - hypergraph memory for long-term conversations, with its own benchmark-backed topic -> episode -> fact retrieval method. |
| Benchmarks | EverMemBench · EvoAgentBench - evaluation suites for conversational memory and agent self-evolution. |
| Long-Context Research | MSA - Memory Sparse Attention for scalable latent memory and 100M-token contexts. |
| Personal Memory Layer | EverMe - CLI and agent plugin suite for cross-device, cross-agent personal memory. |
| Developer Integrations | evermem-claude-code · everos-plugins - plugins, skills, and migration tooling for AI coding agents. |
Together, these repositories form EverMind’s research-to-runtime stack: new memory methods, reusable algorithms, benchmark evidence, and practical agent integrations.
Contributing
Contributions are welcome across the whole repository: memory methods, benchmark coverage, use-case examples, documentation, and bug fixes. Browse Issues to find a good entry point, then open a PR when you are ready.
Welcome all kinds of contributions 🎉
Help make EverOS better. Code, documentation, benchmark reports, use-case write-ups, and integration examples are all valuable. Share your projects on social media to inspire others.
Connect with one of the EverOS maintainers @elliotchen200 on 𝕏 or @cyfyifanchen on GitHub for project updates, discussions, and collaboration opportunities.
Code Contributors
License
Apache License 2.0 — see NOTICE for third-party attributions.
Citation
If you use EverOS in research, see CITATION.md.
相似文章
@Pluvio9yte: https://x.com/Pluvio9yte/status/2070318502016426008
本文深入探讨了AI Agent的记忆架构,以Hermes四层记忆模型为例,分析了Claude Code记忆系统的局限性,并介绍了如何通过开源框架(如EverOS)为Agent增添本地记忆能力,提供了详细部署步骤。
@yyyole: Agent memory的创业方向好火爆! 很多团队都在做,大概有下面几种比较主流的思路: 第一种最粗暴:context路线,把上下文增长。 第二种最常见:RAG / 向量库路线,接一个向量库把历史内容 embedding 后做检索。 第…
介绍Agent memory创业的几种主流思路,并推荐EverMind团队的开源项目EverOS,它提供以Markdown为源的本地记忆操作系统,支持双轨记忆、多模态摄取和自演化能力。
@seclink: 陈天桥再不努力一把, 大模型记忆就要被字节偷家了... 赶了个大早, 很努力,但是执行的人不行 ... OpenViking 开源的 cli 工具做了好多迭代优化... 早晚你们会想起,用AI 编程改造复杂项目时, 一定会用上大模型记忆的…
OpenViking是一个开源的CLI工具,旨在通过大模型记忆功能优化复杂项目的AI编程体验并节省token。文章评论了其在执行层面的表现以及与字节跳动等竞争者在LLM记忆领域的动态。
@seclink: GBrain 是 Y Combinator 总裁 Garry Tan 在 2026 年 4 月开源的一个 AI Agent 持久记忆系统(Memory Layer)。 它本质上是一个“自布线知识图谱 + 混合检索层”,专门解决 AI Ag…
GBrain 是 Y Combinator 总裁 Garry Tan 开源的一个 AI Agent 持久记忆系统,通过自布线知识图谱和混合检索层解决 Agent 的长期记忆和知识累积问题。
@AYi_AInotes: https://x.com/AYi_AInotes/status/2069399806502453264
一篇保姆级教程,介绍如何用30分钟为AI Agent搭好持久记忆,使用开源的EverOS工具,将记忆存储为可编辑的Markdown文件,无需Docker或向量库集群。