Introduction

In the plugin workflow of DSH, dynamic Cordis Plugins are often only used in the current session. If you need to take them to another session or environment, manually copying the configuration is inconvenient. zby1211/cordis-transfer-plugin provides entry points for importing and exporting dynamic Cordis Plugins, including two types of operations: the browser Settings panel and model tools.

What is it

cordis-transfer-plugin is a persistent DSH plugin used to import and export dynamic Cordis Plugins. Documentation describes it as a static profile bundle, rather than an in-memory dynamic plugin. It is maintained by zby1211, licensed under MIT, and declares dsh.client.platform as web.

This plugin provides two types of interfaces:

  • The browser Settings panel, used to list, export, and import plugins.
  • Model tools, available for agent invocation, used to list, export, and import dynamic Cordis Plugins for the current session.

Core Features

Verified capabilities include:

  • Import and export dynamic Cordis Plugins.
  • List dynamic plugins in the current session in the browser Settings panel and support multi-selection.
  • Export one or more plugins as .dsh-cordis-bundle.zip.
  • Upload and import plugins from a local .zip file.
  • Provide three model tools:
  • cordis_plugin_list
  • cordis_plugin_bundle_export
  • cordis_plugin_bundle_import

Installation and Activation

When installing this plugin under a web profile, use:

dsh plugin --profile web add cordis-transfer-plugin

This command installs cordis-transfer-plugin. After installation, dsh web needs to be restarted.

If handling it in a regular Node.js project, you can also execute:

npm install cordis-transfer-plugin

This plugin declares the following peerDependencies; you can confirm that your current environment meets these dependencies before installing:

{
  "peerDependencies": {
    "@deepseek-ai/dsh-tools": ">=0.1.0-rc.6",
    "@deepseek-ai/dsh-typert-protocol": ">=0.1.0-rc.6",
    "fflate": "^0.8.3"
  }
}

Typical Usage

The browser operation path is:

Settings → Plugins → Import / Export

When exporting a plugin package:

  1. Select one or more dynamic Cordis Plugins from the list.
  2. Execute export.
  3. Download .dsh-cordis-bundle.zip.

When importing a plugin package:

  1. Select a local .zip file.
  2. Upload the file to the Host.
  3. Execute import.

If operating via model tools:

  • cordis_plugin_list: List dynamic Cordis Plugins in the current session.
  • cordis_plugin_bundle_export: Export one or more plugins as a zip bundle.
  • cordis_plugin_bundle_import: Import plugins from a zip bundle.

Use Cases and Precautions

This plugin is suitable for scenarios where dynamic Cordis Plugins need to be reused in a web profile, such as exporting plugins from the current session to a local file and then importing them elsewhere.

Precautions before use:

  • The plugin runs with the permissions of the current DSH process.
  • Before installing, check the source code, license, and dependency versions.
  • The license is MIT.
  • The plugin declares dsh.client.platform as web, therefore the installation command uses --profile web.
  • Import and export rely on local .zip files; it is recommended to keep a backup of the plugin packages.

Conclusion

cordis-transfer-plugin puts the listing, exporting, and importing of dynamic Cordis Plugins in the same entry point, reducing the steps of manually moving plugins between sessions. Relevant information can be viewed at the following addresses:

  • Directory page: https://www.skillhub.cn/plugins/zby1211/cordis-transfer-plugin
  • GitHub: https://github.com/zby1211/cordis-transfer-plugin