homily707/dsh-session-header
Project Overview项目介绍
This repository is a native plugin built exclusively for DeepSeek Harness (DSH). It injects an x-session-id HTTP header onto every outgoing LLM provider request that DSH sends, carrying the unique session ID of the current request. DSH does not natively expose a seam to add per-request headers, as each LLM adapter builds wire headers internally, so this plugin fills that gap for users that need session headers for routing, caching, or auditing. It works by combining two official DSH interception points to patch globalThis.fetch, so it covers all fetch-based LLM adapters without any changes to core DSH code.
The plugin uses AsyncLocalStorage to correctly propagate context across concurrent active requests. Only fetch calls that occur during an active LLM stream get the header injected, so unrelated traffic like web RPC, telemetry, and external tool calls remain completely untouched. It follows official HTTP semantics and will never overwrite an existing header that was already set by another part of DSH or a custom user configuration. When the plugin is unloaded, it automatically restores the original unpatched fetch implementation, leaving your entire DSH environment completely unchanged.
To install the plugin, you need Node.js 22 or newer and a working installation of the DSH CLI. The recommended installation method is as a bundle, which you can add directly via the command dsh plugin --profile <name> add github:homily707/dsh-session-header. Since the plugin is plain JavaScript with no build scripts, it does not require pnpm 10 or newer to install or run. After installation, you can verify it loaded correctly by checking the dumped config for the plugin layer entry, and it is released under the permissive MIT license for free use, modification, and distribution.
这是一个专为DeepSeek Harness(DSH)构建的原生插件,核心功能是给DSH发出的每一个LLM请求注入x-session-id HTTP头,携带当前请求对应的会话ID。DSH原生没有提供针对每个请求添加自定义请求头的入口,各个适配器都是内部构建请求头,无法直接透出会话信息给模型网关或中间代理。这个插件利用DSH官方提供的两个拦截点组合实现功能,不需要修改DSH的核心适配器代码。
对于需要基于会话头进行路由、缓存或审计的模型网关和中间代理场景,这个插件刚好能满足这类需求。它使用AsyncLocalStorage实现上下文传播,只会修改LLM调用过程中的fetch请求,不会影响无关的网络请求比如Web RPC、遥测和工具调用流量,也不会覆盖已经存在的同名请求头,卸载插件后还会完整恢复原始的fetch方法。
该插件要求Node.js版本不低于22,需要配合DSH CLI安装使用,推荐通过dsh plugin add命令直接从本仓库安装作为bundle包。它是纯JavaScript实现,没有构建脚本,不需要pnpm 10以上的构建权限。你也可以通过本地检出的overlay补丁方式安装,配置项支持自定义头名称、固定值、URL前缀匹配和覆盖指定已有头,采用MIT许可协议免费开源。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-session-header(homily707/dsh-session-header)
仓库:https://github.com/homily707/dsh-session-header
本站详情页:https://www.yhbd.top/plugins/homily707-dsh-session-header/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 8 · 最近提交 2026-09-09 · 主语言 JavaScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- Only 8 stars - very few users, little community feedback星标只有 8,几乎没人在用,遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add github:homily707/dsh-session-header
把 homily707/dsh-session-header 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
dsh-session-header
English | 中文
A DeepSeek Harness plugin that injects an x-session-id HTTP header onto every LLM provider request the harness sends, carrying the harness session id of that exact call.
Why
The harness has no per-request header seam — GenerateOptions has no headers field and every adapter builds its own wire headers internally. If your model gateway (or an intermediary proxy) keys routing, caching, or auditing on a session header, the harness cannot send one by itself.
This plugin closes that gap with the two official interception points composed together:
- the
llm/streamwaterfall names the calls that are LLM calls and carriesoptions.sessionId; - a
globalThis.fetchpatch adds the header, so every fetch-based adapter (llm-deepseek,llm-pi-ai, and any SDK whose transport bottoms out in global fetch) is covered without touching adapter code.
Context propagation uses AsyncLocalStorage: only fetches that happen inside an LLM call's stream are touched; unrelated fetches (web RPC, telemetry, tool traffic) pass through untouched. A header anyone else already set is never overwritten (case-insensitive, per HTTP semantics). Unloading the plugin restores the original fetch.
Semantics of the value:
- default:
GenerateOptions.sessionIdof the call in flight, with the harness'ssession-branding prefix stripped (a plain UUID is sent) — main-session turns, compaction/title helper calls, and in-process subagent children each report their own session id (subagents get their own child session ids); valueconfig: a fixed value for every call instead (sent verbatim, no prefix stripping);- calls with neither get no header.
Install
Requires the dsh CLI and Node ≥ 22.
As a bundle (recommended)
dsh plugin --profile <name> add github:homily707/dsh-session-header
This package is plain JavaScript with no build scripts, so the pnpm ≥ 10 build allowance is not needed. Verify the layer and boot:
dsh --profile <name> --dump-config # look for the "# == dsh-session-header" layer
dsh --profile <name>
As a --patch overlay from a local checkout
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
liangmianya/dsh-synapse
alaliqing/claude-paper
acryldev/acryl
omdsh-dev/dsh-annotation
Anionex/dsh-turn-rewind
Tyan66666/billion-context-dsh
qkycir-123/dsh-run2skill