Install
Inside DeepSeek Harness, with dsh-market
dsh plugin --profile web add dshmarket
Or from the command line
dsh plugin --profile web add github:dpskk2/dsh-sync-plugin
Installing runs third-party code with your own permissions — it can read your files, use your credentials and reach the network. Review the source first, and pin a commit (github:owner/repo#sha) when you can.
README
DSH ChatSync
Pick up where you left off.
Sync DeepSeek Harness (DSH) conversations, attachments, settings and project files across your computers. Your data stays in your own private GitHub repository.
Get started · Detailed guide (Chinese) · Source downloads · Changelog (Chinese) · 中文
For alternating between your own computers: sync on the first, retrieve on the next, and continue.
- Synced: conversations, attachments, model and interface settings, and workspace project files.
- Set up separately: model API keys, other plugins and project dependencies on each computer.
- Bring your projects along: sync workspace project files as well as conversations, so you can keep chatting and working on another computer.
First-time setup
Before you start: DSH opens normally, Git and GitHub CLI are installed, and GitHub is reachable.
① Install the plugin
Run the command for your host in PowerShell; install separately if you use both.
Web:
dsh plugin --profile web add @dpskk2/dsh-chatsync
Desktop (default Windows installation):
& "$env:LOCALAPPDATA\Programs\DeepSeek Harness\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add @dpskk2/dsh-chatsync
Open Desktop once, then fully quit it (including its tray icon) before installing. For custom installation paths or errors, see the desktop installation guide.
② Sign in to GitHub
gh auth login --hostname github.com --git-protocol https --web
Complete browser authorization. Choose Yes when asked to authenticate Git with this account.
③ Sync on your original computer
Restart DSH, open 设置 → 同步 (Settings → Sync), and click 立即同步 (Sync now). The default setup creates or reuses a private GitHub repository automatically.
Note: turn off 同步工作区文件 and save first if you do not need project files. A local snapshot alone means nothing has been uploaded yet.
④ Retrieve on your new computer
Repeat ①② with the same GitHub account, restart DSH, and sync. After retrieval succeeds, restart again and configure local model API keys to continue your conversations.
Note: install other plugins and project dependencies separately. For a custom repository, use the same URL and branch on both computers.
Everyday use
Sync before starting and after finishing; confirm success before switching computers. Click ⟳ 同步 in the sidebar. To automate syncing, enable it under 设置 → 同步 → 同步偏好 and save.
Detailed instructions
The linked guides are in Chinese.
- Installation and troubleshooting: tools, Desktop setup, the two dsh commands and common issues.
- Switching computers: retrieval, project paths and dependencies.
- Sync settings: automatic sync, intervals, proxies and custom repositories.
- Sync scope: included data and exclusion rules.
Features and limits
- Workspace grouping: syncs conversation-to-workspace mappings and attempts to repair missing registrations; prompts for a restart when the sidebar needs refreshing.
- Automatic sync: off by default. When enabled, defaults to five-minute intervals and responds to session activity. Startup sync is bidirectional; normal exit attempts to save and upload. DSH must stay running with network access. See Configuration.
- Conflict handling: confirmed append-only histories are preserved verbatim. Divergent sessions retain one side, with both originals in Git history and recovery references in sync details. Settings merge field by field; ordinary file conflicts usually keep the local version.
- Restart repair: on Windows, instructions and actions follow the host: Web restarts its service; Desktop closes and reopens the app. Automatic restart is on by default; explicit opt-outs are preserved. Detected session activity pauses it; unknown activity requires manual confirmation. See restart requirements.
- Patch hosting (advanced):
.dsh/patches/syncs with the repository. Web checks and applies patches on startup and after syncing; Desktop does not apply these Web runtime patches.
Data and privacy
The dedicated credentials file is excluded, but secrets written into conversations, attachments or project files can still be synced. Use exclusion rules to control what uploads. Sync propagates deletions and edits; keep separate backups of important data.
Updates and help
The complete source ZIP contains all version-controlled files at the release tag, including tests, development check scripts and documentation. It excludes Git history, dependencies and local files outside the repository. The npm package follows the files list in package.json: runtime code, the desktop restart script and selected documentation; tests and development check scripts are excluded. Bundled validation records document historical checks, not additional real-device validation of the current version. See the 0.20.0 validation record for the current scope.
Each new version includes Chinese release notes and a complete source ZIP on GitHub Releases. To download the source, open a release and select dsh-chatsync-vVERSION-source.zip under Assets. Use the installation steps above or the update command below to install or update the plugin.
To update the plugin, run this command and restart DSH:
dsh plugin --profile web update @dpskk2/dsh-chatsync
On the desktop app, update through its bundled command runtime instead (quit the app first):
& "$env:LOCALAPPDATA\Programs\DeepSeek Harness\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop update @dpskk2/dsh-chatsync
- Installation errors, missing Sync controls, failed uploads or missing conversations: see Troubleshooting.
- Proxies, custom repositories and other settings: see Configuration.
- Still stuck? Report an issue with error details, removing private content and keys.
The linked guides are in Chinese. The plugin supports DSH's web profile and the desktop app's desktop profile, and declares DSH ≥ 0.1.5-rc.3 and Node.js ≥20; Node.js 24 is recommended. DSH Web 0.2.0-rc.1 has been tested. See the validation record for tested environments.
Comments
Comments live in GitHub Discussions. Sign in with GitHub to post or react.