Yiipu/dsh-agentmemory
DSH ↔ agentmemory session-memory bridge: mirrors session lifecycle into a local agentmemory daemon (REST), exposes memory_recall / memory_remember tools, and injects a per-session memory context window via agent/pre-step.
Gives every DSH session a persistent, searchable memory backed by agentmemory — a local self-hosted memory daemon. Three surfaces: a write bridge that maps every DSH session event to an agentmemory standard hookType so the daemon's compression pipeline, search index and viewer read real content; a read side that appends sourced user/message rows via the agent/pre-step waterfall (project recall window once per session, optional per-message semantic recall, pre-compaction re-inject); and explicit agent tools memory_recall / memory_remember. It does not modify any @deepseek-ai package and does not touch the shipped preset install directory.
Install
dsh plugin --profile web add github:Yiipu/dsh-agentmemorydsh plugin --profile web add github:Yiipu/dsh-agentmemory (repo Yiipu/dsh-agentmemory; npm 404-verified, GitHub install per README, verified 2026-08-31). Start the agentmemory daemon first (default http://localhost:3111) — the plugin's load gate requires it. Then mount the row from cordis-row.example.yml into a host composition cordis.yml (or a per-session agent preset).
Compatibility
DSH web profile; hard dependency on the local agentmemory daemon (REST API, /agentmemory/livez); fails loudly if the daemon is unreachable — no silent degradation; MIT.
Details
- Repo: Yiipu/dsh-agentmemory
- Category: Memory
- Stars: 3
- Version: repo main (cordis plugin; no npm package)
- Last push: 2026-08-25
- First seen: 2026-08-15
Recent updates
Event-to-hookType observation bridge; pre-step context injection waterfall; memory_recall / memory_remember tools; livez load gate; config via cordis row only.
FAQ
- What happens if agentmemory is not running?
- On load the plugin checks /agentmemory/livez; if the daemon is unreachable or does not report status ok, the plugin fails to load loudly rather than silently degrading.
- What does the write bridge store?
- Every DSH session event is mapped to an agentmemory standard hookType, so the daemon's compression pipeline, search index and viewer all read real content.
- How do I configure it?
- All configuration comes from the plugin's row in cordis.yml (or the file carrying it) — there is no browser UI and no persisted config file. Keys omitted from a row are filled with defaults by Cordis.
Alternatives
Aik358/dsh-auto-memory · KLRSL/dsh-biomemory · Scorp1o117/dsh-tdai-memory