How to use dsh-mnemon
Integrates a three
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
dsh-mnemon
— source: plugin_wiki.wiki_content
Install & verify
dsh plugin --profile web add dsh-mnemon
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- Runtime and Documents are local deterministic stores. Mnemon Native is local by default; external Providers are explicit opt-ins.
- Provider credentials are mode
0600under<storageRoot>/state/memory-providers.json. They are never returned to the browser, smart-selection Agent, or Mnemon Pack. - Host calls use argument arrays with shell disabled, bounded output, timeouts, cancellation, schema validation, path boundaries, locks, and revisions.
- Disabling a Provider clears its local catalog metadata but never deletes remote data. Reconnecting rebuilds metadata from the Provider, using local defaults only when a field cannot be mapped.
- Changing scope never migrates, merges, or deletes an old root automatically.
— source: plugin_wiki.readme_en (fallback readme_raw)
FAQ
Do I need to do anything else after installing the plugin? Do I need to install mnemon CLI first?
Yes. Mnemon Native is the default long-term memory engine, and the plugin will invoke the mnemon executable; if the CLI cannot be found, the status page will show unavailable, and all semantic writes and reads will fail. Homebrew, Go go install, or the official Windows ZIP all work. DSH can also explicitly specify the path via MNEMON_CLI_PATH or mnemon.cliPath.
Where is memory data stored? Will I lose it if I switch computers or uninstall the plugin?
Data is stored in the directory selected by storageScope: default global writes to ~/.mnemon (overridable by MNEMON_DATA_DIR), workspace writes to the current session's <cwd>/.mnemon, and custom writes to the absolute path specified by dataDir. Uninstalling the plugin, deleting the plugin directory, or switching scope will not automatically migrate, merge, or delete old data; the original files remain in their original path, and can be moved using the ZIP export/import via "Settings → Memory System → Backup & Migration" when needed.
What's the difference between runtime memory (USER.md / MEMORY.md) and long-term memory (Memory Spaces)?
Runtime memory is minimal Markdown automatically injected into prompts each round by DSH (USER.md for user preferences, MEMORY.md for project conventions), with limits of 4 KiB / 10 KiB respectively, only suitable for the most commonly used high-frequency information; long-term memory resides in external services/databases, recalled on-demand, suitable for cross-session, cross-task facts requiring graph or entity relationships. Document archives sit in the middle, preserving complete designs, retrospectives, flow documents and supporting deterministic full-text search.
If I disable the plugin or set it to read-only, will my memories be cleared?
No. writeEnabled: false only prohibits semantic writes (create/associate/delete/import packages), and is not equivalent to read-only disk - Runtime projection initialization, document recent access time updates, and database migrations triggered by Mnemon reads may still occur. Disabling the service also doesn't delete remote Provider data, only clears the local directory mapping; re-enabling will rediscover from the Provider.
What can each of the nine Providers do? Will the plugin inject features that don't exist?
The plugin strictly exposes functionality based on what the Provider actually declares. For example, Mnemon Native supports full typed graphs, associations, precise writes, and soft deletion; OpenViking writes are asynchronous semantic refinement; Honcho/Mem0/RetainDB have no graph/related/link; ByteRover doesn't support forget; Holographic is a local JSON facts file. Buttons visible in WebUI and methods callable in Agent tools will not be fabricated.
Can I make the background "Remember" and "Recall" Agents use different models?
Yes. Under mnemon.taskAgentModel, select fixed mode and fill in provider and model; independent task Agents like AI meta-info, archiving, Agent queries, and memory distillation will all route through that; the default inherit follows the Provider/Model when DSH creates a new session, and does not affect conversation Agents.
Can remote Web pages directly modify my memories?
No by default. remoteAccess is a security boundary sampled only at startup, defaulting to read-only: remote pages can only read and toggle Memory Space activation states; writes, settings, and backup RPCs are still restricted to loopback. If you need to open the pathway, you must change remoteAccess to trusted-host in DSH local configuration (also configuring DSH's own trustedHosts) and restart the Host.
Will my old data still be there after upgrading dsh-mnemon?
Yes, all persisted data remains under the selected storageRoot. However, v0.8 documentation explicitly states that Mnemon may run migrations in-place when opening the database. Please do a ZIP export via Settings → Backup & Migration before upgrading, and verify the restore process in an isolated directory before switching to the production scope.
— source: plugin_wiki.faq_json
Compatibility
- DSH: 0.1.0-rc.6+
- Node: >=20
- Platforms: macOS, Windows, Linux
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule