Introduction

DeepSeek Harness (DSH) Web provides the official Session Log export feature, primarily used for debugging, recovery, and replaying sessions. However, when you need to read conversation content, perform an AI handoff, or organize documentation, the raw log format is not intuitive enough. The dsh-conversation-exporter plugin adds local export functionality to DSH Web, allowing conversations to be output locally in clean Markdown format.

What It Is

dsh-conversation-exporter is a client-side plugin maintained by liuyuelintop under the MIT License. Its core purpose is to add an export action to the DSH Web interface. It does not depend on any cloud service; it only reads the current session data through the local DSH runtime and generates a Markdown file.

Core Features

  • Full Export: Download the entire current session with one click and generate a readable Markdown file.
  • Selective Export: Supports filtering by “turn.” One exported turn consists of a user message and its corresponding final assistant reply.
  • Local Processing: All processing is completed locally; nothing is uploaded, stored in the cloud, or sent as telemetry.
  • Rich Formatting Preservation: Supports preserving rich Markdown formats such as Mermaid diagrams.

Installation and Enablement

Run the following command in your terminal to add the plugin to the DSH web configuration file:

npx @deepseek-ai/dsh plugin --profile web add dsh-conversation-exporter@latest

After adding it, stop and restart the DSH Web process for the configuration to take effect:

npx @deepseek-ai/dsh web

Typical Usage

  1. Open any session in DSH Web.
  2. Click the Export Chat button in the interface to download the full Markdown file for the current session.
  3. To filter content, click Select turns…. All turns are selected by default.
    • Use Select all or Clear to adjust the selection.
    • Click Export selected turns to export.
  4. The browser will download a file named <session title>--<short session ID>.md, for example Project-Architecture-Guide--2002da4d.md.

In the exported Markdown file:
* The session title is rendered as a level-1 heading (H1).
* Messages are marked with blockquotes; Human and Assistant are marked as > Human and > Assistant, respectively.
* If a message ends in the middle of a code block, the exporter automatically closes that code block.
* Incomplete replies are marked as > Response incomplete..
* Messages containing only images are shown as [Image omitted].

Use Cases and Notes

  • Use Cases: Suitable when you need to organize conversation content into documentation, perform an AI handoff, or keep session archives for non-debugging purposes.
  • Important Notes:
    • Difference from Session Log: The Markdown generated by this plugin focuses on readability and human consumption. It does not include debugging information such as raw events, tool calls, intermediate responses, injected context, or sub-agent logs. This data is available only in the official Session Log.
    • Turn Limitation: Export can only be done by full turn; individual Human or Assistant messages cannot be selected separately.
    • Privacy and Permissions: Export is fully local and has no upload path. The plugin reads session data within the permissions of the current DSH process.
    • Version Compatibility: DSH is currently in developer preview, so the plugin API may change. V0.3 is compatible with @deepseek-ai/dsh@0.1.0-rc.6.

Summary

dsh-conversation-exporter addresses the “readability” issue of DSH sessions in non-debugging scenarios. If you need to convert conversations into Markdown documents, it is a lighter and more intuitive alternative to Session Log.