dsh-noc-memory

September 4, 2026 · View on GitHub

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 / delete, backed by your own Noc Memory MCP server on Cloudflare.

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

English · 中文

Tools

toolwhat it does
noc_bootload at session start: core + recent + triggers (system://boot, system://recent/5, system://triggers) + briefing
noc_readread a memory by URI (system://…, noc://agent, …)
noc_searchsearch memories (semantic + keyword / trigger recall via search_memory)
noc_createcreate a memory node ([Baseline]/[Deviation]/[Result]/[Reusable judgment])
noc_updatefull replace, patch (old_string/new_string), or append; optional relation
noc_deletedelete a memory by URI (delete_memory)

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: ""  # prefer mcp_headers for Access service 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>
keyrequiredmeaning
mcp_urlyesyour Noc Memory MCP endpoint (Streamable HTTP)
mcp_authnolegacy; prefer mcp_headers for Cloudflare Access service token
mcp_headersnoextra 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