Memtrace for DeepSeek Harness

The code intelligence graph, as a DeepSeek Harness plugin.
Structural search · blast radius · temporal memory · 27 agent skills

English · 简体中文

---

What you get

One dsh plugin add wires Memtrace into DeepSeek Harness:

Surface	What the agent sees
MCP tools	mcp__memtrace__find_symbol, mcp__memtrace__find_code, mcp__memtrace__get_impact, mcp__memtrace__get_evolution, mcp__memtrace__get_symbol_context, … — the full Memtrace graph, namespaced by the official DSH MCP client
Skills	27 Agent Skills (memtrace-first, memtrace-search, memtrace-impact, memtrace-codebase-exploration, fleet coordination, …) registered on ctx.skills
Local-first	The graph lives on your machine. No cloud index. No repo upload.

Ask the agent: "Index this repo, then show me the blast radius of apply."

It should call Memtrace — not grep.

Quick start

dsh is the DeepSeek Harness CLI (@deepseek-ai/dsh). Install that first — this plugin does not ship it.

# once
npm install -g @deepseek-ai/dsh

# then add Memtrace
dsh plugin --profile web add github:syncable-dev/dsh-plugin-memtrace

# no global install? same command via npx:
npx -y @deepseek-ai/dsh plugin --profile web add github:syncable-dev/dsh-plugin-memtrace

# 2. Restart the profile and confirm the layer
dsh --profile web --dump-config | grep -A4 'id: dsh-plugin-memtrace'

First launch may take a minute while npx memtrace mcp fetches the Memtrace binary. Pin a local install to skip that:

npm install -g memtrace
export MEMTRACE_BIN=memtrace

Then open the Web UI and index the workspace:

Use Memtrace to index this directory, then give me an architecture briefing.

Install & uninstall

Channel	Command
Git (main)	dsh plugin --profile web add github:syncable-dev/dsh-plugin-memtrace#main
npm	dsh plugin --profile web add dsh-plugin-memtrace
Local checkout	dsh plugin --profile web add ./dsh-plugin-memtrace
Uninstall	dsh plugin --profile web remove dsh-plugin-memtrace

This package is plain ESM — no prepare script, no allowBuilds prompt.

How it works

flowchart LR
  DSH[DeepSeek Harness] --> Bundle[dsh-plugin-memtrace]
  Bundle --> Skills[ctx.skills.register]
  Bundle --> MCP["@deepseek-ai/dsh-mcp-client"]
  MCP --> Server["memtrace mcp"]
  Server --> Graph[(local code graph)]

Two Cordis rows, both owned by this bundle:

1. dsh-plugin-memtrace — reads skills/*/SKILL.md and registers each skill at apply time. Unload disposes them.
2. mcp-memtrace — official MCP client, serverName: memtrace, stdio. MEMTRACE_BIN overrides the command; otherwise npx -y memtrace mcp.

We do not patch the filesystem skill provider's config. That row is last-write-wins; runtime registration does not collide with other skill packs.

Tools the model gets

After MCP discovery, every Memtrace tool is a native DSH tool under mcp__memtrace__*. The ones agents use first:

Tool	Use when
list_indexed_repositories	Check what is already in the graph
index_directory	First contact with a repo
find_symbol / find_code	Locate a function, type, or behavior
get_symbol_context	Callers, callees, community
get_impact	Blast radius before an edit
get_evolution	What changed, and when
recall_decision	Why odd-looking code is there

Full parameter spec: references/mcp-parameters.md.

Skills

Skill	Triggers on
memtrace-first	Any code discovery / "how does this work"
memtrace-index	"index this project"
memtrace-search	"find this function"
memtrace-impact	"what breaks if I change this"
memtrace-evolution	"what changed last week"
memtrace-codebase-exploration	"I'm new here"
memtrace-code-review	PR review
memtrace-incident-investigation	"something broke"
memtrace-fleet-*	Multi-agent coordination

All 27 bundles live under skills/.

Configuration

Variable	Effect
MEMTRACE_BIN	Absolute path or command used instead of npx -y memtrace mcp

Override the MCP row in the profile's cordis.patch.yml if you already run a Streamable HTTP Memtrace endpoint — restate the whole mcp-memtrace config (DSH does not deep-merge).

Compatibility

Surface	Status
Harness	DeepSeek Harness 0.1.0-rc.6+
Node	^22.19.0 || >=24.0.0
Platforms	macOS, Linux, Windows (Memtrace native binary via npm optional deps)
Network	None required after the Memtrace binary is present

Permissions & data

• Spawns memtrace mcp in the session working directory (reads the repo to index; writes .memdb next to the project).
• Registers skills from this package only.
• Does not send code to Memtrace cloud. Local graph.

Topics

dsh · dsh-plugin · deepseek-harness · cordis · memtrace · mcp

License

MIT © 2026 Memtrace / Syncable

Community-maintained Harness plugin. Not an official DeepSeek product.