DSH Context vs Mnemon
These two listings overlap in this directory — they share a category or a use case, so they are candidates for the same job. Below is every field this directory checked, side by side: verification level, security scan, compatibility target and install command. Under the table: editorial notes on when to pick each side, and when neither is the right install.
DSH Context
bowenliang123
Context dashboard, browser and command that show how the context window is composed and how it evolves.
Read the listingMnemon
mnemon-dev
LLM-supervised persistent memory with graph-based recall, cross-session stores and a single native binary.
Read the listing| Field | DSH Context | Mnemon |
|---|---|---|
| Verification | L3 · Install spec | L2 · Structured |
| Security scan | Unverified | Unverified |
| Health | Active | Active |
| dshTarget | 0.1.2-rc.1 || 0.1.3-alpha.2 || 0.1.5-rc.1 | — |
| Last checked | 2026-09-18 | 2026-09-18 |
| Licence | Apache-2.0 | Apache-2.0 |
| Language | TypeScript | Go |
| Stars (context only) | 1,430 | 587 |
| Categories | Memory & Context, Development & Operations | Memory & Context |
| Use cases | Memory & Context | Memory & Context |
| Install command | dsh plugin --profile web add dsh-context | dsh plugin --profile web add github:mnemon-dev/mnemon |
Every row is a public field of the two listings. This page does not score plugin quality.
Scenario notes
Do not collapse these into one “memory” pick. Context answers what is in the window now, how it is composed, and when compaction fired. Mnemon is long-term recall: graph-backed, cross-session, LLM-supervised so trivia does not flood the store. The failure modes are different, so the correct install is usually both — Context for visibility, Mnemon for survival across sessions.
When to pick DSH Context
Choose Context when the pain is “I cannot see why the model forgot” or when sessions run past an hour and window hygiene becomes maintenance. Composition views and compaction event logs turn context tuning from guesswork into measurement.
When to pick Mnemon
Choose Mnemon when nothing durable survives the next session and you want supervised writes into a cross-session store. Pin versions while the snapshot schema is still settling; approval gates on writes are the feature that separates it from dump-everything memories.
When neither fits
A single plugin that claims both must prove bounded retrieval and gated writes before you trust it. Star counts do not separate observational tooling from a real memory store. If your model already has strong long-context behaviour, start with Context and add Mnemon only when cross-session recall is the actual gap.
Which to pick
- DSH Context carries the higher verification level (L3 vs L2), meaning its install path was exercised further.
- They declare different harness targets (0.1.2-rc.1 || 0.1.3-alpha.2 || 0.1.5-rc.1 vs undefined); the older target may simply not have caught up with the current preview line.
- DSH Context has the larger community (1,430 stars), though star counts measure attention rather than safety or quality.
- DSH Context is published to npm and installs by package name, while Mnemon installs the way its own documentation specifies.
Questions
- Are DSH Context and Mnemon interchangeable?
- They overlap in what they do (they share at least one category or use case), but they differ in install path and how far they were checked: DSH Context is L3, Mnemon is L2. Confirm the install command in the table above, then try it in an isolated profile.
- Which one is more current?
- DSH Context was checked more recently (2026-09-18 against 2026-09-18). That date is when this directory last verified the listing, not when the plugin last shipped a release.
- Can I install both?
- Sometimes — if they do not fight for the same tool name or UI slot. DSH Context is unverified and declares 0.1.2-rc.1 || 0.1.3-alpha.2 || 0.1.5-rc.1; Mnemon is unverified and declares no harness target. A later install that re-registers the same capability can silently override the first. Safer path: try each in an isolated profile, compare the registered tools, then combine only what does not collide.