GLFzr/dsh-file-upload

This is a natively-developed plugin built exclusively for DeepSeek Harness (DSH), that extends the default Web GUI attachment system which originally only handled image uploads to support any file type. It can be installed using DSH’s official CLI plugin command, and will automatically load every time DSH restarts after the initial one-time setup. Users can drag and drop one or multiple files of any format anywhere on the DSH Web UI page, and the plugin saves the file to a local transfer directory, generates a blue uneditable file chip inserted into the input box, so the DSH agent can access and read the file content. On Chromium-based browsers like Google Chrome and Microsoft Edge, the plugin can get the original file path via the browser’s entry API, allowing direct reference of local files without any upload or copying.

The plugin includes a built-in two-level deduplication system that checks for matching file name, size, and last modified date to avoid re-uploading files that have already been added, which saves both time and disk space. The width of each generated file chip automatically adapts to the length of the file name, so the UI stays clean and consistent regardless of how long the file name is. A trash icon for accessing the transfer directory cleaning tool is added to the DSH sidebar above the settings icon; users can view the full file list, delete redundant automatically-named copies, remove files over a specified size, or clear the entire transfer directory. All cleaning actions require explicit user confirmation before execution, to prevent accidental deletion of important files.

The plugin supports a maximum file size of 512MB, splits files into 4MB chunks for upload, and runs full integrity checks on each chunk to ensure no corrupted files are written to local disk. It is released under the open-source MIT license, and all core host-side logic has a full suite of automated unit tests that run via GitHub Actions CI on every push and pull request. The only known limitations are that concurrent uploads of multiple large files can consume a significant amount of host process memory, and direct path references on Chromium only work for actual local files, not virtual or placeholder cloud files. This is not a security flaw, just a current architectural limitation that may be improved in future releases.