AI Agent Hub
Back to plugins
⚙️

dsh-migrate-codex

Workflow Updated 2026.08.23

Run the following command in DeepSeek Harness:

dsh plugin install ChengxiuCDP/dsh-migrate-codex

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install ChengxiuCDP/dsh-migrate-codex inside a DeepSeek Harness session to install this plugin; the source is at https://github.com/ChengxiuCDP/dsh-migrate-codex

About this plugin

Switching machines means re-cloning repos, reconfiguring worktrees, and manually carrying uncommitted changes — migrating a Codex environment has always been tedious and risky. dsh-migrate-codex turns the process into a verifiable pipeline: after declaring a whitelist of repos, the plugin handles packaging, verification, and restoration without ever touching credentials, never overwriting an existing target, and leaving no half-restored state on failure.

The four-step workflow works as follows: prepare bundles whitelisted repo commits and dirty snapshots into git bundles; verify checks SHA256SUMS integrity and confirms credential files are excluded; restore applies the bundle on a new machine, aborting immediately if the target already exists; restore-worktree recreates a single dirty worktree on demand. The bundled codex-migration Skill teaches the agent the full workflow, safety red lines, and how to align Codex configuration with DeepSeek Harness, so a single natural-language prompt triggers the entire migration.

If you juggle multiple local worktrees, distribute repos offline, or need to sync a Codex environment safely between a work laptop and a dev box, this plugin fills the automation and safety gap in the migration step.

Use Cases

  • Restoring a Codex environment after swapping from a work laptop to a personal dev box
  • Distributing whitelisted repos and dirty snapshots to an offline machine
  • Verifiable backup and on-demand recreation of multiple worktree environments

Best For

  • Heavy Codex users who maintain multiple local worktrees daily
  • Engineers syncing development environments across two or more machines
  • Security-conscious developers who require sensitive credentials to never leave the machine