[Idea] Import sessions & agents from pi / opencode / codex / claude-code into dsh — worth making this official?

[Chang-Tong]

Hi maintainers & community,

I've been using dsh alongside pi (pi-coding-agent), opencode, codex and claude-code, and built a plugin that imports their sessions, chat history, and agents into dsh. It works well for my workflow, and I'd like to ask whether this is a feature the project wants to own — as a first-party plugin or built-in — or whether it's better left as a community extension.

What it does

• Session import — parses pi JSONL session files, the opencode SQLite store, codex rollout JSONL, and claude-code JSONL into real dsh sessions, written in the exact on-disk format the dsh JSONL persistence backend uses (checksummed zstd frames, project-dir encoding). Round-trip verified with the backend's own list / load / prepare.
• Resumable — imported sessions appear in the dsh session list and can be resumed: the model continues with the complete history (text, reasoning, tool calls) as context. Tool calls become tool-call content blocks paired with tool/call + placeholder tool/result events so OpenAI-compatible APIs accept resumed requests (no orphaned tool_calls).
• Agents → skills — pi agents / mode prompts and opencode agents become discoverable dsh skills under $DSH_AGENTS_HOME/skills, with metadata.source / metadata.kind in the frontmatter.
• Workspace placement — imported sessions attach to a workspace matching their original cwd (created on demand) instead of piling up ungrouped.
• Plugin UX — slash commands (/import-pi, /import-opencode, /import-agents, /import-all, /attach-workspaces), a session-start migration prompt (asks once per project, remembered in $DSH_HOME state), and a one-click Sync button in the composer tool row.
• Idempotent, zero runtime deps — stable ids (pi-<uuid>, oc-<id>, codex-<id>, claude-<id>); re-imports skip what already exists. Only Node built-ins (node:zlib zstd, node:sqlite) + dsh platform modules.

Where it lives

• Repo: https://github.com/Chang-Tong/dsh-import-agents (MIT)
• npm: pnpm add dsh-import-agents (v0.2.1)
• Enable: append one row to cordis.patch.yml, restart dsh web.

The question

Is cross-tool migration in scope for dsh? Specifically:

1. Would you like this as a first-party plugin / built-in, or is community extension the right home?
2. What would it take to be acceptable upstream — storage-contract stability, tests against the real backend (already have verify.mts + plugin-test.mts), docs, naming?
3. Which sources matter most to you (pi / opencode / codex / claude-code)?

I'm happy to contribute the code directly if there's interest. 🙏

[Chang-Tong]

中文摘要：我在做一个把 pi / opencode / codex / claude-code 的会话、聊天记录和 agent 导入 dsh 的插件（dsh-import-agents，MIT，已发 npm）。导入后会话变成真正的 dsh 会话（走 dsh 自己的 JSONL/zstd 存储格式），可以直接续聊，agent/模式提示词转成 dsh skills，还带一键 Sync 按钮和斜杠命令。这篇帖子是想问：这类跨工具迁移功能，主仓库要不要收编成官方插件/内置功能？还是留在社区扩展？欢迎维护者和社区给意见。插件展示见 #1362 🙏

[sjh9714]

会话之外的那半（配置、技能、MCP、hooks、子代理、权限规则），Claude Code 这个来源已经能搬了，dsh-movein 一条命令，默认先出预演清单。会话历史那半 dsh-chat-import 做得更全（13 个来源）。

codex / opencode / pi 作为来源，正好是我们排的下一步（sjh9714/dsh-movein#3 ）。搬运的部分（符号链接技能、生成 patch 行、manifest）是来源无关的，缺的只是各家的扫描器。如果你在用其中一个，能不能在 issue 里说下你的配置里都有什么（技能格式、MCP 配置文件位置），这决定扫描器的实现顺序。

[Chang-Tong]

一起加油吧 哥们儿 可以聊聊