同一套 Reflect2Evolve 核心,同时接入 OpenClaw 和 Hermes
本地存储 分层记忆 技能结晶 Viewer 可观测
One Reflect2Evolve core for both OpenClaw and Hermes.
Local storage, layered memory, skill crystallization, and an observable Viewer.
宿主适配器隔离,算法核心共享,运行时数据按 agent 分开保存Isolated host adapters, shared algorithm core, per-agent runtime data
MemOS 为 OpenClaw 与 Hermes 提供同一套本地优先的分层记忆核心。MemOS gives both OpenClaw and Hermes the same local-first layered memory core.
记忆、技能、日志和配置都保存在本机运行时目录。Memory, skills, logs, and config stay in the local runtime directory.
Viewer 可查看 trace、policy、world model、skill、日志与配置。The Viewer exposes traces, policies, world models, skills, logs, and settings.
高价值 trace 归纳成 L2 policy,成熟策略再结晶为可调用 Skill。High-value traces induce L2 policies, and mature policies crystallize into callable Skills.
Embedding 与 LLM 可分别选择本地、OpenAI 兼容、Gemini、Anthropic、Bedrock 等提供方。Embedding and LLM backends can be configured independently across local and cloud providers.
配置中保留 Hub 能力入口;默认关闭,不影响本地记忆主流程。Hub configuration is available as an optional surface and stays out of the local memory path by default.
OpenClaw 与 Hermes 使用独立运行时目录和 Viewer 端口,避免数据归属混淆。OpenClaw and Hermes use separate runtime homes and Viewer ports to keep ownership clear.
每个回合先沉淀为 L1 trace,再由反馈信号驱动 L2 policy、L3 world model 和 Skill 生成。算法核心与宿主无关,因此 OpenClaw 和 Hermes 使用同一套演化逻辑。Turns become L1 traces first; feedback then drives L2 policies, L3 world models, and Skills. The algorithm core is host-agnostic, so OpenClaw and Hermes share the same evolution loop.
L1 trace: action + observation + reflection + value Reward: V_t = alpha_t * R + (1-alpha_t) * gamma * V_{t+1} L2 policy: trigger + procedure + verification + boundary L3 world: project/environment knowledge from L2 + L1 Skill: invocation guide + procedureJson ✓ Retrieval injects Skill → Trace/Episode → World Model
OpenClaw 适配器在 TypeScript 进程内直接调用 core;Hermes 适配器通过 Python MemoryProvider 和 JSON-RPC bridge 访问同一个 core。适配器只处理宿主协议,算法、存储、检索和技能生命周期都留在共享核心里。The OpenClaw adapter calls core in-process from TypeScript; the Hermes adapter reaches the same core through a Python MemoryProvider and JSON-RPC bridge. Adapters handle host protocol only; storage, retrieval, and skill lifecycle stay shared.
OpenClaw: before_prompt_build → core.onTurnStart() agent_end → core.onTurnEnd() Hermes: prefetch → JSON-RPC turn.start sync_turn → JSON-RPC turn.end ✓ Same SQLite schema and retrieval pipeline
内置 Web 管理面板可查看 trace、policy、world model、skill、日志、配置和导入状态。OpenClaw 默认端口 18799,Hermes 默认端口 18800。The built-in dashboard shows traces, policies, world models, skills, logs, settings, and import state. OpenClaw uses port 18799; Hermes uses 18800.
OpenClaw 与 Hermes 的差异只存在于 adapter 层;core、server、viewer、SQLite schema 和算法事件保持一致。OpenClaw and Hermes differ only at the adapter layer; core, server, viewer, SQLite schema, and algorithm events stay shared.
OpenClaw 使用进程内 TS 插件;Hermes 使用 Python provider + bridge。OpenClaw uses an in-process TS plugin; Hermes uses a Python provider plus bridge.
DTO、事件、错误码和 JSON-RPC 方法名在这里稳定下来。DTOs, events, errors, and JSON-RPC method names live here.
capture、reward、L1/L2/L3、skill、retrieval、storage、logger 都在共享核心里。Capture, reward, L1/L2/L3, skills, retrieval, storage, and logging live in the shared core.
HTTP + SSE 提供 Viewer 与调试入口,每个宿主有独立端口。HTTP + SSE power the Viewer and diagnostics, with one port per host.
macOS / Linux 安装器会自动检测 OpenClaw 与 Hermes,并写入对应运行时目录。The macOS/Linux installer auto-detects OpenClaw and Hermes and writes each runtime home.
安装脚本会下载 npm 包、安装生产依赖、生成 config.yaml,并为 OpenClaw / Hermes 启动各自的 Viewer。
遇到安装问题?查看排查指南 →The script downloads the npm package, installs production dependencies, writes config.yaml, and starts the per-host Viewer.
Install issues? See troubleshooting guide →
网页面板:OpenClaw 默认 http://127.0.0.1:18799,Hermes 默认 http://127.0.0.1:18800。运行时配置写在各自的 config.yaml。Web panel: OpenClaw defaults to http://127.0.0.1:18799, Hermes to http://127.0.0.1:18800. Runtime config lives in each host's config.yaml.
version: 1 viewer: port: 18799 # OpenClaw; Hermes uses 18800 embedding: provider: local apiKey: "" llm: provider: host # Hermes: openai_compatible or another real provider apiKey: "" model: "" hub: enabled: false telemetry: enabled: true logging: level: info
Embedding 与 LLM 后端独立配置;无云端 key 时仍可使用本地 embedding 和宿主模型能力。Embedding and LLM backends are configured independently; local embedding and host LLM paths remain available where supported.
三层检索Three-tier search
读取 trace / policy / world modelFetch trace / policy / world model
查看 episode 时间线Episode timeline
查询 L3 环境认知Query L3 world models
列出候选和活跃技能List candidate and active skills
获取技能调用指南Fetch invocation guide
OpenClaw 与 Hermes 默认各自本地隔离。显式开启 Team Sharing 后,多个实例可以通过 Hub 共享技能和可选 Trace 摘要;私有数据库、配置与日志仍留在本机。OpenClaw and Hermes stay isolated by default. When Team Sharing is explicitly enabled, multiple instances can share skills and optional trace excerpts through a Hub while private DBs, config, and logs remain local.
OpenClaw 与 Hermes 的数据库、技能包和日志默认互不共享。OpenClaw and Hermes keep DBs, skill bundles, and logs separate by default.
hub.enabled、hub.address 和 token 写入 config.yaml 后才加入团队。Instances join a team only after hub.enabled, hub.address, and tokens are configured.
适合共享已结晶 Skill 和可选 Trace 摘要,而不是直接合并私有数据库。Designed for sharing crystallized skills and optional trace excerpts, not merging private databases.
Hub 不可用时,本地记忆、检索和 Skill 生命周期仍按本机流程运行。If the Hub is unavailable, local memory, retrieval, and skill lifecycle continue normally.
Viewer 提供导入入口:OpenClaw 读取原生 session JSONL,Hermes 读取原生 MEMORY.md;也支持 MemOS JSON bundle 的导入导出。The Viewer exposes import paths for OpenClaw native session JSONL, Hermes native MEMORY.md, and MemOS JSON bundles.
OpenClaw 与 Hermes 只扫描当前 Viewer 所属宿主的数据源。OpenClaw and Hermes scan only the data source for the current Viewer host.
导出文件可重新导入,用于迁移设备或备份本地记忆。Exported bundles can be imported again for device migration or backup.
原生导入按 offset / limit 分批执行,避免一次性处理过多历史数据。Native import runs in offset / limit batches to avoid processing too much history at once.
导入入口写入 trace bundle;后续价值、策略和技能由核心算法按正常流程处理。Import writes trace bundles; value, policy, and skill evolution remain handled by the core pipeline.
从企业到个人,从云端到本地,围绕 MemOS 构建完整 AI 记忆能力栈。From enterprise to personal use, from cloud to local-first deployments, MemOS anchors the full AI memory stack.
企业级 OpenClaw 智能体平台Enterprise OpenClaw agent platform
面向团队与企业落地,提供智能体编排、经验沉淀、治理和云电脑沙箱能力。Built for teams and enterprise deployment, with agent orchestration, experience capture, governance, and cloud sandboxing.
个人记忆助手,支持长期会话记忆Personal memory assistant with long-term conversation memory
跨 session 持久化记忆,让不同 AI 应用逐步理解你的偏好与上下文。Cross-session persistent memory helps AI apps gradually understand your preferences and context.

OpenClaw 云插件OpenClaw Cloud Plugin
为 OpenClaw 注入云端持久记忆,Inject cloud persistent memory into OpenClaw, 快速接入托管记忆服务quickly connect managed memory
OpenClaw / Hermes 本地插件OpenClaw / Hermes Local Plugin
共享 Reflect2Evolve 核心,Shared Reflect2Evolve core, 完全本地 · 双宿主适配fully local · two host adapters
MemOS Cloud
开箱即用的云端记忆服务Ready-to-use cloud memory service
适合快速接入、托管运行和跨应用记忆能力。Useful for quick integration, managed runtime, and cross-app memory.
MemOS Lite
专为本地场景的轻量记忆服务Lightweight memory service for local-first scenarios
零云依赖,本地全量运行,面向 Agent 工作流。Zero cloud dependency, fully local runtime, built for agent workflows.
MemOS 正式版开源MemOS Open Source
记忆管理 API 与基础设施Memory APIs and infrastructure
支持深度定制、二次开发和更完整的记忆系统构建。Supports deeper customization, secondary development, and full memory-system construction.
本地优先 · 分层记忆 · 策略归纳 · 技能结晶 · Viewer 可观测 · 宿主数据隔离Local-first · Layered memory · Policy induction · Skill crystallization · Observable Viewer · Per-host isolation