chenzheshushi-commits/dsh-evolve

C2

Self-evolving memory + skill lifecycle for DeepSeek Harness — durable cross-session memory with zero-token deterministic recall, tiered approval, reinforcement learning from repetition, and anti-bloat

★ 5+ · chenzheshushi-commits/dsh-evolve source on GitHub · this plugin in the registry

chenzheshushi-commits/dsh-evolve is a DeepSeek Harness plugin rated C2 — one powerful capability or sensitive behavior. It patches the dsh runtime, can rewrite the system prompt, command execution in build output only, executes commands in development tooling the package does not ship.

Installable plugin — declares a dsh.bundle manifest

What it can do

CapabilityFlagEvidence
patches the dsh runtimeruntime_patch./cordis.patch.yml
can rewrite the system promptprompt_surfaceapproval, systemPrompt, webServer
command execution in build output onlyexec_bundled×21 in build output only, e.g. lib/index.js:24, lib/index.js:24
executes commands in development tooling the package does not shipexec_tooling×12 in development tooling the package does not ship, e.g. scripts/harness-boot-check.mjs:23, scripts/harness-boot-check.mjs:23
starts a network server in development tooling the package does not shipnet_server_tooling×1 in development tooling the package does not ship, e.g. scripts/harness-boot-check.mjs:102

Services it injects

approval llm settings slots storageDomain systemPrompt tools webServer

Hooks it attaches

agent/error agent/pre-step loader/volatile-update session/event

Environment variables it reads

DSH_HOME EVOLVE_DB

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.