DeepSeek Harness Plugin Hub

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

探索

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

社区

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

相关链接

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

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

Plugin Memory — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
P

@deepseek-ai/dsh-plugin-memory

Plugin Memory

适用于 DeepSeek Harness 的持久化五层记忆系统(条目注入、相关性检索、智能体工具和基于 LLM 的自动提取)。

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

npx -y @deepseek-ai/dsh plugin --profile web add github:NattoCB/dsh-plugin-memory#468f2a8f36f256fe90d6a97d43e68b639c21436a
README兼容性版本

兼容性与来源证明

Plugin Memory 以 @deepseek-ai/dsh-plugin-memory 发布,当前版本为 0.1.0-rc.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

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

版本

0.1.0-rc.1prerelease
2026/8/20

相关插件

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

Memsearch Dsh@zilliz/memsearch-dsh适用于 DeepSeek Harness 的 MemSearch 插件:在多个代理之间共享 Markdown 记忆,支持捕获、步骤前上下文注入、记忆召回技能和技能候选审核面板。Reme@agentscope-ai/reme面向 TypeScript 代理的 ReMe 客户端和记忆集成Stratagate Dshstratagate-dsh最近的对话依然鲜活。较早的对话会逐渐淡化为摘要,而不是被遗忘。StrataGate 为 DeepSeek Harness 提供六层、随时间衰减的记忆,同时将持久的事件和关系沉淀为知识图谱。将你在其他 AI 中的记忆带来Meow Memorymeow-memoryDeepSeek Harness 的跨会话项目记忆:七层 SQLite 记忆、首轮快照注入、每条消息的关键词命中、memory_remember/search/project 工具、带 reflection-fold UI 的自动反思,以及由空闲触发的梦境整合
最新版
0.1.0-rc.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
MIT
发布源
github
GitHub
★ 3
周下载
0
最近提交
2026/8/21
查看源码 ↗
README Badge

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

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

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

认领这个 Plugin →
报告问题

README

@deepseek-ai/dsh-plugin-memory

English | 中文

Persistent five-layer memory for DeepSeek Harness: profile, project context, daily log, and recallable topics — so the agent remembers you across sessions, not just within one.





Two cordis seams — agent/pre-step injection + ctx.tools.register (six tools)

A persistent five-layer memory system for DeepSeek Harness (DSH): a user profile (L1), a per-project semantic index with topic files (L2), and append-only per-day logs (L3) under ~/.dsh/memory/ and <cwd>/.dsh/memory/. It injects relevant memories into every request and auto-extracts durable facts from finished sessions via the LLM. Integrates as a DSH plugin on two cordis seams — agent/pre-step for injection, ctx.tools.register for six memory_* agent tools. Without an llm route it still works: entry injection, keyword relevance, and profile rotation remain; only LLM ranking and auto-extraction are disabled.

✨ Features

  • 🧠 Five-layer model: L0 user-owned identity (~/.dsh/AGENTS.md, not managed by the plugin) → L1 profile → L2 project index + topics → L3 per-day append-only log → L4 skills (existing). Each layer has its own write path, truncation budget, and injection rule.
  • 📇 Index + topic split (L2): MEMORY.md is always an index of one-line pointers (≤150 chars each); details live in <topic>.md. Keeps single files small, searchable, and truncatable.
  • ✂️ Truncation budget: the booted index is hard-clamped to 200 lines / 40,000 chars, so cold-start context stays cheap.
  • 🎯 Relevance injection: on each step, the latest user query selects relevant topic files (LLM ranking when llm is configured, keyword scoring otherwise) and appends them as a <system-reminder data-role="memory"> block; files already surfaced in this session are de-duplicated. The two channels are labeled memory-entry (once per session) and memory-relevance (per step) in the GUI context rows.
  • 🤖 LLM auto-extraction: when a session goes idle, a debounced (60 s) best-effort pass scans the recent 40 events, asks the LLM for new topic files and index lines, and writes them. Never overwrites existing memories; degrades silently if the model is unavailable.
  • 🔄 Profile rotation (L1): memory_profile merges new facts into four fixed sections (工作背景 / 个人背景 / 当前关注 / 近期动态) and rotates the version, keeping the previous copy in profile.md.bak.
  • 🔒 Read-back data, not instructions: memory is written with fs/promises directly to the memory roots — intended persistence, not self-modification — and paths are confined to the store root. Memory files are context the agent reads back, never permission grants.
  • 🧩 Pure harness plugin: no HTTP API or GUI panel — injection and tools only. DSH serves a single user, so paths carry no <uid> layer.
  • 🛠️ Six agent tools registered via ctx.tools.register (defineTool from @deepseek-ai/dsh-tools):
  • ToolScopeEffect
    memory_writeglobal/projectWrite/overwrite a topic file; optionally add an index line.
    memory_readglobal/projectRead a topic file or the MEMORY index.
    memory_searchglobal/project/bothKeyword-search topic files.
    memory_dailycwdAppend a dated line to <cwd>/.dsh/memory/YYYY-MM-DD.md.
    memory_forgetglobal/projectDelete a topic file and its index pointer.
    memory_profileglobalRead, or merge-and-rotate, the single-user profile.

    Quick Start

    Prerequisites

    • A DeepSeek Harness (DSH) installation with a plugin-capable profile (e.g. web).
    • No LLM route required — the plugin falls back to keyword-only relevance.

    Install

    dsh plugin --profile web add github:NattoCB/dsh-plugin-memory
    

    Run

    Restart dsh web. On first use the plugin bootstraps both memory roots:

    ~/.dsh/memory/
      MEMORY.md        # global index (≤200 lines / 40K chars)
      profile.md       # L1 profile (Version N)
      profile.md.bak   # previous profile version
      <topic>.md       # global topic files
    <cwd>/.dsh/memory/
      MEMORY.md        # project index
      YYYY-MM-DD.md    # daily memory (append-only)
      <topic>.md       # project topic files
    

    Tell the agent something worth remembering, or let idle auto-extraction pick it up — then check the memory roots a session later.

    Configuration

    Deploy the plugin via a DSH bundle entry (see cordis.patch.yml and package.json exports):

    KeyDefaultMeaning
    enableEntryInjectiontruePrepend the how-to-save + index block once per session.
    enableRelevancetrueAppend relevant topic files per step (data-role=memory).
    enableExtractiontrueIdle-time LLM auto-extraction.
    maxRelevant5Max files surfaced per step (1–20).
    relevanceTopK8Max candidates the LLM selector may pick from (1–40).
    relevanceBudgetChars2000Per-topic char cap fed to relevance selection (≥200).
    extractionDebounceMs60000Idle debounce before an extraction pass runs.
    extractionLookback40Recent events scanned per pass (5–200).
    llm.provider""Provider for extraction / relevance ranking (empty → keyword-only).
    llm.model""Model for extraction / relevance ranking.
    llm.maxTokens1024Completion token cap for LLM calls.

    Example entry:

    - id: memory
      name: '@deepseek-ai/dsh-plugin-memory'
      config:
        enableEntryInjection: true
        enableRelevance: true
        enableExtraction: true
        maxRelevant: 5
        relevanceTopK: 8
        relevanceBudgetChars: 2000
        extractionDebounceMs: 60000
        extractionLookback: 40
        llm:
          provider: deepseek   # example: fill in your route
          model: deepseek-chat
          maxTokens: 1024
    

    License

    MIT — see LICENSE.


    Open an issue · Source