What it may solve
Per-provider request headers in the DeepSeek Harness Models settings page, with per-conversation ${sessionId} expansion.
Imported third-party catalog description; not a Registry verification conclusion.Per-provider request headers in the DeepSeek Harness Models settings page, with per-conversation ${sessionId} expansion.
Author: duanyunlun · Sessions & Messages · Catalog snapshot: 2026-09-16Per-provider request headers in the DeepSeek Harness Models settings page, with per-conversation ${sessionId} expansion.
Imported third-party catalog description; not a Registry verification conclusion.duanyunlun/dsh-provider-headers
— stars · 0 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-16No exact-version test is available.
No Registry security conclusion is available.
No functional smoke evidence is available.
Plugin permissions have not been resolved.
Package structure and integrity have not been analyzed.
Describe your task in a DSH conversation and mention dsh-provider-headers. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-provider-headersExact version not resolvedgithub:duanyunlun/dsh-provider-headersExact version not resolved