What dsh-config-manager manages
DeepSeek Harness configuration can be exported as one ZIP archive and imported on another Windows, macOS or Linux machine. The documented bundle can contain settings, model providers, plugins and plugin configuration, MCP servers, skills, agent presets, workspaces and AGENTS.md. During migration, dsh-config-manager detects dead absolute paths and supports batch prefix mapping.
DeepSeek Harness keeps $DSH_HOME/profiles/<name> outside the backup. These profiles determine which plugin stack starts on a machine and are managed separately in Environment → Profiles, where they can be listed, created, renamed or deleted. The same view can launch or stop an independent instance.
dsh-config-manager’s import and backup behaviour
The import flow previews changes before writing them. It supports per-item conflict decisions, creates an automatic snapshot before applying changes, and can roll back to that snapshot. Scheduled full backups are configured in Home → Scheduled backup with 6h, 12h, 24h, 7d, or a custom weekly weekday and time. Retention keeps the last N backups plus one per month and one per year.
dsh-config-manager’s security and remote storage
Secrets are not exported or synchronised by default. When “Export secrets” is selected, ~/.dsh/.credentials.yaml is encrypted with scrypt and AES-256-GCM inside the snapshot; the encryption password is required for restoration. Remote synchronisation supports a private Git repository, WebDAV, an S3-compatible object store, and GitHub Gist. The remote payload excludes clear-text secrets.
The plugin can also import configuration and, for supported sources, chat history from 30 other AI-agent formats. Secret values are not read during that process; only key names are used so values can be entered again.
dsh-config-manager’s documented UI features
The built-in configuration market provides preview-first installation for shared configurations. Each section must be explicitly approved, and supply-chain warnings are shown. Conversation rewind creates a new branch while leaving the original archived; workspace-file changes can be reviewed by diff and line counts before reverting.
The README documents these UI flows rather than a separate command-line command set or named configuration keys.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub