AI Agent Hub
Back to plugins
🧰

dsh-plugin-claude-import

Web Tools Updated 2026.08.15

Run the following command in DeepSeek Harness:

dsh plugin install changhang155/dsh-plugin-claude-import

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

Run dsh plugin install changhang155/dsh-plugin-claude-import in your terminal (source: https://github.com/changhang155/dsh-plugin-claude-import ) and restart DSH Web to activate the plugin.

About this plugin

You just finished a dev sprint in Claude Code and want to pick up where you left off in DeepSeek Harness. Dumping raw .jsonl events into a new session is neither practical nor useful — what you need is a distilled, ready-to-continue context. dsh-plugin-claude-import tackles exactly that: instead of replaying raw events, it extracts the auto-summary chain, the last task, the file footprint, and the tail state, then assembles them into a context block you can actually build on.

The plugin exposes two agent tools and a Web GUI shortcut. Use claude_session_list to browse every Claude session under a project directory with title, mtime, size, and message stats. Use claude_session_import to pull any session in as a paste-ready seed context block or a full Markdown continuation document; with createSession set, it spins up a new DSH session in the matching project folder and delivers the context as the first message. On the Web side, a button in the conversation header lets you type a session ID and go — the plugin handles creation, opening, and seeding in one step.

Built for developers who work across both Claude Code and DeepSeek Harness: when you switch workflows or want a historical Claude session to seed a new project, this plugin collapses hours of manual context wrangling into a single conversation. The import logic is heuristic (pure Node, zero external dependencies) and handles title extraction, file-change tracking, and local-command-mode sessions with targeted detection, but a quick human review of the seeded context before diving in is still advisable.

Use Cases

  • Switching from Claude Code to DeepSeek Harness mid-task and recovering context instantly
  • Seeding a new project from a past Claude session instead of re-briefing from scratch
  • Benchmarking both tools against the same task context for quality comparison

Best For

  • Developers actively working across both Claude Code and DeepSeek Harness
  • Engineers who switch between AI coding tools as part of their daily workflow
  • Solo developers who want to convert past chats into reusable working context