feat: support DeepSeek Harness 0.2.x (peer deps currently pin <0.2.0) #2520

Activity

1. Memtensor-AI

   added

   area:pluginOpenClaw & HermesOpenClaw & Hermes

   status:needs-product-reviewRequires product owner confirmation before deciding public repo, transfer, or internal backlog.Requires product owner confirmation before deciding public repo, transfer, or internal backlog.

   types:enhancementNew feature or improvement | 新功能或改进New feature or improvement | 新功能或改进

   on Oct 20, 2026
2. Memtensor-AI

   assigned

   CarltonXiang

   ,

   hijzy

   ,

   shinetata

   and

   whipser030

   on Oct 20, 2026
3. XMD-jck commented on Oct 23, 2026

   

   XMD-jck

   on Oct 23, 2026

   More actions

   Confirming this on a second clean environment. Adding one fact that changes the severity from "may not run correctly" to "cannot run at all":

   DSH 0.2.1-rc.2 does not merely fail the peer check — it actively refuses to load the bundle.

   Environment:

   • DSH runtime 0.2.1-rc.2, desktop client 0.2.1.0
   • Windows 11 (10.0.26200)
   • @memtensor/memos-local-plugin@2.0.20 installed on a sandbox profile (real profile untouched)

   After registering the bundle in dsh.profile.bundles, dsh --profile <sandbox> --dump-config exits with:

   dsh: skipping profile bundle "@memtensor/memos-local-plugin":
   Error: Plugin @memtensor/memos-local-plugin@2.0.20 is incompatible with dsh 0.2.1-rc.2:
   requirements {
     "@deepseek-ai/dsh-agent":         ">=0.1.0-rc.5 <0.2.0",
     "@deepseek-ai/dsh-llm":           ">=0.1.0-rc.5 <0.2.0",
     "@deepseek-ai/dsh-session":       ">=0.1.0-rc.5 <0.2.0",
     "@deepseek-ai/dsh-system-prompt": ">=0.1.0-rc.5 <0.2.0",
     "@deepseek-ai/dsh-timeout":       ">=0.1.0-rc.5 <0.2.0",
     "@deepseek-ai/dsh-tools":         ">=0.1.0-rc.5 <0.2.0"
   }.
   Running it may cause crashes or data loss.
   Exact-version exemption: not active.
   

   So the bundle is skipped before a single plugin row is mounted — the memos-local-memory row never appears in the composed tree.

   What already works (verified in the sandbox), so this looks like a peer-range/adapter issue rather than a packaging one:

   • pnpm install resolves all 195 dependencies fine
   • better-sqlite3 native binding loads correctly inside the Electron host (ELECTRON_RUN_AS_NODE=1)
   • onnxruntime-node, sharp, and the local embedding model are all present
   • the adapter patch itself parses (adapters/deepseek-harness/cordis.patch.yml)
   • the bundle already sets failOnStartupError: false on the memos-local-memory row

   On the "just widen the peer range?" question from the original report: the adapter hooks six host services (agent, llm, session, system-prompt, timeout, tools). I have not audited whether their 0.2.x signatures still match, so I cannot say whether widening the range alone is sufficient — an actual adapter pass is probably needed.

   Workaround we chose: not running dsh plugin allow-version on a memory plugin. Those six hooked services are core; a silent write-path mismatch in memory storage is worse than no memory at all.

   Happy to test a beta branch on 0.2.1-rc.2 if one appears.
4. endxxxx commented on Oct 29, 2026

   

   endxxxx

   on Oct 29, 2026

   Collaborator

   More actions

   Partial update: #2519 has been merged and released as @memtensor/memos-local-plugin 2.0.21. It fixes V4 message-source admission and addresses the Electron SQLite installation problem with better-sqlite3@13.0.3.

   This does not complete the requested DSH 0.2.x support. The local plugin’s peer range still ends at <0.2.0, and #2519 does not update the Cloud plugin’s compatibility range.

   Keeping this issue open for peer-range updates and validation against the supported DSH 0.2.x versions. Related work remains in #2541.
5. syzsunshine219

   added a commit that references this issue on Nov 4, 2026

   fix(plugin): support validated DSH 0.2 preview APIs (#2549)

   ...

   d326a64
6. endxxxx commented on Nov 9, 2026

   

   endxxxx

   on Nov 9, 2026

   Collaborator

   More actions

   Thanks for reporting the startup compatibility check. The local plugin now has a published beta for the supported DSH 0.2.0 and 0.2.1 previews, including 0.2.1-rc.2. #2549 updates the peer ranges and adapts to the DSH 0.2 API. The beta also includes the V4 message-source fix from #2519.

   To try it in a DSH CLI profile:

   dsh plugin --profile web add @memtensor/memos-local-plugin@2.0.21-beta.1

   Replace web with your profile name and restart DSH. Select the beta explicitly, since the local plugin's latest tag still points to 2.0.21.

   For the Cloud plugin, @memtensor/memos-cloud-dsh-plugin@0.1.2 now declares compatibility with the DSH 0.2.0 and 0.2.1 preview lines. We'll keep this issue open to track the stable local plugin release and confirm that the Cloud plugin loads and runs on the reported 0.2.1-rc.2 setup. If you've tried either package on that version, we'd appreciate hearing how it went.