DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Memos Cloud Dsh Plugin — DeepSeek Harness 插件(DSH Plugin)
← Plugins

@memtensor/memos-cloud-dsh-plugin

Memos Cloud Dsh Plugin

用于 DeepSeek Harness 的 MemOS Cloud 生命周期记忆插件

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@0.1.1
README兼容性版本

兼容性与来源证明

Memos Cloud Dsh Plugin 以 @memtensor/memos-cloud-dsh-plugin 发布,当前版本为 0.1.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
npm
Registry 更新时间
2026/9/20

版本

0.1.1stable
2026/9/7
0.1.0stable
2026/8/16
查看其余 4 个版本
收起版本
0.1.1-beta.0beta
2026/9/7
0.1.0-beta.2beta
2026/8/16
0.1.0-beta.1beta
2026/8/16
0.1.0-beta.0beta
2026/8/16

相关插件

继续浏览 memory-context 分类下经过校验的插件。

Memory Plugin@openviking/dsh-memory-plugin适用于 DeepSeek Harness 的 OpenViking 记忆与上下文套件Contextdsh-context用于上下文洞察和管理的 DeepSeek Harness 插件,提供上下文仪表板和上下文命令,帮助了解上下文的构成及其演变过程。Weknora@wxg-prc-cpg/dsh-weknora适用于 DeepSeek Harness (dsh) 的 WeKnora 知识检索工具:通过自有知识库进行语义搜索、文档阅读以及 RAG/代理回答。Mnemondsh-mnemon面向 DeepSeek Harness 的可组合三层记忆控制平面:持久化运行时上下文、可搜索的项目文档、可插拔的长期记忆、受保护的策略、WebUI 和无头工具。
最新版
0.1.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
88.7 kB
文件数
7
Surface
any
许可证
MIT
发布源
npm
GitHub
★ 0
周下载
179
安全扫描
✓ v0.1.1 扫描通过
查看源码 ↗项目主页 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录

README

MemOS Cloud DeepSeek Harness Plugin (Lifecycle)

Official plugin maintained by MemTensor.

English | 中文

A lifecycle bundle for DeepSeek Harness that recalls relevant memories from MemOS Cloud before the model starts the current turn and adds the completed user/assistant turn back to MemOS Cloud afterward.

Features

  • Recall: before the first model step of every user turn → /search/memory
  • Add: after that turn ends with completed → /add/message
  • Deterministic filters: user, public, knowledge-base, metadata, tags, and static or preset-based agent isolation
  • Lifecycle-native: memory is automatic; the model does not decide whether to call a memory tool
  • Fail-open: MemOS errors never interrupt the Harness turn
  • Safe capture: excludes system prompts, reasoning, attachments, and plugin context; tool calls/results are included only when includeToolMemory is enabled
  • Uses Token auth (Authorization: Token <MEMOS_API_KEY>)

Install

The following commands install the plugin into DeepSeek Harness's default web profile.

Option A — NPM (Recommended)

dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@latest

If DSH is not installed globally:

npx @deepseek-ai/dsh plugin --profile web add @memtensor/memos-cloud-dsh-plugin@latest

Option B — Package from Source

Run from the monorepo repository root. Install the workspace dependencies, then create the versioned .tgz; packaging does not add the plugin to DSH.

pnpm install --frozen-lockfile
pnpm pack:dsh
dsh plugin --profile web add ".\packages\dsh\artifacts\memtensor-memos-cloud-dsh-plugin-$(node -p "require('./packages/dsh/package.json').version").tgz"

If DSH is not installed globally:

npx @deepseek-ai/dsh plugin --profile web add ".\packages\dsh\artifacts\memtensor-memos-cloud-dsh-plugin-$(node -p "require('./packages/dsh/package.json').version").tgz"

The install command derives the tarball filename from packages/dsh/package.json, so it remains valid after a version change. lib/ is build output; the installable package is the .tgz file under artifacts/.

Remove

dsh plugin --profile web remove @memtensor/memos-cloud-dsh-plugin

If DSH is not installed globally:

npx @deepseek-ai/dsh plugin --profile web remove @memtensor/memos-cloud-dsh-plugin

Start or Restart DSH Web

After installing or removing the plugin, restart DSH Web to reload the web profile. If it is already running, press Ctrl+C in its terminal, then start it again:

npx @deepseek-ai/dsh web

Configuration

1. API Key and User ID via .env (Recommended)

Create a MemOS API key at MemOS Dashboard.

Create or edit ~/.dsh/.env in the DSH configuration directory:

MEMOS_API_KEY=mpg-your-key
MEMOS_USER_ID=your-stable-user-id

Use a stable, distinct MEMOS_USER_ID for each user's memories. The plugin uses this same ID for both recall and add. If it is omitted, the default is deepseek-harness-user.

DSH reads ~/.dsh/.env by default. It also reads .env from the directory where you run the dsh command, which takes precedence.

Restart DSH after changing .env; its environment values are loaded at startup.

Alternatively, store the API key in ~/.dsh/.credentials.yaml under refs. Add it to the existing mapping and preserve other credentials and records:

version: 1
refs:
  MEMOS_API_KEY: mpg-your-key
records: {}

Configure the user ID using either MEMOS_USER_ID in .env or memos-cloud.userId in settings.yaml, described below.

2. Plugin Settings

DSH plugin settings file: ~/.dsh/settings.yaml

Minimal config

memos-cloud:
  apiKeyEnv: MEMOS_API_KEY

Keep the API key and user ID in .env as shown above; configure ordinary plugin options such as baseURL, recall, and add in settings.yaml.

Configuration precedence

For an option with multiple supported sources, precedence is, highest first: values entered directly in settings.yaml → inherited process environment → credentials in ~/.dsh/.credentials.yaml → launch-directory .env → ~/.dsh/.env → plugin defaults.

The credentials file applies only to the API key. Set apiKeyEnv to the credential name (default: MEMOS_API_KEY), and store the actual key in .env or .credentials.yaml.

Optional config

  • apiKeyEnv (default: MEMOS_API_KEY; Harness credential reference)
  • baseURL (default: https://memos.memtensor.cn/api/openmem/v1; MemOS API root)
  • userId (default: MEMOS_USER_ID, then deepseek-harness-user; stable shared read/write user namespace)
  • recallEnabled (default: true; search before the first model step of each user turn)
  • addEnabled (default: true; add after the current turn ends with completed)
  • includeAssistant (default: true; include assistant text in add)
  • includeSubagents (default: false; process sessions with origin: subagent)
  • multiAgentMode (default: false; use the stable DSH agentPreset as agent_id, falling back to agentId when no preset exists)
  • queryPrefix (default: empty; text prepended to every recall query)
  • recallGlobal (default: false; omit conversation_id and search the user's memories globally)
  • memoryLimitNumber (default: 6; factual result limit, 1..25)
  • preferenceLimitNumber (default: 6; preference result limit, 1..25)
  • includePreference (default: true; recall preference memories)
  • includeToolMemory (default: false; recall tool memories and add correlated tool calls/results)
  • toolMemoryLimitNumber (default: 6; tool-memory result limit, 1..25)
  • relativity (default: 0.45; semantic threshold, 0..1)
  • filter (optional; ordinary or per-source deterministic filter)
  • knowledgebaseIds (default: []; KB IDs to search; all cannot be mixed with concrete IDs)
  • tags (default: [deepseek-harness]; tags for add)
  • info (default: {}; non-blank string metadata)
  • agentId (optional; add and constrain the user search branch)

How It Works

  • Recall (agent/pre-step): on the first model step of each direct user turn, the plugin calls /search/memory and inserts the results before the user message.
  • Add (turn/end): after a turn ends with completed, the plugin sends the user text, optional assistant text, and—when enabled—correlated tool calls/results to /add/message.
  • MemOS failures do not interrupt the Harness turn. Subagent sessions are excluded unless includeSubagents is enabled.

Shared MemOS API behavior

The private workspace core is also used by the OpenClaw adapter. DSH therefore uses the same Authorization: Token client, request validation, filter construction, timeout handling, retry bounds, safe serialization, response validation, and MemOS tool-message wire types. Search can request factual memories with memoryLimitNumber, preferences with includePreference and preferenceLimitNumber, and tool memories with includeToolMemory and toolMemoryLimitNumber. The response projector keeps these categories separate before DSH inserts the resulting untrusted JSON context.

knowledgebaseIds and filter constrain /search/memory. tags, info, agentId, appId, allowKnowledgebaseIds, asyncMode, and allowPublic are applied to /add/message when configured. maxQueryChars, maxRecallChars, maxItemChars, and maxMessageChars bound text before it crosses the MemOS or host boundary. searchRetries and addRetries remain independently configurable because recall and write failures have different host impact.

DSH adapter boundary

The shared core does not contain DSH lifecycle code. This package alone owns the Cordis credential/settings services, agent/pre-step and turn/end subscriptions, session-to-conversation mapping, DSH message/tool conversion, preset-based agent attribution, capture policy, prompt insertion, and serialized write queue. OpenClaw-only configuration UI, per-agent overrides, and model-based second-pass recall filtering are not implied by the shared MemOS API layer.

When multiAgentMode is enabled, both search and add use session.header.agentPreset as agent_id. DSH deployments such as the headless profile may create sessions without a preset; those sessions use the explicitly configured agentId, or omit agent_id when no fallback is configured. A subagent joined to its parent's preset shares that preset-level memory partition while keeping its own conversation_id.

Because the preset selects agent_id per Session, do not also set a fixed agent_id inside filter when multiAgentMode is enabled; configuration validation rejects that conflicting combination.

Compatibility

  • DeepSeek Harness: tested with 0.1.2-rc.1 and 0.1.0-rc.6
  • Node.js: ^22.19.0 || >=24.0.0
  • MemOS Cloud API: /api/openmem/v1

Harness is a developer preview. Re-run the full tests and a live smoke after upgrading it.

Security and Privacy

  • Recall JSON escapes < and is labeled untrusted, read-only background data.
  • Instructions, permission claims, and tool requests inside memory are never executed by the plugin.
  • The plugin never uploads cwd, full configuration, system prompts, reasoning, plugin-injected context, or attachment bytes. Tool arguments and textual results are uploaded only when includeToolMemory is enabled; non-text results use an omission marker, and an over-budget argument omits its whole correlated tool pair instead of emitting invalid JSON.
  • Original DSH message IDs and event timestamps are preserved.
  • Public writes remain disabled unless allowPublic is explicitly enabled.
  • Warnings omit API keys, authorization headers, and request bodies.
agent_id
  • appId (optional; add app_id; not an automatic search filter)
  • allowKnowledgebaseIds (default: []; KB IDs allowed for writes)
  • maxQueryChars (default: 4000; search query character budget)
  • maxRecallChars (default: 12000; total recalled-text budget)
  • maxItemChars (default: 2000; per-item recalled-text budget)
  • maxMessageChars (default: 12000; per-message add budget)
  • timeoutMs (default: 5000; HTTP timeout, 100..60000 ms)
  • searchRetries (default: 1; extra search attempts, 0..3)
  • addRetries (default: 0; extra add attempts, 0..3)
  • allowPublic (default: false; allow generated memories to enter the public project store)
  • asyncMode (default: true; ask MemOS to process added messages asynchronously)