dsh-config-sync

Moving to a new machine used to mean manually copying settings.yaml, .credentials.yaml, profile plugin patches, and agent presets one by one — miss a single file and your workflow breaks. dsh-config-sync collapses that chore into a single step: say "export my config" in a DSH conversation and it bundles everything into a portable directory, or, for the more common case, a single .dshsync file sealed with a password you choose. Drop it on a cloud drive, a USB stick, or even a chat app — it stays locked until you say otherwise.

Restoring is just as frictionless. Point the new machine's DSH at the backup bundle, run a dry-run preview first, then commit the overwrite. Old files are automatically archived into a config-backups directory before anything is replaced, so backing out costs nothing. Five model-facing tools cover the full cycle — plain export, encrypted export, plain import, encrypted import, and a status check that never exposes key material in its output.

The security design is deliberate: encryption uses PBKDF2-SHA256 with 600,000 iterations plus AES-256-GCM, and a wrong password produces an explicit error rather than silent corruption. On the import side, only whitelisted paths are accepted; path traversal, absolute paths, and node_modules are all rejected. If you juggle multiple machines or simply want a just-in-case snapshot of your DSH configuration, this plugin is ready to use out of the box.