RealAlexandreAI/dsh-noc-memory 预览 preview

RealAlexandreAI/dsh-noc-memory

插件Plugin 原生Native ⭐ 2 MIT

Connects DeepSeek Harness to Noc Memory: session-start boot + daily briefing, plus memory read / search / create / update, backed by your own Noc Memory MCP server on Cloudflare.

catalog 简介 / catalog descriptioncatalog description:dsh memory: Nocturne Memory client for DeepSeek Harness

项目介绍Project Overview

dsh-noc-memory 将 DeepSeek Harness 连接至 Noc Memory,提供会话启动引导、每日简报及记忆读写搜索更新,基于自部署的 Cloudflare MCP 服务器。适合需要长期记忆的会话场景。注意:需自行部署 Noc Memory 服务器并配置 mcp_url。

dsh-noc-memory connects DeepSeek Harness to Noc Memory via your own Cloudflare-hosted MCP server. It provides session-start boot, daily briefing, and memory read/search/create/update tools. Use it when persistent memory across sessions is needed. Caveat: requires deploying and configuring your own Noc Memory server with mcp_url.

或使用命令行安装(适合开发者)Or use CLI install (for developers)

命令行安装CLI Install

dsh plugin --profile web add dsh-noc-memory

RealAlexandreAI/dsh-noc-memory 加入你的 DSH 配置(web profile)即可启用。

READMEREADME

dsh-noc-memory — long-term memory for DeepSeek Harness

dsh-noc-memory

Connects DeepSeek Harness to Noc Memory: session-start boot + daily briefing, plus memory read / search / create / update, backed by your own Noc Memory MCP server on Cloudflare.

Port of pi-noc-memory — same protocol, same tool names.

English · 中文

Tools

tool what it does
noc_boot load at session start: core memories + recent context + glossary
noc_briefing today's working-memory briefing (system://briefing) — recent activity, expiring, cold candidates
noc_read read a memory by URI (system://…, noc://agent, …)
noc_search search memories by keywords (trigger recall first, then FTS)
noc_create create a memory node ([Baseline]/[Deviation]/[Result]/[Reusable judgment])
noc_update patch (old_string/new_string) or append to a memory; optional relation evolution marker

Quick start

dsh plugin --profile web add dsh-noc-memory

Requires your own Noc Memory server — deploy it to Cloudflare in minutes: cf-noc-mem.

- id: noc-memory
  name: dsh-noc-memory
  config:
    mcp_url: https://mem.example.com/mcp
    mcp_auth: Bearer <your token>

For a server behind Cloudflare Access (e.g. noc-mem.slahser.com), use the service token headers instead of mcp_auth:

- id: noc-memory
  name: dsh-noc-memory
  config:
    mcp_url: https://noc-mem.slahser.com/mcp
    mcp_headers:
      CF-Access-Client-Id: <your client id>
      CF-Access-Client-Secret: <your client secret>
key required meaning
mcp_url yes your Noc Memory MCP endpoint (Streamable HTTP)
mcp_auth no Bearer <token> if the server requires it
mcp_headers no extra headers merged into every MCP request (e.g. Cloudflare Access service token)

Upgrading from dsh-nocturne-memory (≤0.1.x): renamed to dsh-noc-memory, tools renamed nocturne_*noc_*. Remove the old plugin and re-add the new package; update any prompt text referencing nocturne_* tools.

Why noc_* (not nocturne_*)?

Some agents probe read_mcp_resource before reaching for a memory tool, wasting a round trip (upstream issue #32). Explicit noc_boot / noc_read naming in the tool list and boot-protocol prompt steers models straight to the right tool — no resource shim required.

License

MIT

Related

上一个 Prev dsh-side-monitor 下一个 Next dsh-airp