foreveryoungpp/dsh-gentle-engram

HTTP-native Engram memory for DSH: native mem_* tools, recall pulled on demand, and per-session memory that outlives a compaction.

Gives DSH persistent project memory that is pulled rather than pushed. A static protocol is injected into every request, but nothing is fetched or injected at session start — the model asks with mem_context or mem_search, and the mem_* tool surface is registered through ctx.tools.register so its schemas, output shape and error handling live and are tested in this repository. Prompts and tool learnings are captured as the session works, and after a compaction a one-shot recovery notice is the only automatic thing that happens, which is what keeps a session's memory alive across the boundary without polluting every turn. Session identity is attached to every operation, and the session key has a defined end: an explicit end is the only thing that sets ended_at, work that continues afterwards is not lost, and the next write detects the closure rather than reopening the closed key. Credential handling is a marked-text convention, and the README says so — it will not detect secrets you did not mark.

Memory ★ 0
View on GitHub ↗

Install

dsh plugin --profile web add @ian_p/dsh-gentle-engram

The npm line. It is the 0.2.0 rewrite: version 0.1.x bridged Engram's MCP server, an approach its own docs/DESIGN.md records as unsalvageable, so the current plugin talks to engram serve over HTTP and inserts no MCP row. That makes the pairing explicit — a local Engram server has to be running (engram --version is the check), and ENGRAM_URL points at a different instance if it is not this machine's. The README adds a warning that matters if you came from 0.1.x: do not also keep a second Engram MCP row, because two rows with the same serverName in one scope is the conflict it removed.

Compatibility

Needs a reachable Engram server and the session API the rewrite was built against — the README notes that 0.2.0 replaced the agent/session-start event the earlier design warmed. Project resolution is read-only and happens once per session via GET /project/current?cwd= with that session's own working directory, so the answer belongs to this session rather than to a shared child process, and it gates both writes and recall. A server whose identity does not match this machine's own Engram instance is refused rather than adopted. Sensitive routes that can import or modify data are explicit-only; the plugin never falls back to them.

Details

Alternatives

skepsun/dsh-engram · OverDustD7/dsh-experience-recall · spicycorn/dsh-context-sniper

More plugins in Memory

Browse more in Memory

Guides for Memory plugins