Skip to main content

How to use dsh-noema

Provides auditable long-term memory for DSH Agent based on Noema: cross-session fact storage and retrieval, settings page management, and memory import from 9 other AI tools.

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-noema

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add @zseven-w/dsh-noema

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

  • The source argument selects one tool, or omit it to run every source enabled in settings.
  • The path argument selects the workspace root for project-scoped files (defaults to the session workspace; workspace files only load when the Import workspace files setting is on).
  • The settings page exposes per-source checkboxes, an import-on-startup toggle, a file-size cap, and an Import now button with a last-run summary.
    • /path/to/dsh-noema/lib
  • Settings — every change made on the Noema Memory settings page applies live through the settings service.

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

What specific problem does this plugin solve?

DSH starts fresh by default for each new session. This plugin enables the Agent to remember user facts, decisions, constraints, and preferences across sessions, avoiding repeated information.

Where is data stored? Is it uploaded to the cloud?

Memories are stored locally as Markdown files in NOEMA_ROOT (default ~/.agent-memory/), the entire system runs locally (local-first) and does not upload user data.

Must DSH be restarted after installation?

Yes. Adding the plugin to a profile for the first time requires one DSH server restart. Subsequent builds can then be hot-reloaded via Cordis HMR and client SSE.

What if the server process crashes?

Keep-alive is enabled by default: it detects when a child process exits and automatically restarts after a configured backoff period. Related settings can be adjusted in Settings → Noema Memory.

How to migrate memories from existing AI tools (Claude Code, Codex, Cursor, etc.)?

Check the desired sources in the settings page and click Import now, or have the model call noema_import. Imported fragments are deduplicated by the ledger, so running multiple times won't create duplicates.

What must be done in Settings to use it?

Works out of the box. For Server command, select bundled to use the precompiled binary, or enter a custom noema-mcp command/path. When NOEMA_ROOT is empty, it defaults to ~/.agent-memory/.

Which operating systems are supported?

Officially provided: darwin-arm64/x64, linux-arm64/x64 (glibc), win32-arm64/x64 - six npm packages covering the corresponding architectures. Other ABIs like Linux musl are not provided with binaries.

How to uninstall?

Run: dsh plugin --profile web remove @zseven-w/dsh-noema. Memory files remain on disk - manually delete ~/.agent-memory/ and the import ledger if needed.

— source: plugin_wiki.faq_json

Compatibility

  • DSH: ^0.1.0-rc.6
  • Node: >=24.11.0
  • Platforms: macOS (arm64), macOS (x64), Linux (arm64, glibc), Linux (x64, glibc), Windows (arm64), Windows (x64)
  • Native modules: @zseven-w/dsh-noema-darwin-arm64, @zseven-w/dsh-noema-darwin-x64, @zseven-w/dsh-noema-linux-arm64, @zseven-w/dsh-noema-linux-x64, @zseven-w/dsh-noema-win32-arm64, @zseven-w/dsh-noema-win32-x64, noema-mcp (Rust stdio 子进程)

— 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