FleetingEcho/dsh-handoff
Self-maintaining handoff memory per working directory and git branch: records turns, folds them into concise Markdown, and injects the result into future sessions from ~/.agent/agent-handoff, byte-compatible with pi-handoff.
Persistent working memory for DeepSeek Harness: one automatically maintained handoff.md per git branch, plus shared project knowledge available on every branch. Records recent turns, periodically folds them into concise Markdown, and injects the result into future sessions via a dsh runtime-context snapshot — nothing is written into your repository. Commands: /handoff status, flush, clear, pause/resume, project status/refresh/add/forget, pin/unpin. If you already use pi-handoff with pi, switching to dsh (or running both) reuses your existing handoff files with no migration.
Install
dsh plugin --profile web add github:FleetingEcho/dsh-handoffGitHub install per README (English): dsh plugin --profile web add github:FleetingEcho/dsh-handoff (equivalent: dsh plugin --profile web add https://github.com/FleetingEcho/dsh-handoff.git). The published repo ships a prebuilt lib/index.js and declares a dsh.bundle.patch, so one command reconciles it into the profile's bundle list. Restart the profile, then confirm with /handoff status. No clone or build needed.
Compatibility
DeepSeek Harness (dsh) web profile. Port of pi-handoff; on-disk store is byte-identical at ~/.agent/agent-handoff/, so pi and dsh share handoff files with no migration.
Details
- Repo: FleetingEcho/dsh-handoff
- Category: Memory
- Stars: 2
- Version: GitHub source (npm dsh-handoff 0.1.0 on registry, verified 2026-08-28)
- Last push: 2026-08-19
- First seen: 2026-08-14
Recent updates
per-branch handoff.md + shared project knowledge; auto-fold + runtime-context injection; pi-handoff byte-compatible store; /handoff command family.
FAQ
- What does it store?
- One automatically maintained handoff.md per git branch plus shared project knowledge available on every branch, at ~/.agent/agent-handoff/.
- Is it compatible with pi-handoff?
- Yes — the on-disk store is byte-identical to pi-handoff's, so both agents share one store and read each other's files with no migration.
- Does it write into my repo?
- No — the store lives under ~/.agent/agent-handoff/; nothing is written into your repository.
Alternatives
Phant0Meow/dsh-memory-meow · Scorp1o117/dsh-tdai-memory · Aik358/dsh-auto-memory