dsh-dejavu-memory

dsh-dejavu-memory

Renamed: former npm/GitHub package dsh-noc-memory → dsh-dejavu-memory. Prefer this package; deprecate the old name when publishing.

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

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

There is also a ChatGPT and Codex plugin, dejavu-memory — the same memory server, but with an interactive knowledge graph of the tree inside the chat client. This plugin stays tool-only.

English · 中文

Tools

tool	what it does
dejavu_boot	load at session start: system://boot, system://recent/5, system://triggers, then best-effort system://briefing; afterward read system://focus (recent is a briefing subset — no need to re-read it after boot)
dejavu_read	read a memory by URI (system://…, dejavu://agent, …)
dejavu_search	search memories (semantic + keyword / trigger recall via search_memory)
dejavu_create	create a memory node ([Baseline]/[Deviation]/[Result]/[Reusable judgment])
dejavu_update	full replace, patch (old_string/new_string), or append; optional relation
dejavu_delete	delete a memory by URI (delete_memory)

Quick start

dsh plugin --profile web add dsh-dejavu-memory

Requires your own DejaVu server — deploy it to Cloudflare in minutes: DejaVu.

- id: dejavu
  name: dsh-dejavu-memory
  config:
    mcp_url: https://dejavu.example.com/mcp
    mcp_auth: ""  # prefer mcp_headers for Access service token

For a server behind Cloudflare Access (e.g. dejavu.example.com), use the service token headers instead of mcp_auth:

- id: dejavu
  name: dsh-dejavu-memory
  config:
    mcp_url: https://dejavu.example.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 DejaVu MCP endpoint (Streamable HTTP)
mcp_auth	no	legacy; prefer mcp_headers for Cloudflare Access service token
mcp_headers	no	extra headers merged into every MCP request (e.g. Cloudflare Access service token)

Upgrading from dsh-noc-memory: package renamed to dsh-dejavu-memory. Remove the old plugin and re-add; point config id at dejavu.

Why dejavu_* (not noc_*)?

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

License

MIT

Related

• DejaVu — the Cloudflare MCP memory server this plugin talks to
• dejavu-memory for ChatGPT and Codex — same memory server, with an interactive knowledge graph
• pi-dejavu-memory — same memory tools for Pi
• DejaVu_memory — upstream project