DSH Conversation Exporter

The problem

DeepSeek Harness preserves a detailed session record for debugging, recovery and replay. That official Session Log includes raw events, tool activity, metadata and attachments, which is the right boundary for a lossless record but not for a transcript someone wants to read, version in Git or hand to another assistant.

DSH Conversation Exporter adds a separate clean-export path for that second job. It is an additive plugin beside DSH's official Session Log; the official function belongs to DSH and is not functionality I built or replaced.

What Export Chat does

Export Chat reads the current session through DSH's local session-query service, keeps the human-authored messages and the final visible assistant answer from each turn, then downloads one Markdown file in the browser. The final usable session title becomes the document heading and filename; message Markdown and Unicode are preserved.

The renderer owns the transcript structure. It labels Human and Assistant sections, closes an otherwise unterminated code fence before the next section, marks an unanswered turn as incomplete and represents an image-only human message with a neutral placeholder instead of dropping the turn.

What selective whole-turn export adds

• —Select turns… lists the conversation chronologically and starts with every whole Human-plus-final-Assistant turn selected.
• —Selection filters the same canonical conversation data used by full export, so request order cannot reorder or duplicate turns and unselected turns never reach the rendered Markdown.
• —The selector receives opaque indexes and previews capped at 180 characters from already-filtered text. Large selections switch from include/exclude arrays to a compact bitset, and the host rejects a stale selection if the turn count changed.
• —Human and Assistant bubbles cannot be selected independently; the unit is deliberately one whole conversation turn.

What exported content deliberately excludes

• —Reasoning blocks, tool calls and results, intermediate assistant responses and streamed chunk fragments.
• —Plugin-injected context, goal and skill-catalog messages, subagent logs and other non-human user-message sources.
• —Runtime metadata such as paths, ids, timestamps and token accounting.
• —Attachments and image data. An image-only human turn remains visible as [Image omitted], but the asset itself is not embedded.

Host and request boundaries

• —The production path reads only the current session identified by DSH's framework-supplied session id and returns filtered data to the same local Web application. The plugin has no upload, cloud-storage, telemetry or analytics path.
• —The plugin owns two exact routes — /api/conversation.export and /api/conversation.turns — and leaves DSH's official /api/session.export route untouched.
• —Both plugin routes accept JSON POST requests only, enforce a 4 KiB body limit, mirror DSH Web's Host, Origin and Fetch Metadata trust checks, return no-store responses and keep operational error details out of browser responses.
• —Turn previews are derived after transcript filtering and contain only an index plus bounded Human and final-Assistant text; raw events, session ids and runtime metadata stay host-side.

How the npm package is verified

• —The package declares the DSH bundle patch, Web client entry, Node.js 20 minimum and the exact source files included in the published payload.
• —npm run verify runs the complete Node test suite, syntax-checks every JavaScript file and finishes with npm pack --dry-run so the installable package contents are checked as part of the same verification command.
• —Golden-file tests cover Markdown, Unicode, injected context, multi-step tool activity, incomplete and image-only turns, malformed fences and selective export. Production-boundary tests cover the local routes, trust checks, bounded bodies and generic failures.

Current limitations

• —Only the current DSH session can be exported, and Markdown is the only output format.
• —Selection is whole-turn only; individual Human or Assistant bubbles are not selectable.
• —Attachments, image data, reasoning, tools, injected context, subagent logs and intermediate responses are intentionally omitted rather than archived elsewhere by the plugin.
• —Message Markdown is preserved except for one deterministic closing fence added when a message would otherwise leave a fenced code block open.
• —Version 0.3 targets @deepseek-ai/dsh@0.1.0-rc.6. DSH is developer-preview software, so later plugin API changes may require an exporter update.