# AI use cases for DSH Config Manager (xiajiajun516/dsh-config-manager) Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Use cases: 5 | Page: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/ A DeepSeek Harness (DSH) plugin that backs up, restores, exports, imports, migrates and syncs a DSH configuration, including plugins, MCP servers, skills and workspaces. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Move your full DSH setup to a new computer in one export and import: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/migrate-dsh-to-new-machine/ - Keep a rolling full DSH backup without manual exports: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/schedule-automatic-dsh-backups/ - Keep DSH configuration in step between machines through Git, WebDAV, S3 or Gist: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/sync-dsh-config-across-machines/ - Bring Claude Code, Cursor or Codex setup and chat history into DSH: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/import-config-from-other-ai-agent/ - Restart a DSH conversation from an earlier message and optionally revert the wor: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/rewind-conversation-to-earlier-message/ ## How to move your full DSH setup to a new computer in one export and import with DSH Config Manager Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Export your DSH configuration as one ZIP on the old machine and import it on the new one. **Who it is for:** A developer who is switching to a new laptop or workstation and does not want to reinstall plugins, MCP servers and skills by hand. **The problem:** Reinstalling every plugin, MCP server and skill on a new machine is slow, and absolute paths from the old machine break. **The outcome:** The new machine has your settings, plugins, MCP servers, skills and global instructions (AGENTS.md), with dead absolute paths remapped. ### 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 to paste into your agent ```text Using the DSH Config Manager plugin in , export the full DSH configuration to a single ZIP, then import it on 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. Risk, 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/migrate-dsh-to-new-machine/ ## How to keep a rolling full DSH backup without manual exports with DSH Config Manager Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Turn on scheduled backups with a fixed cadence and a retention policy that keeps old copies thinned out. **Who it is for:** A user who wants a recent copy of the DSH configuration on disk without remembering to export it. **The problem:** Manual exports are easy to forget, so the latest working configuration is often not backed up when something breaks. **The outcome:** DSH writes a fresh full backup on a schedule, keeps a set of older copies by retention rule, and flags repeated failures in red. ### 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 to paste into your agent ```text In DeepSeek Harness on , 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. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/schedule-automatic-dsh-backups/ ## How to keep DSH configuration in step between machines through Git, WebDAV, S3 or Gist with DSH Config Manager Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Difficulty: Advanced | Time: 2 hours | Basis: From the README Push and pull portable configuration through a remote channel, with optional encrypted credentials. **Who it is for:** A developer who works on two or more machines and wants the same DSH setup on each without copying ZIP files by hand. **The problem:** Keeping several DSH installs aligned by hand drifts over time, and secrets must not leak to the remote host. **The outcome:** Each machine pushes or pulls the same portable configuration through one configured channel, and the remote only stores ciphertext when credentials are included. ### Steps 1. Open the Sync section and configure one channel: Git private repo, WebDAV, S3-compatible object storage, or GitHub Gist. 2. Run the first push from the machine that holds the reference configuration. 3. On the second machine, configure the same channel and pull the configuration. 4. Review the preview and resolve any conflicts before applying. 5. If you need credentials to travel, tick Export secrets, set an encryption password, and confirm the snapshot is encrypted before syncing. ### Prompt to paste into your agent ```text Configure the DSH Config Manager plugin on to sync portable configuration to (Git, WebDAV, S3-compatible or Gist). Run a push, then confirm on that a pull shows the same sections and that the remote holds only encrypted content if credentials were exported. ``` ### Caveat Secrets do not sync by default, so each new machine needs its credentials entered again unless you use an encrypted snapshot. Risk, credentials: Credentials only leave the machine as scrypt and AES-256-GCM ciphertext when Export secrets is ticked with a password, so losing that password means losing the stored credentials. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/sync-dsh-config-across-machines/ ## How to bring Claude Code, Cursor or Codex setup and chat history into DSH with DSH Config Manager Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Translate another AI coding agent's MCP servers, skills, instructions and conversations into a DSH import. **Who it is for:** A developer who already uses Claude Code, Cursor, Codex or another supported agent and wants to move that setup into DSH. **The problem:** Rebuilding MCP servers, skills and conversation history by hand in a new agent is tedious and error prone. **The outcome:** DSH shows a reviewable import plan with MCP servers, skills, global instructions, conversations and workspaces, and asks you to re-enter any secret key names. ### Steps 1. Pick the source agent on this machine in the import from other AI agents flow. 2. Let DSH translate that agent's configuration into a standard bundle. 3. Open Preview and review the plan, including chat history if the source supports it. 4. Resolve per-item conflicts with Keep current or Use backup. 5. Apply the import, then re-enter any secret values that DSH asks for. ### Prompt to paste into your agent ```text Use the DSH Config Manager plugin to import the configuration and chat history on into DeepSeek Harness. Stop at the preview step, list the MCP servers, skills and conversations that would be imported, and state which secret key names need re-entry. ``` ### Caveat The README says 30 sources are recognized and 29 can migrate chat history, so confirm that your specific source supports chat history before relying on it. Risk, credentials: The import reads only secret key names from the source agent, never the values, so the values must be typed in again inside DSH. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/import-config-from-other-ai-agent/ ## How to restart a DSH conversation from an earlier message and optionally revert the wor with DSH Config Manager Repo: [xiajiajun516/dsh-config-manager](https://github.com/xiajiajun516/dsh-config-manager) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Branch a conversation from any user message while keeping the original archived and unchanged. **Who it is for:** A developer in a long DSH session who realizes an earlier message sent the work down the wrong path. **The problem:** Continuing from a bad turn keeps the wrong context, and undoing the work by hand across files is slow. **The outcome:** A new branch conversation starts from the chosen message, the original stays intact in the archive, and workspace files can be reverted with a per-file diff shown first. ### Steps 1. Find the user message you want to restart from in the conversation. 2. Click the rewind to here action on that message. 3. Decide whether to revert the workspace files too. 4. Review the per-file diff and line counts shown before anything changes. 5. Confirm, then continue in the new branch conversation. ### Prompt to paste into your agent ```text In DeepSeek Harness on , use the DSH Config Manager rewind feature on the user message in the conversation . Keep the original conversation archived, do not revert workspace files, and report the new branch conversation name and the original's archive status. ``` ### Caveat Rewind is separate from Snapshot restore, so reverting workspace files here does not roll back the full configuration. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/xiajiajun516-dsh-config-manager/rewind-conversation-to-earlier-message/