AI Agent Hub
Back to plugins
🖥️

dsh-session-snapshot

Client Updated 2026.09.05

Run the following command in DeepSeek Harness:

dsh plugin install po-et/dsh-session-snapshot

Paste the following prompt into your AI chat to install this plugin:

Install the session-snapshot plugin in DeepSeek Harness by running dsh plugin install po-et/dsh-session-snapshot; the open-source repository is https://github.com/po-et/dsh-session-snapshot. Once installed it automatically takes integrity-verified rolling snapshots at every turn boundary with no extra configuration required.

About this plugin

When a DeepSeek Harness session log crashes mid-write or hits dsh's own cold-load repair path, the damage can be unrecoverable. dsh-session-guard stops concurrent-write corruption, but those two scenarios still slip through. dsh-session-snapshot was built to close that residual gap from the other side.

At the end of every turn it runs an integrity check on the live log. If the log still loads cleanly, it is promoted to a rolling snapshot; if it is already corrupt, the last good snapshot is preserved and a concrete recovery guide is shown. The CLI works even when dsh itself refuses to boot, and every restore first saves the current file as .pre-restore- while rejecting any snapshot that fails its own verification. The overhead is a single file copy plus one scan per turn, negligible in day-to-day use. Snapshots cover the session log only, not workspace files.

Ideal for developers who rely on DeepSeek Harness daily, care about session continuity, and want the worst case to cost at most the one turn in flight. Zero runtime dependencies,MIT licensed.

Use Cases

  • A DeepSeek Harness session crashes mid-write and you need to roll back to the last verified snapshot
  • Multiple dsh processes run concurrently and you want a safety net against silent log corruption
  • Keep an integrity-verified good copy between turns so a single bad write never wipes the whole history

Best For

  • Developers who rely on long DeepSeek Harness sessions every day
  • Teams with hard requirements on session-log integrity and recoverability
  • Individual users who want the worst case to cost only the in-flight turn