dsh-models-plus: Local Route Proxy and Model Settings Enhancements for DeepSeek Harness

What Does It Do?

DSH Models Plus is a DSH plugin for DeepSeek Harness that enhances the Settings → Models page with a loopback local route proxy and a smoother model-management UI. It solves two problems: external clients cannot easily reach the models already configured in Harness, and model-list extensions often break or blank out after version updates. The plugin opens a configurable local port and bridges OpenAI and Anthropic protocol requests to the providers you have enabled in Harness, without replacing any official package. It is maintained by gongstudent under the MIT license and was last updated on 2026-09-30.

Core Features

• Loopback local route proxy: listens on port 8317 by default and bidirectionally translates OpenAI chat/completions and responses calls plus Anthropic messages calls to the active DSH providers.
• Health check and route discovery: exposes a health endpoint that reports available routes and server status so external clients can verify connectivity.
• Dynamic port configuration: toggle the proxy on or off and set a custom port (1024–65535) directly from the Models settings page, with instant hot reload.
• Zero-conflict UI extension: attaches to the bottom of the settings page through the official slot contract, preserving built-in model search, bulk select/deselect, and DeepSeek Account login while avoiding update-related breakage and blank screens.
• Cross-platform and version resilient: runs reliably on both DSH Web and Desktop across v0.1.x, v0.2.x, and later releases.
• Restrained permissions: the proxy binds 127.0.0.1 only, stores no keys, calls no other service, sends no telemetry, and opens a single local TCP port.

How to Use This Plugin?

After enabling it in DSH, open Settings → Models and find the Local Route Proxy card at the bottom of the page; toggle the proxy and enter a port there, and the change takes effect immediately. Then point external clients such as Cline, Claude Dev, Cursor, or LibreChat at the loopback address and port, and their requests will be translated to the model routes you configured in Harness. To confirm the service is healthy, query the health endpoint to see the available routes and endpoints. If you only want the UI improvements, leaving the proxy off still keeps model search and bulk selection working.

How to Troubleshoot This Plugin?

If an external client cannot connect, first confirm the proxy is enabled and the port is not taken by another process, then use the health endpoint to check whether the target provider appears in the available routes. If the Models settings page goes blank or loses features, the plugin and your DSH version are likely mismatched; update to a compatible version following the official instructions. Because the plugin replaces no official package, such issues usually trace back to the upstream version.