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.
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 recall, cross-session knowledge and a single binary install.
Read the listing| Field | DSH Context | Mnemon |
|---|---|---|
| Verification | L3 · Install spec | L3 · Install spec |
| Security scan | Unverified | Unverified |
| Health | Active | Active |
| dshTarget | rc.6 | rc.6 |
| Last checked | 2026-09-09 | 2026-09-06 |
| Licence | Apache-2.0 | Apache-2.0 |
| Language | TypeScript | Go |
| Stars (context only) | 1,305 | 558 |
| 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.
Which to pick
- Both are at verification L3, so the difference is not how far the install was checked.
- DSH Context has the larger community (1,305 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 L3. 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-09 against 2026-09-06). That date is when this directory last verified the listing, not when the plugin last shipped a release.