DeepSeek Harness (DSH) follows the “everything is a plugin” architectural philosophy. When deploying DSH locally or on a server, outgoing requests usually carry additional correlation metadata, such as Harness user ID, session identifier, and compression flag. dsh-request-privacy aims to reduce this metadata, overrides the native DeepSeek provider endpoint, and provides a way to streamline request headers without changing core business logic.

Plugin Overview

This plugin is maintained by jhckevin under the MIT license. It only handles incoming DeepSeek chat requests and does not involve file uploads, telemetry, or other providers.

Core Features

  1. Reduces the additional correlation metadata carried by chat requests.
  2. Uses the private-client request identity.
  3. Does not attach the Harness user, session, and compression flag.
  4. Provides a WebUI setting to streamline request headers.
  5. Overrides the native deepseek-official endpoint.
  6. Supports compatibility with the legacy deepseek-private endpoint.

Installation and Configuration

1. Confirm the Environment

Run the following command to confirm whether the DeepSeek Harness version is 0.1.2-rc.1:

dsh --version

2. Install the Plugin

Run the installation command in the same terminal where DSH is running. This command installs version 0.4.1-rc.1 from the official npm registry:

dsh plugin --profile web add dsh-request-privacy@0.4.1-rc.1 --registry=https://registry.npmjs.org/ --ignore-scripts

3. Start the Service

After installation, restart DSH to apply the changes:

dsh --profile web

4. Enable the Setting

  1. Open the WebUI address printed in the terminal.
  2. Go to Settings in the lower-left corner.
  3. Find Request Privacy.
  4. Toggle the Slim Request Headers switch and confirm that “Settings saved” is displayed.

Notes

This plugin cannot provide an absolute privacy guarantee. Please note the following limitations:
* Unofficial training toggle: This is not an official “do not use for training” toggle and cannot guarantee that the service provider will not store, filter, or train on the data.
* Data transmission: The API key, chat content, and tool descriptions are still sent.
* Scope: File uploads, telemetry, and other providers are out of scope.
* Mechanism: Installation uses the official DSH profile plugin mechanism and does not modify host files.

Ecosystem Context

DeepSeek Harness aims to provide developers with flexible model access capabilities. The plugin directory is independently maintained by the community and is not subordinate to DeepSeek’s official team or High-Flyer Quant. The plugin introduced in this article follows this ecosystem convention and helps reduce information leakage in specific scenarios by modifying request metadata.