Feature: natively auto-inject ~/.dsh/memory/ (with MEMORY.md) so a user's markdown memory convention stops being an AGENTS.md-rule-driven soft contract

[etzhe]

📌 更新 / Update — 2026-09-07 15:34 UTC+08:00
Scope clarification: This asks only for a native, opt-in load of the user's markdown memory/ dir + its MEMORY.md index — not a general memory backend (SQLite/graph/vector already have plugins), and not the "preference / correction" layer (e.g. Tacit), which is a separate concern.
Feasibility note: the agent-instructions row already supports per-session paths via an agent preset (see the #519 workaround); the injection seam is already configurable per-session, so a load of memory/ could reuse the same seam.

Summary — Today DSH auto-loads only (a) the instruction-file chain ($DSH_HOME/AGENTS.md + per-directory AGENTS.md/CLAUDE.md (+ .local overlays), content-deduped) and (b) skills. It auto-loads no memory/ dir or MEMORY.md index. Verified in @deepseek-ai/dsh-agent-instructions (lib/index.js:16): DEFAULT_INSTRUCTION_FILE_CANDIDATES=["AGENTS.md","CLAUDE.md"], and grep for MEMORY.md/readMemory/loadMemory returns 0 hits.

Consequence — ~/.dsh/memory/+MEMORY.md is a model-side convention, not a platform mechanism. A memory file is only noticed when an AGENTS.md rule (e.g. "check existing memory before acting") or pointer drives the model to read it. Remove that rule and most memory files go untouched — a soft dependency tied to rules the user happens to keep in AGENTS.md.

What I'd like — A native, opt-in session load of memory/ (global ~/.dsh/memory/ + workspace memory/), including its MEMORY.md index and pointers, analogous to the existing instruction chain. Not a new memory backend (SQLite/graph/vector are already well served by dsh-memory, dsh-statecore, dsh-memory-eternal); just a first-class home for the user's markdown memory convention that doesn't depend on AGENTS.md rules staying intact.

Already searched (per repo rule) — #519 (AGENTS.md not injected in web app), #4749 (context-injection order / prefix cache), #1436 (OpenViking native-memory hub proposal), #5121 & #4638 (persistent-memory plugins). None requests a first-class auto-load of a user's markdown memory/+MEMORY.md index.

---

中文（镜像）

现状 — DSH 目前只自动加载 ①指令文件链（$DSH_HOME/AGENTS.md＋项目根到 cwd 每层 AGENTS.md/CLAUDE.md（＋.local overlay，按内容去重））②skills。不自动加载任何 memory/ 目录或 MEMORY.md 索引。源码依据：@deepseek-ai/dsh-agent-instructions（lib/index.js:16）DEFAULT_INSTRUCTION_FILE_CANDIDATES=["AGENTS.md","CLAUDE.md"]，且全插件 grep MEMORY.md/readMemory/loadMemory 0 命中。

影响 — ~/.dsh/memory/＋MEMORY.md 是模型侧约定，非平台机制。记忆文件只有在 AGENTS.md 规则（如"动手前先查已存记忆"）或指针驱动模型去读时才被注意到；删掉该规则，多数记忆文件就无人问津——这是软依赖，绑在用户自己写在 AGENTS.md 里的规则上。

希望 — 提供一个原生、可选的会话加载位，把 memory/（全局 ~/.dsh/memory/ 与工作区 memory/）连同 MEMORY.md 索引与指针注入，机制与现有指令链一致。不是要新 memory 后端（SQLite/图/向量已有 dsh-memory、dsh-statecore、dsh-memory-eternal 等做好）；只是给用户已有 markdown 记忆约定一个不依赖 AGENTS.md 规则存活的一等落点。

已搜索（按仓库规则） — #519（web app 不注入 AGENTS.md）、#4749（context 注入顺序/前缀缓存）、#1436（OpenViking native-memory hub 提案）、#5121／#4638（持久记忆插件）。无一条请求"原生一级地自动加载用户 markdown memory/＋MEMORY.md 索引"。