dsh-session-guard
DeepSeek Harness 插件，可防止并发写入导致的会话损坏问题：为每个会话使用支持过期接管的建议锁，因此两个 dsh 进程不再会损坏同一个会话日志
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:po-et/dsh-session-guard#f3fa933554c5dbf8eb52469affbe6de588bef29aSession Guard 以 dsh-session-guard 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Stops two DeepSeek Harness processes from corrupting one session log.
中文文档 · Companion: dsh-session-rescue (repairs the damage this plugin prevents)
The most common dsh corruption family is concurrent writing: a dsh web plus a CLI, two instances on different ports, or a desktop shell sharing one $DSH_HOME. Each process keeps its own in-memory seq cursor, the second writer lands events with already-committed seqs, and the session becomes permanently unloadable:
history unavailable for session "…": corrupt session log: seq gap in committed region …
dsh has no cross-process lock today. This plugin adds one — advisory, per-session, with automatic takeover of dead owners — so the conflicting step fails loudly with an actionable message instead of silently destroying your history.
dsh plugin --profile web add dsh-session-guard
Using an AI agent? Tell it: "Install the dsh-session-guard plugin into my dsh."
Error: session-guard: session session-37374e34… is already being written by another
dsh process (pid 84231 on mbp.local, held 42s, last heartbeat 3s ago). Two writers
on one session corrupt its log ("seq gap in committed region"). Close that process
or use a different session; a dead owner’s lock is taken over automatically …
The step fails; the log stays intact; nothing is lost. Crashed processes never wedge a session: a lock whose owner pid is gone is taken over instantly, and unverifiable owners (other hosts on a shared home) expire after 90s without a heartbeat.
All optional, set on the plugin row in your profile patch:
- id: session-guard
name: dsh-session-guard
config:
mode: enforce # 'enforce' (default) fails conflicting steps; 'warn' only logs
heartbeatMs: 15000 # heartbeat refresh for held locks
staleAfterMs: 90000 # unverifiable owners expire after this silence
# lockDir: /custom # default: $DSH_HOME/session-locks
agent/session-start, agent/pre-step). The cold-load repair path that commits synthetic interrupt-closers before any step runs is inside dsh itself and cannot be intercepted from a plugin — that fix needs to land upstream.$DSH_HOME/session-locks; deployments overriding the session root elsewhere in config still key locks by home + session id.Zero runtime dependencies. MIT.