Introduction¶
DeepSeek Harness (DSH) uses a plugin-based architecture that allows developers to extend functionality through plugins. In practice, there are scenarios where specific logic needs to be executed without network access or under network request restrictions. This article introduces the dsh-plutonium plugin, which addresses the need to extend functionality in network-independent environments.
Plugin Overview¶
dsh-plutonium is a plugin integrated through the cordis.patch.yml patch mechanism. It is maintained by uckkk and is positioned as a model inference plugin. Its key characteristics are that it is fully implemented in pure Node and does not rely on any network requests.
Core Features¶
- Pure Node implementation: It does not depend on an external runtime environment and runs directly on Node.js.
- No network dependency: It does not initiate any network requests during execution.
- Patch mechanism integration: It uses the
cordis.patch.ymlconfiguration file to inject code into the Cordis core.
Installation and Enablement¶
Run the following command in a terminal to install it:
dsh plugin add github:uckkk/dsh-plutonium
Before installation, ensure the following dependency requirements are met:
* The version of @deepseek-ai/cordis must be ^4.0.1 or higher
* The version of @deepseek-ai/dsh-tools must be 0.1.0-rc.6 or higher
Typical Usage¶
The plugin is integrated through the cordis.patch.yml patch file. After installation, the plugin runs with the permissions of the current DSH process. Due to its network-independent nature, it is suitable for deployment in isolated or offline environments.
Applicable Scenarios and Notes¶
- Applicable scenarios: Model inference tasks that require offline execution, or scenarios with strict network restrictions.
- Permission note: The plugin runs with the permissions of the current DSH process. Please review the source code and license (MIT) before installation.
Summary¶
dsh-plutonium provides a way to extend DeepSeek Harness logic in network-independent environments. For more details, refer to the plugin directory page or the GitHub repository.