Qinling-Melon-Farmers/dsh-memoir
C2DeepSeek Harness (DSH) local-first cross-session project memory: zero bundled runtime deps, bounded cache-friendly Hot Memory, BM25 recall/cache, provenance, lifecycle and bilingual Web GUI; no embedd
★ 10+ · Qinling-Melon-Farmers/dsh-memoir source on GitHub · this plugin in the registry
Qinling-Melon-Farmers/dsh-memoir is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, executes commands in development tooling the package does not ship, starts a network server in development tooling the package does not ship.
Installable plugin — declares a dsh.bundle manifest
What it can do
| Capability | Flag | Evidence |
|---|---|---|
| patches the dsh runtime | runtime_patch | ./cordis.patch.yml |
| can rewrite the system prompt | prompt_surface | systemPrompt, webServer |
| executes commands in development tooling the package does not ship | exec_tooling | ×3 in development tooling the package does not ship, e.g. scripts/compat-swap.mjs:14, scripts/compat-swap.mjs:14 |
| starts a network server in development tooling the package does not ship | net_server_tooling | ×2 in development tooling the package does not ship, e.g. scripts/check-guide-browser.mjs:54, scripts/check-guide-browser.mjs:68 |
Tool registrations
8 confirmed registration point(s); analysis is incomplete.
lib/index.js:237tools.registerlib/tools.js:159tool factorylib/tools.js:297tool factorylib/tools.js:395tool factorysrc/host/index.ts:315tools.registersrc/host/tools.ts:194tool factorysrc/host/tools.ts:337tool factorysrc/host/tools.ts:439tool factorysrc/client/index.tsx:121Context or tools service passed to an unresolved helpersrc/client/index.tsx:122Context or tools service passed to an unresolved helper
Services it injects
sessionProjections slots systemPrompt tools uiWorkspace webServer
Hooks it attaches
agent/disposed tools/result
How to read this
Levels measure capability surface and transparency, not maliciousness. A C3 plugin can be entirely legitimate — a desktop shell genuinely needs subprocesses. The point is that you can see this before installing. See the levels explained and how dsh plugins work.
Findings come from static analysis of shipped code; nothing is executed. Think a flag is wrong? Open an issue — every flag cites the file and line it came from.