How dsh-rewind behaves
Each user message can expose a rewind action, or /rewind and /undo can open a candidate list. After selecting a target, choose conversation-only rewind or conversation-and-file rewind. The target text returns to the composer. Candidate and mode panels support ↑, ↓, Enter, and Esc.
DeepSeek Harness keeps the session log append-only. dsh-rewind appends one hidden-and-replaced marker rather than deleting history, so the withdrawn records remain available in the trajectory panel. Rewinding an already-read message interrupts the current turn; an unread steering message can also be selected without interrupting generation.
Configuring dsh-rewind
The plugin configuration card controls these settings:
| Setting |
Default |
Effect |
| Snapshot backups |
Enabled |
Creates file backups for later restoration |
| Automatic snapshot cleanup |
Disabled |
Removes snapshot directories for long-inactive sessions when configured and run |
DeepSeek Harness stores plugin configuration in the current profile’s cordis.patch.yml. The cleanup setting can also be viewed, configured, and run with /snapshot-auto-cleanup.
dsh-rewind storage and file scope
Snapshots are stored at <dsh home>/rewind-snapshots/, normally ~/.dsh/rewind-snapshots/. Deleting that directory removes file backups only; conversation rewind is unaffected. The plugin tracks files changed by write and edit tools, backs them up before writes, and checks tracked files at each user-message boundary. Unchanged files are not stored. Symlinks and hard links are skipped, and individual file failures do not stop the rest of a restoration.
Requirements and limits
The runtime requirement is Node.js >=24.9.0. Supported DeepSeek Harness versions come from package.json’s engines.dsh declaration. File rewind is deliberately not a full-tree snapshot: untracked files, child-agent edits, and Git history are outside its scope. Two documented UI limits are retained: distant rewinds can show a blank conversation until earlier history is loaded, and the round navigator keeps unloaded markers for rewound turns.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub