At a Glance

Provides Noema-based local long-term memory for DeepSeek Harness (DSH) Agent: enables the Agent to remember user facts, decisions, and preferences across sessions. Also allows importing old memories from other AI tools like Codex, Claude Code, Cursor for unified management.

Core Features

• Automatically recall relevant historical memories at session start or before new tasks (noema_recall)
• Persist long-term facts, decisions, constraints, or preferences stated by users as auditable local memories (noema_remember)
• Find memories through full-text search, PageIndex browsing, and multi-hop graph association三种方式查找记忆 (noema_search / noema_browse / noema_recall_graph + noema_neighbors)
• Support both "软删除（墓碑）" and "硬删除"两种方式移除记忆 (noema_forget)
• Import memories from Codex, Claude Code, opencode, Cursor, Grok, WorkBuddy, Antigravity, Trae, Qoder 共 9 个 AI 工具的 AGENTS.md/CLAUDE.md/rules files with deduplication by content (noema_import)
• Provide settings page and local status route for hot-restarting service, configuring import sources, browsing/adding/reviewing/deleting memory entries

Technical Implementation

• Language: TypeScript（宿主插件）+ Rust（noema-mcp 子进程）
• Key Dependencies: @deepseek-ai/cordis（插件运行时）、@deepseek-ai/dsh-tools（工具注册）、@deepseek-ai/schemastery（设置 schema）、react ^18.2.0（客户端 UI）
• Architecture Pattern: Plugin entry with id dsh-noema injected via cordis.patch.yml; host side mounts 15 noema_* tools, registers system prompt "记忆使用指南" section, and registers /_dsh/dsh-noema/status status route on webServer; memory engine runs as independent subprocess communicating via MCP stdio (JSON-RPC + Content-Length framing), managed by NoemaServerManager for start/stop, Keep-alive and idle recycling
• Entry Files: src/index.ts（宿主 apply）, src/client/index.tsx（设置页 UI）

Use Cases

When you want DSH Agent to remember user identity, project conventions, long-term decisions and constraints instead of starting from scratch each time. Especially suitable for those who switch between multiple AI tools and want to consolidate old tool memories into a unified local knowledge base. The import feature enables seamless migration from existing tools like Codex, Claude Code, Cursor.

Prerequisites & Compatibility

Installation

dsh plugin --profile web add github:ZSeven-W/dsh-noema

Note: After first adding to profile, DSH server needs one restart. After that, builds work with Cordis HMR and client SSE hot reload—no further restart needed.

Configuration Options

FAQ

Q: Is data uploaded to the cloud?

A: No. Memories are stored as auditable Markdown files locally in NOEMA_ROOT (default ~/.agent-memory/), with the entire engine running independently on your machine (local-first). The import feature only reads data from local config files of other tools.

Q: Do I need to restart DSH after installation?

A: One server restart is required when adding the plugin to profile for cordis to detect it. After that, both pnpm run build and pnpm run build:client support hot reloading through Cordis HMR and client SSE—restarting again is unnecessary.

Q: What if the server process crashes?

A: Keep-alive is enabled by default. The keep-alive loop checks every second (minimum interval adjustable in settings), and after detecting subprocess exit, waits for Restart delay before launching in the background. Failed restarts log warnings and surface errors on the next tool call. Intentional idle stop and manual stop are not overridden by keep-alive.

Q: I want to migrate memories from other AI tools (Codex / Claude Code / Cursor), how do I do it?

A: Three ways: ① Check desired sources in settings and click "Import now"; ② Have the model invoke noema_import; ③ Enable "Import on startup" when launching DSH. Each snippet deduplicates via SHA-256(path + heading + body), so repeated runs won't create duplicates. Use force: true to force re-import.

Q: Does the noema-mcp subprocess start by default? What's the resource usage?

A: "Start server on mount" is enabled by default, so noema-mcp persists after DSH launches (unless idle timeout is set to a positive value). The subprocess communicates with the host via Rust stdio on a single connection and consumes no additional resources when idle.

Q: Which settings take effect immediately?

A: Fields modified through the Settings page (/_dsh/dsh-noema/status) write and apply hot instantly, including server command, keep-alive, budget, sources, etc. After changing Server command, manually clicking "Restart" is recommended for the new command to take effect.

Q: What operating systems are supported?

A: Six npm optional packages cover macOS (arm64/x64), Linux (arm64/x64, requires glibc), and Windows (arm64/x64). Other ABIs like Linux musl lack precompiled binaries and require compiling noema-mcp manually, then specifying its path in the Server command.

Q: Are memory files deleted after uninstall?

A: No. The uninstall command dsh plugin --profile web remove @zseven-w/dsh-noema only removes the plugin itself. Memory files stay in NOEMA_ROOT and the import deduplication ledger remains in $DSH_HOME/storages/dsh-noema-imports.json—manual cleanup is needed if desired.

Learning Curve

Intermediate — The plugin runs out of the box, but effective use requires understanding long-term memory mechanics (recall vs search vs browse), the review queue, write strategies (manual/review/auto-safe/auto), and concepts like keep-alive and import ledgers. After first installation, spend a few minutes reviewing the status cards and import sources in settings, then have the model explain a few stored memories.

Known Issues & Limitations

• First load requires DSH restart: Cordis HMR only hot-swaps already-loaded plugins. After first adding dsh-noema to profile, one server restart is required for the plugin inventory to recognize it (README.md:188)
• Limited platform coverage: Only 6 optionalDependencies packages cover macOS arm64/x64, Linux arm64/x64 (glibc), Windows arm64/x64. Other platforms (Linux musl, FreeBSD, Linux x86 musl) need to compile noema-mcp binary themselves and specify the path in Server command (package.json:87-94, platforms.json:1-58)
• Linux links glibc: Both linux-arm64 and linux-x64 optional packages explicitly require libc: glibc; musl distributions (Alpine, etc.) cannot use precompiled binaries directly (platforms.json:24, 34)
• Startup fails when optional dependencies stripped: If the package manager skips optional dependencies (npm installs them by default, but some CI tools omit them), first noema-mcp launch throws "bundled package ... is not installed" with a fix hint: reinstall with optional enabled or run npm run build:noema:dev in source (src/bundled-binary.ts:101-120, src/server-manager.ts:266-273)
• Import ledger cap at 2000 entries: To prevent unbounded ledger growth, saveLedger trims to 2000 entries by most recent timestamp; in extreme re-import scenarios, old entries get discarded (src/import-service.ts:124, 144-151)
• Import recursion depth cap at 3: When scanning directories like Cursor rules, Trae memory, Qoder rules/memory/projects, directory recursion is hard-limited to 3 levels; files in deeper directories won't import (src/import-service.ts:170-205)
• Status route only listens on localhost: Status route IP check restricts access to 127.0.0.1 / ::1, with Origin validation requiring same-origin; direct settings API calls are unavailable when accessing DSH web port remotely (src/status-route.ts:34-94)
• Status route request body cap at 16 KB: POST requests to /status readBody limited to 16384 bytes; oversized write requests return 413 (src/status-route.ts:121-137)
• Startup failure doesn't block DSH startup: If noema-mcp fails to start, the host continues without interruption, only logging a warning and erroring on tool calls; if keep-alive is enabled, confirm successful startup in logs (src/index.ts:124-127)

DSH Noema

Long-term memory for DeepSeek Harness — durable, inspectable agent memory backed by Noema.
_{Recall Before Work • Import From 9 Agent Tools • Settings-Page Memory Management • Crash Keep-Alive • Hot Reload}

_{npm: @zseven-w/dsh-noema · Current plugin release: 0.1.0-rc.1 · Tested with DSH 0.1.0-rc.6}

English · 简体中文 · 繁體中文 · 日本語 · 한국어 · Français · Español · Deutsch · Português · Русский · हिन्दी · Türkçe · ไทย · Tiếng Việt · Bahasa Indonesia

_{The Noema Memory settings page — import sources, memory management, and live server status}

Why DSH Noema

DSH Noema connects DeepSeek Harness with Noema — a local-first, non-vector memory system for coding agents — so an Agent keeps durable knowledge across sessions instead of starting every conversation from zero.

Install into DSH

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

Or, for local development straight from the source tree:

dsh plugin --profile web add link:/path/to/dsh-noema
dsh web

The link: protocol symlinks the profile dependency to this repository, so rebuilds are visible immediately and Cordis HMR can watch the compiled output.

The plugin bundles the noema-mcp binary through per-platform optional npm packages. To build it yourself instead, run cargo build --release -p noema-mcp inside the bundled noema submodule, or point the Server command setting at any noema-mcp build.

Memory Tools

The model-facing tools mirror the Noema MCP surface:

Each tool returns a uniform envelope { ok, tool, text } where text carries the full server output.

Import memories from other tools

• 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).
• Imports are deduplicated through a ledger at $DSH_HOME/storages/dsh-noema-imports.json, keyed by file path + section content — when several tools share one project AGENTS.md, each section is imported exactly once. force: true re-imports everything.
• 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.

Settings

Open Settings → Noema Memory:

The status card shows server health with restart/stop actions, and the import section manages the nine memory sources.

Hot reload

DSH's HMR machinery is fully usable once the plugin has been loaded once:

• Host plugin — enable the Cordis HMR entry in the profile patch with its watch root pointed at this package's lib/ output, and keep the link: dependency. Run pnpm run build and the running DSH reloads the plugin entry automatically (the Noema server child is restarted by the reload) — no server restart.

  # ~/.dsh/profiles/<profile>/cordis.patch.yml
  - id: hmr
    disabled: false
    config:
      root:
        - /path/to/dsh-noema/lib
  

• Client bundle — ppnpm run build:client rewrites lib/client.js; the client-hmr node half stat-polls every graph bundle (default 500ms) and broadcasts a rebuilt frame over the /plugins/events SSE channel, and the browser hot-swaps the module without a page refresh.

• Settings — every change made on the Noema Memory settings page applies live through the settings service.

The one thing hot-reload cannot do is load a plugin that was never in the booted tree: the running composition neither watches the profile patch layer (the web app does not wire watchUserPatches) nor exposes a loader mutation API (the plugin inventory RPC is read-only). A fresh plugin therefore needs exactly one server restart, after which the loop above is fully hot.

Develop

pnpm install
pnpm run build     # host tsc + client tsdown bundle
pnpm test          # build + node --test tests/

The e2e test runs against noema/target/debug/noema-mcp when present (it is skipped otherwise).

License

MIT