Show and tell: qclaw2octop — replicate a complete QClaw/OpenClaw agent workspace in Octop

[ltwtl]

Hi Octop team and community,

I'd like to share qclaw2octop, an open-source migration kit I built and validated while moving a long-running personal AI assistant from QClaw to Octop:

https://github.com/ltwtl/qclaw2octop

The problem. For many users, a personal agent is a long-lived asset rather than a disposable chat. Its value lives in the accumulated configuration, memory, skills, conversation history, and the way conversations are organized over time. Switching runtimes usually means rebuilding that asset by hand — repeated work that is easy to get wrong.

The approach. qclaw2octop treats migration as a full workspace replication task, not a partial export:

• Agent definition: identity, behavior, user profile, tool rules, and related Markdown configuration (SOUL.md, USER.md, TOOLS.md, etc.) are carried into the Octop expert workspace.
• Long-term memory: memory and continuity files are migrated, so the agent retains the facts, preferences, and ongoing context it accumulated before the move.
• Custom skills: skill packages are copied and wired in, so the agent keeps its original capabilities rather than losing them at the boundary.
• Conversation history: exported QClaw conversations are written into Octop session storage instead of being archived as unread backups.
• Session windows: QClaw sessions.json is used to rebuild the sidebar entries, preserving the user's original conversation organization rather than flattening everything into one list.

Validated result. In a real migration, 90 exported conversation records were restored into 19 sidebar windows matching the source workspace. After migration, the same window could answer questions that depend on historical records — for example, “When was the most recent checkup?” — using the restored memory and history. In other words, the agent was not re-created; it was continued.

Who it is for. Non-technical users and builders who want to move an existing QClaw/OpenClaw-style assistant into Octop without repeating setup work, and without losing the structure they already rely on.

Scope and boundaries. The kit fully restores the visible workspace: agent configuration, memory, skills, conversation history, and session entries. It does not carry over QClaw's internal checkpoint state; the migrated agent reconstructs its working context from the restored memory and history. Scheduled jobs are intentionally left for explicit user confirmation before being recreated.

The repository includes a parameterizable migration script, an anonymized operations manual, and diagrams of the migration pipeline and concept mapping. Feedback, issues, and pull requests are welcome.

中文摘要：qclaw2octop 是一个开源迁移工具，解决的是“换一个 Agent 运行时，就要把长期积累的助手资产手工重建一遍”的问题。它把迁移定义为完整工作区复刻：Agent 的设定与行为文件、长期记忆、自定义技能、会话历史，以及侧边栏会话窗口的组织结构，都一起迁入 Octop。实测中，90 条导出会话被恢复为 19 个与源工作区一致的会话窗口；迁移后，在同一个窗口里提问依赖历史记录的问题，Agent 能基于恢复的记忆和历史直接回答——助手不是被重建，而是被延续。工具面向不想重复搭建的普通用户和开发者；仓库内含参数化迁移脚本、匿名化操作手册，以及迁移流程与概念映射图。已知边界：可见工作区完整恢复，但 QClaw 内部 checkpoint 状态不延续，定时任务需确认后手动重建。

Keywords: QClaw, OpenClaw, Octop, Tencent Cloud Octop, AI agent migration, personal AI assistant, agent workspace replication, agent continuity, session window restore, conversation history restore, long-term memory, agent skills, local-first AI assistant.

[jubaoliang]

Great project, and thank you for the effort! It really helps lower the barrier for users coming from QClaw. One suggestion: it would be awesome if you could expand the migration coverage to include more platforms such as OpenClaw, Hermes, and others. That would make it a more comprehensive migration toolkit for the community.

[jubaoliang]

PS: If you'd like to connect with the core team or need any guidance on the migration roadmap, feel free to reach out via the WeCom support group — scan the QR code in our README under the "Community → WeCom Customer Group (CN)" section. The admins are happy to help!

[ltwtl]

我的意思我自己做另一个迁移的方案，分享出来供需要的使用。