If you want to carry an unfinished DeepSeek conversation into DSH, there is now an alternative to copying passages by hand. Released on November 13, DSH v0.2.2-rc.3 adds an experimental plugin for importing past conversations from the DeepSeek App or website and continuing them in a workspace. DSH is DeepSeek's open-source agent harness: it runs separately, rather than adding a feature inside the App.
Start DSH, then check the plugin's entry point
The project README provides a starting point. Install Node.js, then run npx @deepseek-ai/dsh web to launch the Web UI. Read the safety notice linked there before running the project. This command starts DSH; it is not an instruction for enabling the importer, whose specific activation steps still need checking.
This is a pre-release, and the README warns of compatibility-breaking changes during the developer preview. The announcement confirms history import, not an ongoing connection between both applications. It makes no promise to send new DSH messages back to the original conversation, and does not explain attachment coverage or duplicate-import handling.
Our suggested acceptance test is simple. Keep the original conversation and choose a short sample whose contents you know. After importing it, check message order and important requirements, then ask a follow-up that depends on the earlier discussion. If the source includes attachments, check their availability separately.
Billing needs its own check. The release notes give no plugin price and do not say that App or web allowances carry over. Before continuing generation, verify the model, account and billing arrangement in the destination workspace against the relevant service terms. Moving conversation content does not establish that usage entitlements move with it.
Windows users should verify the update actually finished
The same release addresses an issue that could make Windows desktop in-app updates fail and prevent automatic reopening. The preceding rc.2 release added switching between stable and development update channels and improved installation-status feedback. The new fix concerns failure and reopening, so visible download progress alone is not proof that the upgrade completed.
Reopen the application and confirm its version before testing imports. Our assessment: this is suitable for a limited migration test. Start with nonsensitive material and check that the conversation carries forward as expected before expanding use.