dsh-backup-migrator

Rebuilding a DeepSeek Harness plugin environment on a fresh machine usually means reinstalling every plugin, hand-recreating configs, and re-attaching launchd timers scattered across ~/.dsh/scripts and ~/Library/LaunchAgents — and locally developed plugins, linked via link: or file:, simply vanish without a trace. dsh-backup-migrator collapses the entire process into a single command: it scans your profiles, builds a manifest covering all four plugin sources (npm, GitHub, link:, file:), packs local plugins into tarballs so they survive the move, gathers dsh-*.json configs, the user-content layer (skills, agent-presets, adapters, AGENTS.md, mnemon memory and distilled notes), and an aux directory carrying external scripts and plist files — then commits and pushes everything to your own GitHub repository. Restoring is equally one command: pull the repo, reinstall every plugin by source (online for npm/GitHub, offline from tarballs for local ones), write back configs and the user patch layer, rewrite home paths and the node interpreter for scripts and plists, and load them with launchctl. Your entire backup history is your git history, so any day snapshot can be rolled back.

If your DSH setup goes beyond stock plugins — locally developed bundles, a TickTick deferred-sync daemon, a blog cron job, a growing ~/.mnemon memory, or a pile of hand-tuned configs — this plugin is built for that treat-your-environment-as-asset workflow. The built-in in-process scheduler lets you flip on autoBackup and have backups run on an interval from inside the host process, with missed windows caught up automatically after the machine wakes or DSH restarts. Failed runs retry after backupRetryMinutes instead of waiting a full interval, and only a run that fully lands (build, commit, and push) counts as success. Combined with the includeSecrets toggle and 0600 file permissions, you control exactly what enters the repo — a private repository is strongly recommended whenever secrets are included.