dsh-session-snapshot
DeepSeek Harness 插件在每轮交互的边界持续创建并验证完整性的会话备份，因此任何损坏最多只会影响正在进行的一轮；即使 dsh 无法启动，也可使用一条命令恢复
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:po-et/dsh-session-snapshot#084e345828f1752e18ea06a7252672e85effb9c0Session Snapshot 以 dsh-session-snapshot 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Rolling, integrity-verified backups of every DeepSeek Harness session — so corruption costs at most the in-flight turn.
Part of a three-piece session-integrity suite:
| Stage | Plugin | Role |
|---|---|---|
| Prevent | dsh-session-guard | stop two dsh processes from corrupting one session |
| Snapshot | dsh-session-snapshot (this) | keep a verified good copy at every turn boundary |
| Repair | dsh-session-rescue | fix or salvage a log that already broke |
dsh-session-guard prevents the common concurrent-write corruption, but two cases stay outside any plugin's reach: a crash mid-write, and dsh's own cold-load repair path that runs before any agent step. This plugin closes that residual gap from the other side. After each turn ends it verifies the live log still loads and, if so, promotes it to a snapshot. When a turn ends with the log already corrupt, it does not overwrite the last good snapshot and tells you how to recover — losing at most the one turn in flight.
dsh plugin --profile web add dsh-session-snapshot
That's it — the plugin snapshots automatically at turn boundaries. Using an AI agent? Tell it: "Install the dsh-session-snapshot plugin."
The CLI works even when dsh itself won't boot:
npx dsh-session-snapshot # list snapshots + live health for every session
npx dsh-session-snapshot list 37374e34 # snapshots for one session (id fragment)
npx dsh-session-snapshot restore 37374e34 # restore the newest verified snapshot
npx dsh-session-snapshot snapshot 37374e34 # take one right now
restore always preserves the current file as <artifact>.pre-restore-<time> first, and refuses any snapshot that does not itself verify as loadable. Use --at <epoch> (shown in list) to restore a specific snapshot instead of the newest.
- id: session-snapshot
name: dsh-session-snapshot
config:
keep: 5 # snapshots kept per session before the oldest is pruned
minIntervalMs: 0 # minimum ms between snapshots of one session (0 = every changed turn)
# home: /custom # default: $DSH_HOME (~/.dsh)
Snapshots live under $DSH_HOME/session-snapshots/<session-id>/ and are only taken when the log grew and still verifies, so an unchanged or already-corrupt session never spends I/O or overwrites a good copy.
minIntervalMs for very large sessions if you want to bound it further..jsonl and .jsonl.zstd, JSONL backend. Compression is detected by content, so renamed/backup copies verify correctly. dsh is pre-1.0 with no format-compatibility promise; on an unknown version the tool refuses loudly rather than guessing.Zero runtime dependencies (zstd via Node's built-in zlib). MIT.