AI Agent Hub
Back to plugins
🧠

dsh-migrate

Memory Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install kkkkkkkkki/dsh-migrate

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install kkkkkkkkki/dsh-migrate in your terminal to install; the source code is available at https://github.com/kkkkkkkkki/dsh-migrate .

About this plugin

Switching AI coding agents rarely fails because of the new tool—it fails because of everything the old tool left behind: months of conversation transcripts, memory files, tool-call logs scattered across a dozen config directories. dsh-migrate is built to close that gap. It reads the on-disk artifacts left by Claude Code, Codex CLI, Gemini CLI, Cursor, Kimi CLI, ChatGPT Web exports, Cline / Roo Code, OpenCode, Aider, Hermes Agent, and OpenClaw, then writes them as native DeepSeek Harness JSONL session logs. Imported sessions appear in the sidebar grouped by project, render their full event stream in the Trajectory view, and can be fork-style resumed as if DSH had recorded them from the start.

Two workflows are provided: a /migrate slash command that runs inside DSH itself, and a standalone CLI that scans the whole machine, previews everything with a dry run, and only writes after you confirm. Every adapter is intentionally tolerant—malformed lines and unknown row types are skipped rather than fatal, missing fields degrade gracefully (an unknown model is still imported, an unknown working directory lands in a _no-cwd project), and source agent directories are always opened read-only. Writes use append-only semantics with fresh session IDs, so an import can never shadow a live session, and original timestamps and provider / model metadata are preserved for provenance.

If you are moving to DeepSeek Harness and do not want to start from a blank context, dsh-migrate is the bridge. One scan collects your conversation history and memory notes from up to eleven upstream agents and turns them into a searchable, inspectable, resumable archive that plugs directly into the DSH session store.

Use Cases

  • Moving from Claude Code or Codex CLI to DeepSeek Harness while keeping all prior conversation context and tool-call records intact.
  • A team using multiple agents needs a unified view of every historical session in one place.
  • Revisiting reasoning chains and tool-call details from other agents through the Trajectory view.

Best For

  • Developers migrating from other AI coding assistants to DeepSeek Harness.
  • Engineers who manage cross-agent session history and memory files in one place.
  • AI workflow users who value context continuity and provenance.