How dsh-chat-import works
DeepSeek Harness loads imported conversations as new sessions rather than modifying the source history or the DeepSeek Harness engine. Source files are read-only. Sessions are grouped into the workspace associated with their source cwd; the plugin consults ~/.claude.json first, applies greedy slug decoding for Reasonix, and uses a home-directory sandbox guard. If the recorded path is not available locally, the source file's directory is used.
dsh-chat-import commands and operations
The README names one importer per supported source, including import_chatgpt({ branch: 'all' }) for restoring every ChatGPT root-to-leaf branch. Other documented operations include export_claude, sync_to_claude, export_codex, export_kimi, export_bundle, restore_bundle, import_agents, import_mcp and import_settings. Slash commands include /resume-claude, /resume-codex, /mcp-status, /settings-suggest and /attach-workspaces.
export_claude produces a Claude Code JSONL transcript that Claude Code can load with --resume. sync_to_claude appends new complete turns without silently overwriting the target. Bundle export and restore use SHA-256 fingerprints and report when a cwd cannot be reached on the destination machine.
dsh-chat-import data handling
Imports retain tool calls and results, thinking blocks, titles, models and timestamps where the source records them. Tool messages from ChatGPT become tool/call and tool/result; opencode names are mapped to DeepSeek Harness equivalents such as websearch to web_search, question to ask_user_question and task to subagent. Export results include a degradations list for orphan results, skipped injections and skipped attachments.
import_agents converts agents, prompts, skills, instructions and config references from pi, opencode, Claude and Codex into persistent DeepSeek Harness skills. import_mcp reads Claude and Codex MCP servers and generates a reviewable DSH MCP client YAML snippet. import_settings reads Claude settings.json and Codex config.toml to produce migration suggestions.
dsh-chat-import requirements and limits
The repository advertises Node.js >= 22.13. The README does not define plugin-specific configuration keys or environment variables. Fidelity depends on what each source format records, and exports can therefore omit source concepts reported through degradations.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub