Preface¶

If you have already accumulated configuration signals and session history in Codex, Claude Code, Qoder, or OpenCode, and are ready to continue working in DeepSeek Harness, manual copying often carries several risks: you might accidentally modify source files, bring credentials into the new environment, or automatically apply MCP configurations without review.

Here is DeepSeek Harness External Migration. It is a DSH plugin designed to migrate configuration signals and session history from the aforementioned sources into DeepSeek Harness, while preserving a human confirmation step before import.

What This Is¶

DeepSeek Harness External Migration is positioned as an external agent history migration tool. It provides three model-side tools:

• external_migration_scan: Read-only inventory of sources; does not return session content, credentials, or write anything.
• external_migration_preview: Read-only parsing, providing a brief session preview.
• external_migration_import: Requires confirm=true before writing native Harness sessions and exports a reviewable configuration package.

This plugin does not modify source files or copy credentials. MCP secrets are replaced with environment variable references, and the generated MCP configurations are not automatically applied.

The repository is licensed under MIT.

Installation and Enablement¶

Before installation, ensure the environment meets the requirements: DeepSeek Harness 0.1.0-rc.5 or a compatible later version, and Node.js 22.19+ or 24+.

Install using a local package:

dsh plugin --profile web add /absolute/path/deepseek-harness-external-migration-0.1.0.tgz

This package declares dsh.bundle.patch, so dsh plugin will activate it as a profile layer. Restart the corresponding profile after installation.

If you want to verify the plugin package from source, you can run:

npm install
npm test
npm pack --dry-run

Typical Usage¶

After the steps above, process the target sources in order within Harness:

1. First, call external_migration_scan to confirm which migration sources are available.
2. Next, call external_migration_preview to view brief parsing results.
3. Finally, call external_migration_import with confirm=true to complete the write.

By default, the reviewable configuration package is written to:

$DSH_HOME/migrations/external-agents/

Before importing, inspect the configuration package in this directory, then decide whether to use the relevant configurations in Harness.

Applicable Scenarios and Notes¶

This plugin is suitable for users who need to migrate configuration signals and session history from existing agent tools into DeepSeek Harness, particularly for scenarios where they want a “scan first, preview next, and explicitly confirm import last” approach.

A few things to note:

• This plugin is activated via dsh plugin and runs with the permissions of the current DSH process; inspect the source code, license, and the migration sources before installation.
• external_migration_import writes to native Harness sessions and exports a configuration package, so confirm=true must be explicitly passed.
• The generated MCP configurations are exported only for review and are not automatically applied.
• Credentials are not copied; MCP secrets are replaced with environment variable references.
• Source files are not modified.

Conclusion¶

The value of DeepSeek Harness External Migration lies in breaking down “cross-tool migration” into three steps: read-only inventory, read-only preview, and explicit import, reducing the risks of accidentally modifying source files, credential sprawl, and automatic configuration application.

Repository address:

https://github.com/buguoshixc/deepseek-harness-external-migration