DeepSeek Harness plugin backup. Archives are written to ~/.dsh-backup.
Repository: https://github.com/usertoandy/dsh-backup.git
| Command | Function |
|---|---|
/backup |
Archive the DSH home to ~/.dsh-backup/dsh-backup-<timestamp>.tar.gz and report the archive path and size. |
/backup-list |
List the existing archives in ~/.dsh-backup (number, filename, size, date). |
/backup-restore |
Ask (via the harness question UI) which backup to restore and how, then extract it into the DSH home. |
The confirm question offers the original tool's three answers:
yes— extract over the current files; files not in the backup are kept.clean— empty the DSH home first, then extract (exact restore of the backup). Refused when the target resolves to/or the user's home directory.no— cancel the restore.
After a restore you may need to restart any running dsh processes.
The host loads src/index.ts directly (no build step). Install straight
from the npm registry — dsh plugin add forwards the package name to pnpm
inside the profile directory, then activates the bundle automatically
(the bundles list is updated by the reconcile step):
dsh plugin --profile web add @wildusk/dsh-backupRestart dsh web afterwards; /backup, /backup-list and /backup-restore
then appear in the command palette.
At runtime the plugin uses the host-provided commands and userQuestions
services plus tar on the PATH.
src/index.ts— plugin entry:name/inject/apply.src/commands.ts— the three command handlers and their output text.src/backup-core.ts— timestamped tar.gz creation, listing and guarded restore (asynchronous, abort-aware).