EasyClaw Brain Migration
Use this skill for the files that define the assistant's operating style and continuity, not just runtime config.
Source locations to check
Primary legacy workspace:
Important source files:
- - INLINECODE1
- INLINECODE2
- INLINECODE3
- INLINECODE4
- INLINECODE5
- INLINECODE6
- INLINECODE7
- INLINECODE8
- INLINECODE9
- launchd files under INLINECODE10
Target workspace:
- - current OpenClaw workspace root
Migration policy
Copy directly
These usually copy well when missing in the target workspace:
- - INLINECODE11
- INLINECODE12 contents
- context snapshots / historical notes that are purely informational
Merge carefully
These should be reviewed or staged before replacing active files:
- - INLINECODE13
- INLINECODE14
- INLINECODE15
- INLINECODE16
Why: the new workspace may already contain OpenClaw-native conventions that should not be blown away.
Rebuild, don't blindly copy
These are automation mechanisms, not just text:
- - launchd plists
- helper scripts invoked by launchd
- old context-management wrappers
Translate them into current OpenClaw mechanisms such as:
- - INLINECODE17
- cron jobs
- workspace scripts
- updated notes in
AGENTS.md / INLINECODE19
Workflow
1. Generate a migration report
Run:
CODEBLOCK0
This reports:
- - what source files exist
- what target files exist
- which files are safe to import directly
- which should be staged for review
- legacy automations that need rebuilding
2. Stage legacy brain files safely
Run:
CODEBLOCK1
This copies legacy brain files into imports/easyclaw/ inside the current workspace without overwriting active files.
Use staging first when you want a safe reviewable landing zone.
3. Import memory into active workspace
Run:
CODEBLOCK2
This:
- - backs up current target files if needed
- copies
MEMORY.md if missing - copies legacy
memory/ files that do not already exist - leaves active
AGENTS.md, SOUL.md, and HEARTBEAT.md untouched
4. Merge principles manually or with explicit review
After staging, read the staged files and selectively merge:
- - stable operating rules from INLINECODE26
- persona/principles from
SOUL.md and INLINECODE28 - heartbeat tasks that still make sense
- context-management notes from INLINECODE29
Do not auto-enable old schedules unless the user wants them restored.
Notes
- - Treat old memory and prompts as sensitive workspace data.
- Prefer additive migration over destructive replacement.
- For heartbeat and scheduling logic, surface what existed and ask whether to rebuild it as cron/heartbeat behavior.
EasyClaw 大脑迁移
使用此技能处理定义助手操作风格和连续性的文件，而不仅仅是运行时配置。
需检查的源位置
主要旧工作区：
重要源文件：
- - AGENTS.md
- SOUL.md
- CORE-PRINCIPLE.md
- MEMORY.md
- USER.md
- HEARTBEAT.md
- memory/
- docs/context-management.md
- scripts/load_context.sh
- ~/Library/LaunchAgents/com.easyclaw.*.plist 下的 launchd 文件
目标工作区：
迁移策略
直接复制
以下文件在目标工作区缺失时通常可直接复制：
- - MEMORY.md
- memory/ 内容
- 纯信息性的上下文快照/历史记录
谨慎合并
以下文件在替换活动文件前应进行审查或暂存：
- - AGENTS.md
- SOUL.md
- HEARTBEAT.md
- USER.md
原因：新工作区可能已包含不应被覆盖的 OpenClaw 原生约定。
重建而非盲目复制
以下为自动化机制，不仅仅是文本：
- - launchd plist 文件
- launchd 调用的辅助脚本
- 旧的上下文管理包装器
将其转换为当前 OpenClaw 机制，例如：
- - HEARTBEAT.md
- cron 任务
- 工作区脚本
- AGENTS.md / TOOLS.md 中的更新记录
工作流程
1. 生成迁移报告
运行：
bash
python3 scripts/reporteasyclawbrain.py
该命令将报告：
- - 存在哪些源文件
- 存在哪些目标文件
- 哪些文件可直接安全导入
- 哪些应暂存待审
- 需要重建的旧自动化机制
2. 安全暂存旧大脑文件
运行：
bash
python3 scripts/stageeasyclawbrain.py
该命令将旧大脑文件复制到当前工作区的 imports/easyclaw/ 目录中，不会覆盖活动文件。
当需要安全可审查的暂存区域时，请先使用暂存功能。
3. 将记忆导入活动工作区
运行：
bash
python3 scripts/stageeasyclawbrain.py --import-memory
该命令将：
- - 必要时备份当前目标文件
- 如果 MEMORY.md 缺失则复制
- 复制不存在的旧 memory/ 文件
- 不触碰活动的 AGENTS.md、SOUL.md 和 HEARTBEAT.md
4. 手动或通过明确审查合并原则
暂存后，阅读暂存文件并选择性合并：
- - AGENTS.md 中的稳定操作规则
- SOUL.md 和 CORE-PRINCIPLE.md 中的角色/原则
- 仍有意义的节拍任务
- docs/context-management.md 中的上下文管理记录
除非用户希望恢复旧调度，否则不要自动启用旧调度。
注意事项
- - 将旧记忆和提示视为敏感工作区数据。
- 优先采用增量迁移而非破坏性替换。
- 对于节拍和调度逻辑，展示已有内容并询问是否将其重建为 cron/节拍行为。
