What happened
DeepSeek Harness’s GitHub release page identifies dsh-v0.2.2-rc.3 as a pre-release. The release was published on November 13, 2026, by imccyu, and the page lists 608 commits to master since this release. The central addition is an experimental “DeepSeek chat import” plugin. The English release notes say it can import past conversations from either the DeepSeek App or its web version into a workspace, allowing the user to continue chatting there.
That description establishes the basic workflow: a user has an earlier conversation in DeepSeek’s app or web client, brings it into a Harness workspace, and continues the conversation from that workspace. The notes do not describe a separate export step, a supported file format, or whether the plugin connects directly to an account. They also do not say which kinds of conversation content are retained, whether attachments or other context travel with the chat, or whether the imported conversation can be edited before continuation. Those are practical details that users will need to check in the tool itself.
The release notes name a second change, a Windows desktop fix. According to the notes, an issue could cause in-app updates to fail and prevent the application from automatically reopening. The release says that issue is fixed. It does not describe a workaround, the affected Windows versions, or how often users encountered the failure. This is a maintenance fix alongside the new plugin rather than the headline capability.
The tag is explicitly marked “Pre-release,” and the release title identifies it as rc.3. It is therefore not presented as a stable 0.2.2 release. The notes credit imccyu for the new plugin and winewill for the Windows fix. They provide no price, subscription requirement, rollout schedule, or availability qualification beyond the release being on GitHub. Builders considering the import should treat its experimental status as a reason to test it with low-risk conversations first, rather than assuming it is a production-ready migration path.
What the archive adds
New Runtime’s earlier coverage described the Harness desktop app in its October 24, 2026 note and an earlier pre-release in another note from October 24. On October 28, coverage of dsh-v0.2.2-alpha.2 noted plugin updates and an experimental subagent tool. This is a new fact in a continuing release sequence: rc.3 adds chat import and a Windows update fix.
Trend signal
This release does not yet fit a pattern New Runtime tracks. The import feature moves conversations between DeepSeek surfaces, but the release notes do not establish a broader interoperability layer, portable skills, or a new agent runtime boundary. Whether this becomes a meaningful workflow shift depends on the plugin’s behavior and on whether users can reliably preserve the context they need.
Why now
The release does not explain why chat import arrived in this candidate or connect it to a deadline or broader product change. Its placement in dsh-v0.2.2-rc.3 makes it a new capability in the current pre-release sequence, but the notes do not state a target date for a stable release or say what prompted the change.
Why it matters
Conversation history is often where a task’s requirements, prior decisions, and corrections accumulate. If a builder can bring that history into a workspace and continue with it there, the transfer could reduce the friction of moving from a general-purpose chat into a tool used for ongoing work. It may also help users avoid repeating background information when switching surfaces.
That value depends on what “import” actually preserves. A transcript that carries the relevant exchanges is different from one that omits attachments, tool results, or other context a user relied on. The release notes do not specify those details, so teams should not treat import as a guaranteed context migration or as a substitute for keeping important project state in a controlled location. The experimental label matters: the feature is worth testing, but a successful import of one conversation would not establish reliability across every kind of chat.
For an individual Harness user, the sensible first use is modest: bring over a non-sensitive conversation and check that the result is understandable and useful before continuing a real task. For a team, it is also worth clarifying what information the conversation contains before importing it. The Windows fix is useful to affected desktop users, but does not change the tool’s capabilities; the main workflow change in this release is the optional path from an existing DeepSeek chat into a workspace.
Limits and uncertainty
DeepSeek’s release notes do not specify how the plugin accesses conversations, what conversation elements it imports, or whether the user can select only part of a history. They do not state whether the feature requires login, works with all DeepSeek App and web conversations, or has known size or language limits. No reliability measurements, privacy details, or security review are described in the release notes. The plugin is experimental, so the notes alone do not establish how it behaves in routine use. The Windows fix is also described without identifying affected versions or reporting validation results.
Reader takeaway
dsh-v0.2.2-rc.3 gives DeepSeek Harness users an experimental way to bring an existing DeepSeek conversation into a workspace and continue it. Treat that as a convenience to test, not yet as a dependable way to migrate project context. Start with a low-risk chat, inspect what actually came across, and keep essential decisions somewhere you can verify independently.
Open question
Does the experimental plugin preserve enough conversation context for reliable work, and what content does it leave behind?