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

How to move your full DSH setup to a new computer in one export and import with DSH Config Manager

Export your DSH configuration as one ZIP on the old machine and import it on the new one.

Credentials. Exports exclude API keys and tokens by default, so you will need to re-enter them on the new machine unless you use an encrypted backup with a password.

Who it is forA developer who is switching to a new laptop or workstation and does not want to reinstall plugins, MCP servers and skills by hand.

The problemReinstalling every plugin, MCP server and skill on a new machine is slow, and absolute paths from the old machine break.

The outcomeThe new machine has your settings, plugins, MCP servers, skills and global instructions (AGENTS.md), with dead absolute paths remapped.

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 the export flow in the plugin and keep the recommended sections ticked, or adjust them item by item.
  2. Package the configuration as a single ZIP file with one click.
  3. Copy the ZIP to the new machine.
  4. Open Preview before import and read the migration consult verdict and its evidence.
  5. Pick the content you want item by item, resolve each conflict with Keep current or Use backup, then run the import.

Prompt for your agent

Using the DSH Config Manager plugin in <source-machine>, export the full DSH configuration to a single ZIP, then import it on <target-machine> through the preview flow. Confirm that the MCP servers and skills are listed as restored and that no secret values were exported.

Caveat. Local development plugins installed with link: or file: are packed into the backup, but the restore still runs through a preview and conflict step, so review the plan before you confirm.

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