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

How to move Claude Code and Codex sessions into DSH with Awesome DeepSeek Harness

Use dsh-claude-move to bring sessions, memories, skills, and slash commands into DSH with approval gates.

Credentials. Migrated sessions and memories can contain private code, keys, or tokens from the source tool, so review each approval prompt before you confirm.

Who it is forA developer who has been using Claude Code, Codex, OpenCode, or Hermes and wants the same setup in DSH.

The problemRebuilding skills, instructions, and session history by hand in a new tool is slow and error-prone.

The outcomeYour existing sessions, memories, skills, instructions, and slash commands appear in DSH after you approve each step.

What you need first

  • Node.js installed, for the npx command that starts the official DSH web runtime
  • pnpm on your PATH, for installing external profile bundles with dsh plugin
  • A project folder or Git repository where the agents can work
  • Review of each third-party plugin's source before installing it

Steps

  1. Open the dsh-claude-move entry in the Core & Bundles section and follow its install link.
  2. Install the package with dsh plugin --profile web add "github:PerryLink/dsh-claude-move". (inferred, check the README)
  3. Restart with dsh --profile web.
  4. Run the migration wizard and confirm each approval prompt before it writes data.

Prompt for your agent

Using the repo 0xsline/awesome-deepseek-harness, install dsh-claude-move from github:PerryLink/dsh-claude-move into DSH. Run its migration wizard for <source tool: Claude Code or Codex> and report which sessions, memories, and skills were moved. Verify the migration is idempotent by running it a second time and confirming no duplicates appear.

Caveat. The README describes the approval gate and resumable sessions but does not say how migrated data is stored or whether it is encrypted.

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