icearia0219/dsh-memory-spaces

Scoped memory spaces for DSH: you pick which sessions donate memories, which sessions consume them, and what reaches the model.

Gives selected Sessions durable memory without pooling every conversation into one global store. A space is an explicit membership object: Sessions that contribute to it and Sessions that may use it are separate relationships, so injection follows membership instead of "the model remembers everything." Governance is deliberately human-side — creating spaces, changing relationships, lifecycle decisions, importing history, clearing provenance and destructive deletion each require a human UI action or a direct human command, and the plugin exposes no model tool for any of them. Injection is reviewed rather than silent: automatic matches stay removable in the composer, and in confirmation mode only the candidates you select are injected. Every memory version records its space, lifecycle status, version chain, source Session id and title, source event range, creation time, whether it was manual or model-extracted, the retained source-message excerpts and the recent answers that received it; creating a new version marks the former one superseded rather than overwriting it. A manager UI keeps those versions and their provenance visible while sources and consumers stay distinct, and /memory commands cover the same operations from the keyboard.

Memory ★ 2
View on GitHub ↗

Install

dsh plugin --profile web add dsh-memory-spaces@0.1.1

The README's Quick start line, and it pins the exact version on purpose — the author writes that version 0.1.1 is the release with fresh-install compatibility evidence. The README also documents a GitHub form (dsh plugin --profile web add github:icearia0219/dsh-memory-spaces) and a local-checkout form (dsh plugin --profile web add .). Removal is explicit about what stays behind: dsh plugin --profile web remove dsh-memory-spaces disables the plugin but leaves its profile-local SQLite database and backups in place, and there is no separate runtime disable switch. Upgrading is not a hot swap — the README says to stop the Web process and back up the database first, then add the intended exact version again, run dsh --profile web --dump-config, restart Web, and exercise a synthetic save-and-recall flow.

Compatibility

The README states the package targets stock DSH aggregate releases >=0.1.5-rc.3 <0.2.0, with fresh-install compatibility evidence for 0.1.5-rc.3 and 0.1.7-rc.2, and points at docs/DSH_COMPATIBILITY.md for the exact evidence rather than a blanket claim. On the host side it needs the ctx.agents, ctx.commands and ctx.llm services, opens a schema-versioned SQLite database and maintains an FTS5 trigram index of active memory versions. The author is open about the gap between the automated matrix and real installations: this release asks for install and workflow reports across Windows, macOS and Linux and across release-candidate versions inside the declared range, and there is a dedicated installation-feedback issue template. Storage keeps sensitive-content warnings before dialogue, history summaries or snapshots are saved, but the README says users remain responsible for secrets and for provider retention.

Details

Alternatives

Luisarg03/dsh-memory-vault · WYR-233/dsh-memory-lite · adithyanraj03/dsh-memory-recall

More plugins in Memory

Browse more in Memory

Guides for Memory plugins