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.
Who it is forA developer who already uses Claude Code, Cursor, Codex or another supported agent and wants to move that setup into DSH.
The problemRebuilding MCP servers, skills and conversation history by hand in a new agent is tedious and error prone.
The outcomeDSH shows a reviewable import plan with MCP servers, skills, global instructions, conversations and workspaces, and asks you to re-enter any secret key names.
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
- Pick the source agent on this machine in the import from other AI agents flow.
- Let DSH translate that agent's configuration into a standard bundle.
- Open Preview and review the plan, including chat history if the source supports it.
- Resolve per-item conflicts with Keep current or Use backup.
- Apply the import, then re-enter any secret values that DSH asks for.
Prompt for your agent
Use the DSH Config Manager plugin to import the <source-agent> configuration and chat history on <machine> 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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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