At a glance
What it does
DeepSeek Harness persona cards with per-session/workspace selection and persistent agent memory.
Deepseek Harness Profile
DSH >=0.1.0-rc.7; peer ranges include rc.7, rc.8, rc.1.1, rc.1.2, and rc.1.5 releases
Evidence-verified
Checked Sep 10, 2026, 2:04 PM UTC
Code-evidenced contributions
What it adds to DSH
Adds memory read/write and persona read/update tools for the agent, with memory injected into prompts when enabled.
Mechanism evidence ↗Provides settings for persona cards and workspace mappings, plus a conversation-header selector for per-session persona changes.
Mechanism evidence ↗Before you choose it
Create named Markdown persona cards in DeepSeek Harness settings, choose defaults by workspace or chat, and let the plugin manage associated memory files. It resolves the active persona in session, workspace, default-card order and can inject capped memory into the prompt.
Best for
DeepSeek Harness users who want reusable personas and durable context across chats without manually maintaining persona or memory files.
Common tasks
- Set a default persona card and switch it for a single conversation.
- Assign different personas to different workspaces.
- Let an agent retain task-relevant memory across sessions.
- Migrate the plugin's documented pre-v0.5 file-based card and memory data on first run.
Permissions and data
Uses the DSH settings namespace and plugin-managed local memory files.
Permissions- Registers five agent-facing tools: memory_append, memory_read, memory_rewrite, soul_read, and soul_update.
- Adds a web settings interface and conversation-header persona selector.
- Stores cards, active selections, session choices, and workspace choices in the soul-md settings namespace.
- Creates global and per-card memory files under `$DSH_HOME/soul-md/memory/` on demand.
- Can import the documented legacy card and memory data on first run.
Limitations
- Requires DSH 0.1.0-rc.7 or newer; users of rc.6 must use the documented 0.5.6 package version.
- Unknown `{{...}}` prompt variables in a card have no escape syntax and can fail rendering.
- Injected memory is capped by configuration; the documented default is 8,000 characters from the file head.
What DSHub checked
- Version 0.6.2 has a verified package manifest, Cordis bundle patch, and immutable Git source commit.
- The repository documents tests against DSH 0.1.0-rc.7, 0.1.0-rc.8, and 0.1.1-rc.1.
What DSHub did not check
- Installation and runtime behavior were not executed during this curation.
- The npm package contents were not audited, although registry identity was verified.
Pinned install
Install dsh-soul-md
This plugin bundle does not have a DSH Plugin install action. Use its source documentation for the delivery method.
Maintainer source
Project README
dsh-soul-md
GitHub: Scorp1o117/dsh-soul-md · npm: dsh-soul-md
Part of the DeepSeek Harness Enhancement Suite — Vision · Soul/Persona · Long-term Memory · Plugin Marketplace.
Persona + long-term memory for DeepSeek Harness — zero file management:
In Settings → 人设卡, type a card name and its content, hit save. The plugin manages everything else.
What you get
- Persona cards — the card content is rendered into the system prompt as
the
soul:personasection. Multiple cards are supported; pick a default, and switch per chat from the conversation header (a "人设" select). - Long-term memory — the agent gets five tools:
memory_append/memory_read/memory_rewrite— a persistent memory file (Agent.md / memory.md style). The active persona card has its own memory; otherwise the global memory is used.soul_read/soul_update— the AI reads and evolves its own persona card: when it notices a stable trait, preference, or value of its own, it folds it into the card. It "grows" across sessions instead of resetting every time.- The memory is also injected as a
soul:memoryprompt section (capped) so the agent always sees its memories.
- Resolution per prompt assembly:
session choice (chat switcher) > workspace mapping > default card > none. Switching applies from the next turn — no restart. - Workspace personas (v0.5.2): Settings → 人设卡 lists every workspace with a card dropdown — sessions of that workspace use the assigned card by default (session-level switching still wins). Workspaces come from dsh's durable workspace registry, so no paths to type.
Install
The plugin is a plain Cordis row. Mount it in a profile patch
($DSH_HOME/profiles/<name>/cordis.patch.yml):
- insert:
- id: soul-md
name: 'dsh-soul-md' # after: pnpm add dsh-soul-md in the profile
Then restart dsh web and open Settings → 人设卡: type a name + content, save.
Where things live (you don't need to care, but for reference)
- Persona cards: stored in the
soul-mdsettings namespace (settings.yaml), ascards: { name -> markdown }+active+ per-sessionsessions. - Memory files: plugin-managed under
$DSH_HOME/soul-md/memory/(global.md+ one file per card), created on demand. - Upgrading from ≤ v0.4 (file-based)? The plugin auto-imports the old
pathcard (as "默认") and the old memory file on first run.
Config
| Field | Default | Meaning |
|---|---|---|
cards |
{} |
Persona cards: name → markdown content (managed from the UI). |
active |
'' |
Default card name; empty disables the persona by default. |
sessions |
{} |
Per-session choice (sessionId → card name / none / ''); written by the chat switcher. |
workspaces |
{} |
Per-workspace choice (workspace path → card name / none / ''); written from the settings page. |
workspaceList |
[] |
Read-only workspace list (path + title), maintained by the host from dsh's workspace registry. |
memory.maxBytes |
1048576 |
memory_append / memory_rewrite refuse to exceed this size. |
memory.inject |
true |
Render the memory as the soul:memory prompt section. |
memory.injectMaxChars |
8000 |
Cap for the injected section (from the file head). |
memory.order |
0.5 |
Prompt section order for the injected memory section. |
| legacy fields | — | path, fallback, order, complete, watch, debounceMs, soulMaxBytes, personas, roster, memory.path… kept so old composition entries and settings still validate; only used for the one-time import. |
Notes
- Never write
{{/}}in a card body — they are prompt-variable syntax; unknown variables fail rendering (no escape syntax yet). - Persona/memory sections resolve per assembly, so steady cards stay byte-identical (KV-cache friendly) and edits hot-apply.
- DSH exposes the registered
soul-mdsettings namespace directly; the plugin does not modify files in the host installation. - Suggest putting work-quality rules in the card (e.g. "task quality first") so roleplay never degrades real work.
- Version 0.5.8 and newer require DSH
0.1.0-rc.7or newer and are tested against0.1.0-rc.7,0.1.0-rc.8, and0.1.1-rc.1. - DSH
0.1.0-rc.6users must pindsh-soul-md@0.5.6, the last release carrying the legacy settings-allowlist compatibility patch.
License
MIT
Operate deliberately
Install and manage
Prerequisites and target Profile
Target: Deepseek Harness Profile
Delivery: Dsh Bundle Git — Scorp1o117/dsh-soul-md#84e1cea06a717d402daa233d72d8752ffc29b168。
Verify, update, and remove
Show lifecycle commands
dsh plugin --profile deepseek-harness listCompatibility and access
Requires DSH 0.1.0 Rc.7+; tested through 0.1.1 Rc.1: DSH >=0.1.0-rc.7; peer ranges include rc.7, rc.8, rc.1.1, rc.1.2, and rc.1.5 releases。
Review compatibility evidence ↗
Risk facts
The plugin stores persona cards and persistent memory under the DSH home directory; the agent can update both through registered tools.
Evidence ↗Persona-card content becomes part of the system prompt, and unsupported `{{` or `}}` variables can make rendering fail.
Evidence ↗Evidence and editorial reviewManifest, Bundle patch, distribution and freshness
Immutable evidence
Review status and source activity
Review persona-card content carefully because it is rendered into the system prompt and the agent can evolve personas and persistent memory through plugin tools.
AI reviewed Sep 10, 2026, 2:05 PM UTC。GitHub facts last checked Sep 10, 2026, 2:05 PM UTC。
No material source change has been recorded since this evidence baseline.