AI Agent Hub
Back to plugins
🧩

dsh-missher-evolution

admin-security Updated 2026.08.25

Run the following command in DeepSeek Harness:

dsh plugin install Missher12/dsh-missher-evolution

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install Missher12/dsh-missher-evolution inside DeepSeek Harness to install the plugin; source is available at https://github.com/Missher12/dsh-missher-evolution

About this plugin

Every time you open DeepSeek Harness you re-state your preferences and re-correct the workflow, because the model simply does not remember last turn. Missher Evolution tackles exactly that: it distills reusable rules from your direct foreground user turns and promotes them through a three-stage verification pipeline (Candidate to Trial to Active) so that only well-confirmed patterns actually influence future instructions.

All learned state lives under a local $DSH_HOME directory, is schema-validated, and contains no raw user messages, credentials, absolute paths, or provider route names. The learning pipeline is fail-open by design, meaning if the store, classifier, or advisor hiccups a normal Harness step is never rejected. Only direct foreground user turns trigger learning; subagents, tool continuations, scheduled work, and internal plugin messages are all filtered out, keeping the boundary tight.

Built for users who work in DeepSeek Harness Desktop daily and want their personal workflow preferences to compound over time. It improves instruction and workflow reuse rather than fine-tuning or replacing the underlying DeepSeek model, and it does not import or synchronize state across agent hosts.

Use Cases

  • Repeating the same format or workflow corrections in daily conversations instead of stating them each time
  • Promoting rules only after three independent session verifications to prevent accidental matches from polluting instructions
  • Verifying that learned state contains no raw messages or credentials and stays strictly under the local $DSH_HOME directory

Best For

  • Developers who use DeepSeek Harness Desktop daily and want preferences to compound over time
  • Operations admins who need fail-open behavior so component hiccups never block a normal step
  • Privacy-sensitive users who require local-only data isolation and no cross-host synchronization