DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to keep a rolling full DSH backup without manual exports with DSH Config Manager

Turn on scheduled backups with a fixed cadence and a retention policy that keeps old copies thinned out.

Who it is forA user who wants a recent copy of the DSH configuration on disk without remembering to export it.

The problemManual exports are easy to forget, so the latest working configuration is often not backed up when something breaks.

The outcomeDSH writes a fresh full backup on a schedule, keeps a set of older copies by retention rule, and flags repeated failures in red.

What you need first

  • DeepSeek Harness (DSH) installed on each machine involved
  • This plugin installed in DSH
  • A target machine (Windows, macOS or Linux) for the restore or migration
  • For sync: a private Git repository, a WebDAV server, an S3-compatible bucket, or a GitHub Gist
  • An encryption password if you want credentials to travel with a backup

Steps

  1. Open Home and find the Scheduled backup card.
  2. Choose a cadence: 6h, 12h, 24h, 7d, or a custom weekly weekday and time.
  3. Set the retention policy: last N backups, plus one per month, plus one per year.
  4. Turn the schedule on and leave it running in the background.
  5. Check the Scheduled backup card for failures, which are highlighted in red.

Prompt for your agent

In DeepSeek Harness on <machine>, use the DSH Config Manager plugin to enable Scheduled backup with a 24h cadence and the default retention policy. Report the next scheduled run time and confirm that the backup contains no secret values.

Caveat. Scheduled backups never include secrets, so restoring a scheduled backup on a new machine means re-entering credentials.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page