DSH Marketplace

plugin-session-export

whyihaveyou/dsh-suite#plugin-session-export

Export the append-only session log as human-readable Markdown or HTML, grouped by trajectory source.

376HTMLMITSource

Install

Add plugin-session-export to DeepSeek Harness

This plugin lives in a subdirectory of a larger repository, and `dsh plugin add` cannot reach it — it forwards to pnpm, which reads everything after `#` as a git branch or commit. Clone the repository and add the plugin through DSH's plugin panel using a repository source, or ask the author to publish it to npm.

Due diligence

Before you install plugin-session-export

  • Source of record: whyihaveyou/dsh-suite — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface, requires credentials. Read the source before granting these.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — Export append-only session logs to readable Markdown or HTML, grouped by trajectory source.

Who it is for — Users who handle append-only session logs in DeepSeek Harness are suitable for installing this plugin. Users who do not use DeepSeek Harness do not need to install it.

Watch out — Sandbox testing has not been performed yet, no obvious issues found. It requires providing an API key or token and will execute shell commands.

The verdict — If I need to convert append-only session logs to readable format, I would install it.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What plugin-session-export does

Layered logs split by source and resolve into Markdown and HTML document forms.

plugin-session-export is a DeepSeek Harness plugin that exports the append-only session log as readable Markdown or HTML, grouped by trajectory source.

DeepSeek Harness supplies the session data, while plugin-session-export turns that log into an organised presentation. The catalogue identifies four source groups: system prompts, chains of thought, tool calls and subagents. The available output formats are Markdown and HTML. The supplied README does not name a command, configuration key, file path or hook used to perform the export, so the exact trigger and destination cannot be determined from the documented material.

plugin-session-export is intended for developers who need a human-readable record of session activity, particularly when different trajectory sources must remain distinguishable. It is a poor choice when a different output format, an explicitly documented export command, or a documented storage destination is required. The catalogue does not describe filtering, redaction, access controls or incremental export behaviour.

The directory marks plugin-session-export with a terminal-surface risk flag and a credentials requirement. Installing it therefore means allowing code in the agent environment to reach the terminal surface and operate with the credentials available to that environment. The README does not explain which credentials are used or what terminal operations occur, so those details should be verified in the source before installation.

plugin-session-export documentation

What plugin-session-export documents

The repository catalogue describes plugin-session-export as a DeepSeek Harness session plugin. Its documented purpose is to export the append-only session log in two human-readable formats: Markdown and HTML. The exported material is grouped by trajectory source rather than presented as one undifferentiated log.

The catalogue names these source groups:

  • system prompts
  • chains of thought
  • tool calls
  • subagents

Output and grouping

DeepSeek Harness provides the session context that this plugin exports. The available description establishes that the source is an append-only session log, but it does not specify whether the plugin reads a file, an API, an event stream, or another DeepSeek Harness interface. It also does not document whether export is a one-off operation, an automatic action, or a live view.

Grouping by trajectory source is the only documented rendering rule. No options for ordering, filtering, redaction, formatting, or selecting individual sources are described.

Configuring plugin-session-export

The supplied README does not document configuration keys, default values, environment variables, output paths, or profile-specific settings for plugin-session-export. It likewise does not state which DeepSeek Harness hook loads or invokes the plugin. No version requirement or supported-platform constraint is given.

Commands and access

No command name, arguments, flags, or one-line installation command is documented for plugin-session-export. The directory metadata marks the plugin with terminal surface and requires credentials risk flags. This indicates that installation should be reviewed as code running with the agent's available permissions, but the README does not identify the credentials involved or the terminal operations performed.

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

Same category

Alternatives to plugin-session-export

Rewind conversation and workspace state, powered by a persistent Change Ledger.

Installed cleanly when we ran it

npm packageJavaScript4d ago

AI review

dsh-turn-rewind

What it is — dsh-turn-rewind adds a rewind icon after each user message in DeepSeek Harness, supporting project file recovery via the Change Ledger with optional restart from the restored request.

Who it is for — When using DeepSeek Harness with the Agent service in a web profile for iterative project development, this plugin captures checkpoints to support message-anchored recovery. If the profile does not provide the DSH Agent service, the plugin is not needed, as checkpoints are not captured there.

Watch out — Sandbox testing passed. The plugin was installed in a fresh profile and registered by Harness. No obvious issues were found.

The verdict — I would install it in workflows requiring message-based file recovery, because the Change Ledger maintains durable restore points with human approval before any change.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Details
57

Import full-fidelity chat histories from 13 coding agents (Claude Code, Codex, ChatGPT, Cursor, Gemini, opencode, and more) as resumable DeepSeek Harness sessions, with reverse export back to Claude Code.

Installed cleanly when we ran it

npm packageJavaScript4d ago

AI review

dsh-chat-import

What it is — Import full-fidelity chat histories from 14 coding agents into DeepSeek Harness as resumable sessions, with reverse export back to Claude Code.

Who it is for — If you are working in a Claude Code development environment and need to import previous conversation histories into DeepSeek Harness to continue chatting, install this plugin. If you only work in a single coding agent environment without involving import of histories from other agents, you can skip this plugin.

Watch out — One-line npm install passes sandbox test in a new profile and registers into harness. It executes shell commands. No obvious issues found.

The verdict — If you need to import histories from Claude Code and export back for continued work, install it for the full fidelity and matrix interop.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

DSH plugin: Claude-style Chinese risk control & conversation autonomy for DeepSeek Harness web

Installed cleanly when we ran it

GitHub sourceJavaScript5d ago

AI review

dsh-claude-ux

What it is — dsh-claude-ux provides Claude-style regional risk control and conversation autonomy for DeepSeek Harness web profile.

Who it is for — When processing messages from specific regional users in DeepSeek Harness web profile, users requiring autonomous dialogue termination are suitable for this plugin. If your interactions are primarily with English-speaking users without regional concerns, the reverse risk control feature may not align with your needs.

Watch out — Manual approval of the build script is required when installing from source. Sandbox testing passed, with successful registration in a new profile. No obvious issues detected.

The verdict — I would install it if autonomous dialogue control is needed, as it enables local judgment with privacy protection by default.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source
30

Cross-instance message and event handoff between DSH instances via an interconnect server.

Installed cleanly when we ran it

npm packageTypeScript4d ago

AI review

dsh-interconnect

What it is — DSH instances exchange messages and events via an interconnect server.

Who it is for — When cross-instance message and event pushing is needed. If only a single DSH instance is used, this plugin can be skipped.

Watch out — Sandbox test passes with installation in a new profile and registration into the profile. Static check shows it will execute shell commands.

The verdict — I would install it since it allows bidirectional event pushing between DSH instances, although wakeup is disabled by default.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

Branch-based message editing, reroll, retry, and a version timeline.

Installed cleanly when we ran it

npm packageTypeScript5d ago

AI review

dsh-message-edit

What it is — dsh-message-edit is a DeepSeek Harness plugin that provides branch-based message editing, reroll, retry, and version timeline management.

Who it is for — It is suitable for users who need to edit committed user messages, assistant reasoning blocks, or replies in DeepSeek Harness conversations and retry specific historical turns. Users who do not require version branching or timeline management in their conversation workflows can skip it.

Watch out — It passed sandbox testing by being registered in a new profile. Static checks indicate it executes shell commands. No obvious runtime issues were found.

The verdict — I would install it because it allows switching session versions without modifying historical events, which is useful for controlling multi-turn conversation flows precisely.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

DeepSeek Harness account monitoring, usage accounting, completion alerts, official recharge, flexible layout, and agent-assisted session controls. / 账户监控、提醒、充值与会话控制中心

Installed cleanly when we ran it

npm packageJavaScript4d ago

AI review

deepseek-harness-control-center

What it is — DeepSeek Harness Control Center is a sidebar tool for account monitoring, usage accounting, completion alerts, and official recharge.

Who it is for — It suits users who need to check official balance and session costs in real time beside the DSH composer. Users who prefer full-page dashboards rather than compact sidebars may skip it.

Watch out — Sandbox test passed with installation in a new profile and successful registration to harness. Installation via npm requires no extra configuration. No obvious compatibility issues found.

The verdict — I would install it because it centralizes monitoring signals in the composer.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
Source