Introduction

In the DSH plugin extension model, community plugins can supplement local workflows. @danglong0313/dsh-history-sync solves a relatively specific problem: it imports the history tasks already occurring on local Codex and Claude Code into DeepSeek Harness (DSH) in the form of a read-only mirror.

It is not a bidirectional sync tool, nor is it responsible for restoring Codex or Claude’s model, tool processes, approvals, sandboxes, or runtime status from DSH.

What is it

  • Plugin Name: @danglong0313/dsh-history-sync
  • Publisher: danglong0313
  • License: MIT
  • Positioning: To import local Codex and Claude Code user/assistant conversations one-way, read-only mirror to DSH.
  • Boundaries: Does not write back to the source; is not bidirectional sync; cannot losslessly restore upstream runtime status.

Core Capabilities

The capabilities listed below are verified by the plugin:

  1. One-way read-only import of Codex and Claude Code user/assistant conversations, without writing back to the source.

  2. Adopt a conservative strategy by default: preview by default, auto-sync disabled by default, and only scan the last 30 days by default.

  3. Can be directly configured and enabled for auto-sync in Settings → Plugins → Plugin Config → History Sync.

  4. Automatically create or reuse a DSH Workspace based on the original working directory and group it in the left sidebar project list.

  5. Uses content fingerprints, append watermarks, and generation to handle duplicate syncs, incremental appends, and upstream history rewrites.

  6. Filters system/developer, reasoning, tool calls, approvals, command outputs, and Claude control tags to avoid treating protocol messages as real chat.

Installation and Enablement

Taking the desktop profile as an example, first execute the installation command, then check the current profile’s configuration status:

dsh plugin --profile desktop add @danglong0313/dsh-history-sync@0.2.0
dsh --profile desktop --dump-config

The first command installs the plugin to the desktop profile, and the second command is used to view the configuration status of that profile.

After installation, start DSH and navigate to:

Settings → Plugins → Plugin Config → History Sync

You can configure the plugin directly here and enable auto-sync if needed. Since the plugin does not auto-sync by default, it is recommended to complete a preview first, confirm the import scope, and then enable actual import or auto-sync.

Typical Usage

Execute a preview in any DSH task:

/history-sync preview

After confirming the scope, enable “Allow Actual Import” in the History Sync config card, then execute:

/history-sync run

Unparameterized /history-sync is equivalent to preview.

If you want the plugin to automatically handle new history later, you can enable auto-sync in the History Sync config card. Auto-sync is disabled by default.

Scenarios and Notes

This plugin is suitable for developers who want to view existing Codex or Claude Code conversation history in DSH. Its core limitation is: this is a history mirror, not a recoverable upstream runtime environment.

Before enabling, pay attention to the following points:

  • Importing will create a second copy of history in DSH persistence.
  • Original tasks may contain source code, command outputs, .env content, credentials, or other sensitive information.
  • Deleting Codex/Claude original tasks will not automatically delete the DSH copy, and vice versa.
  • In v1, readOnly must be true; previewOnly being true rejects actual import.
  • DSH is still in pre-release, and Session format is not guaranteed to be compatible across pre-release versions; verified DSH is 0.1.0-rc.6.
  • The plugin runs with the permissions of the current dsh process; you should check the source code, dependencies, and MIT license before installing.

Conclusion

The value of @danglong0313/dsh-history-sync lies in: importing local Codex and Claude Code historical conversations into DSH one-way under the premise of default preview, default read-only, and default no auto-sync, and displaying them grouped by original working directory in the project sidebar.

  • GitHub: dsh-history-sync
  • Directory: Verified materials do not provide an available directory page; it is recommended to refer to the GitHub repository.