DSH v0.2.1-rc.3 update

DeepSeek Harness v0.2.1-rc.3: Plugins & Draft Recovery

Author
DeepSeekAgent.io Editorial Team
Published
Updated

DeepSeek Harness v0.2.1-rc.3 was released on October 23, 2026. This candidate does not introduce a new Session format or a large migration. It places plugin actions closer to the active workspace, preserves unsent New Session drafts across conversation switches, and aligns the model list used by the DeepSeek API Key adapter.

npm channel and installation

npx @deepseek-ai/[email protected] web

At release time, npm next points to 0.2.1-rc.3, while latest remains 0.2.1-rc.2. Running npx @deepseek-ai/dsh web without a version can therefore still install rc.2. Pin the complete version when validating rc.3.

Plugin actions move into the main workspace

The official notes add more menus to the left sidebar, conversation views, and right sidebar for browsing and creating plugins. This shortens the path from an active task to the plugin market or Creator workflow.

The additional entry points do not change the security boundary. Bundle installation, build-script execution, tool enablement, and Session capability injection still need the same approval and isolation rules. Treat rc.3 as a navigation improvement rather than a broader permission grant.

Unsent drafts survive conversation switches

rc.3 fixes a direct workflow problem: text entered in New Session should remain available after switching to another conversation and returning.

A small upgrade check is enough:

  1. type a non-sensitive test draft in New Session;
  2. switch to an existing conversation and return;
  3. verify that the draft remains, then check whether a page refresh behaves as expected.

Draft recovery protects composer state. It does not replace an explicit checkpoint containing completed work, relevant files, and external side effects for long-running tasks.

API Key mode receives the same model list

The DeepSeek API Key adapter model list now follows the account sign-in path. Users who test both authentication modes should see fewer differences in model names and availability.

After upgrading, verify the actual provider, model ID, and capability declaration instead of relying only on the displayed label. Image input, search, and reasoning controls still depend on the selected model and adapter route.

Upgrade checklist

  • start the pinned 0.2.1-rc.3 version and confirm it at runtime;
  • inspect plugin entry points in the left sidebar, conversation view, and right sidebar;
  • verify New Session draft recovery after switching conversations;
  • compare the model list under account sign-in and API Key authentication;
  • run one read-only tool call in an important Profile to confirm plugin state.

For the V4.1 Flash 1017 and Search/Fetch additions inherited from the previous candidate, see the v0.2.1-rc.2 release guide.

References