dsh-memory-pilot
面向 DeepSeek Harness 的决策驱动型记忆编排
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:youluo1230/dsh-memory-pilot#8c04bb7e075a556cb0e68f1a984bd79a3480a978Memory Pilot 以 dsh-memory-pilot 发布，当前版本为 0.3.10。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
Decision-driven memory orchestration for DeepSeek Harness.
English | 简体中文
MemoryPilot decides when an agent needs cross-session memory, which authorized scope to query, and what is worth retaining. It is an orchestration layer—not a memory database. Storage identities and permissions remain under server control.
A memory backend can store and search data, but an agent still needs a policy for when, where, and how to use it. MemoryPilot provides that policy layer across multiple backends and scopes.
Typical use cases:
global, workspace, project, and personal memory scopes.recall and deeper reflect retrieval modes.memory_retrieve and memory_remember agent tools.| Component | Supported | Limitations |
|---|---|---|
| Node.js | >=22 | Earlier versions are unsupported |
| DeepSeek Harness | @deepseek-ai/dsh-llm and dsh-tools >=0.2.0-rc.2 <0.3.0 | Compatibility with DSH 0.3.x is not implied |
| Hindsight | search, reflect, and write through the standard HTTP API | Each binding uses a fixed bank; writes may be asynchronous |
| MemOS local bridge | search and write through memos-local-plugin stdio JSON-RPC | Requires a local plugin installation |
| MemOS local HTTP | search through the local-plugin Viewer API | Search-only; requires a dedicated, isolated instance |
| MemOS Server / Cloud | Not supported | Cube and Cloud APIs require dedicated adapters |
The MemOS adapters target @memtensor/memos-local-plugin, the local core shared by Hermes, OpenClaw, and DSH integrations. They do not implement the self-hosted Cube API or MemOS Cloud API.
POST /v1/systemonePOST /v1/chat/completions with JSON modedsh plugin --profile web add github:youluo1230/dsh-memory-pilot#v0.3.8
Add dsh-memory-pilot to dsh.profile.bundles in the Web profile's package.json:
{
"dsh": {
"profile": {
"bundles": ["dsh-memory-pilot"]
}
}
}
Restart DSH Web unless the profile uses patchReload: "live".
Open Settings → Memory Orchestration (MemoryPilot) and configure:
Configuration changes are applied live. For file-based configuration, start from examples/cordis-patch-minimal.yml.
In the MemoryPilot settings page:
Install the official local plugin if you want to use memos-bridge:
curl -fsSL https://raw.githubusercontent.com/MemTensor/MemOS/main/apps/memos-local-plugin/install.sh \
| bash -s -- --agent dsh --profile web
Review remote installation scripts before running them. The bridge defaults to $DSH_HOME/memos-plugin (normally ~/.dsh/memos-plugin). Set home explicitly only for a legacy Hermes installation or another custom location.
Do not enable both MemoryPilot-managed MemOS capture and another automatic MemOS DSH plugin for the same store unless duplicate recall and retention are intentional.
MemoryPilot complements dynamic backends with a small session-start snapshot:
| File | Scope | Maintenance |
|---|---|---|
$DSH_HOME/SOUL.md | DSH profile | Human-only agent identity and tone |
$DSH_HOME/memory/USER.md | Global | Human editing and controlled agent upserts |
$DSH_HOME/memory/MEMORY.md | Global | Human editing and controlled agent upserts |
$DSH_HOME/memory/projects/<project-key>/MEMORY.md | Git repository | Human editing and controlled agent upserts |
The snapshot is frozen for a session; changes take effect in the next session. SOUL.md contributes trusted persona instructions. USER and MEMORY documents are bounded, untrusted memory data. Automated writes are restricted to a marked managed section and cannot overwrite human-authored notes.
The decision model sees resident memory when deciding whether external retrieval is still needed. For explicit retention, it chooses one authorized target: user profile, global resident memory, project resident memory, or an external backend. It never receives file paths and cannot write SOUL.md.
Edit these documents in Settings → MemoryPilot → Resident memory.
session event
│
▼
capability inventory → decision model → plan validation
│ │
└──────── authorized actions only ─────┘
│
▼
bounded execution and rendering
│
▼
untrusted memory context
| Scope | Intended use |
|---|---|
global | Stable preferences, standing instructions, and cross-workspace history |
workspace | Knowledge shared by repositories in one DSH workspace |
project | Decisions, constraints, attempts, and milestones for the current Git repository |
personal | Private, user-specific long-term memory |
Workspace membership comes from DSH. Project identity is detected from the nearest Git repository under the session cwd. See GLOSSARY.md for precise terminology.
memory_retrieve — retrieves prior memory when a task needs missing historical facts or rationale. In auto mode, SystemOne selects recall versus reflection and the relevant scopes.memory_remember — requests retention of an explicit decision, stable preference, verified fact, or milestone. Policy still determines whether and where it is stored.Credentials, hidden reasoning, transient logs, and unverified claims must not be retained.
decisionKeyEnv, keyEnv, or cookieEnv, not committed to configuration files.pnpm install
npm test
npm run check
Live smoke tests require a configured DSH host. See test/plugin-smoke.mjs and the scripts under scripts/ for their environment requirements.