ZSeven-W/dsh-noema
636Last commit Aug 15, 2026
dsh-noema DSH plugin
DSH Noema connects DeepSeek Harness with Noema, a local-first, non-vector memory system for coding agents. It provides durable recall across sessions, import from 9 AI coding tools, and a settings-page memory management interface. Memories persist as inspectable Markdown files, and the plugin includes crash keep-alive and hot reload features.
How to install the dsh-noema DSH plugin
dsh plugin --profile web add @zseven-w/dsh-noema@latestCopying does not run this command. Review the repository and version before installing the dsh-noema DSH plugin.
dsh-noema DSH plugin data source
dsh-noema DSH plugin snapshot date: Aug 16, 2026
discovered
What the dsh-noema DSH plugin can do
- Durable recall of memories across sessions using `noema_recall` and related tools.
- Import memories from 9 other AI coding tools (Codex, Claude Code, opencode, Cursor, Grok, WorkBuddy, Antigravity, Trae, Qoder) with deduplication.
- Settings-page memory management: search, browse, add, review, and delete memories.
- Keep-alive loop that restarts the memory server on crash or exit.
- Hot reload for host plugin and client bundle after initial load.
Where the dsh-noema DSH plugin fits
- Maintain context across multiple coding sessions for an AI agent.
- Migrate memories from a previous AI coding tool to DSH Noema.
- Manage and review stored memories through a dedicated settings page.
- Ensure agent memory server stays running during long development sessions.
- Develop and test memory plugin changes with hot reload without restarting DSH.
Who the dsh-noema DSH plugin is for
- Developers using DeepSeek Harness who want persistent agent memory.
- Teams migrating from other AI coding tools to DSH and need to preserve past context.
dsh-noema DSH plugin limitations
- Requires DSH version 0.1.0-rc.6 or compatible.
- Memory storage is local-first and not cloud-synced; only accessible on the same machine.
- Import from other tools requires the tool's memory files to be present in standard locations.
- Hot reload cannot load a plugin that was never in the booted tree; a fresh plugin needs one server restart.
dsh-noema DSH plugin: from the repository README
Quoted from the ZSeven-W/dsh-noema README, the upstream source of the dsh-noema DSH plugin. Copyright remains with the original authors.
DSH Noema connects [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) with [Noema](https://github.com/ZSeven-W/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. <table> <tr> <td width="50%"> ### 🧠 Durable Recall Memories persist as inspectable Markdown files under `NOEMA_ROOT` (default `~/.agent-memory/`). `noema_recall` loads relevant context at the start of a session; `noema_search`, `noema_browse`, `noema_catalog`, and `noema_recall_graph` cover lookup, exploration, and auditing. </td> <td width="50%"> ### 📥 Import From Other Tools `noema_import` reads the memory files of nine other AI coding tools — Codex, Claude Code, opencode, Cursor, Grok, WorkBuddy, Antigravity, Trae, Qoder — splits them into sections, and saves each as a durable memory. A content-keyed ledger deduplicates across runs and across tools that share files. </td> </tr> <tr> <td width="50%"> ### 🛠️ Settings-Page Management The Noema Memory settings page configures the server command, memory root, budgets, idle/call timeouts, and the guidance section — and a Manage m
Read the full READMERepository license: MIT
dsh-noema DSH plugin questions
How do I install DSH Noema plugin?
Run `dsh plugin --profile web add @zseven-w/dsh-noema@latest` in your terminal, then start DSH with `dsh web`. The plugin will be downloaded and enabled. For local development, you can use `dsh plugin --profile web add link:/path/to/dsh-noema` for instant rebuilds.
Does DSH Noema work with other coding tools' memory files?
Yes, it can import memories from nine AI coding tools: Codex, Claude Code, opencode, Cursor, Grok, WorkBuddy, Antigravity, Trae, and Qoder. The import process reads the tool's memory files from standard locations, splits them into sections, and saves each as a durable memory. A ledger deduplicates across runs and shared files.
Where are memories stored?
Memories are stored as inspectable Markdown files under the `NOEMA_ROOT` directory, which defaults to `~/.agent-memory/`. You can change this path in the settings page under Noema Memory. The files are local to your machine and not synced to the cloud.
Can I manage memories without using the command line?
Yes, the plugin provides a settings page (Settings → Noema Memory) where you can search, browse, add, review, and delete memories. You can also toggle import sources, adjust budgets, and monitor server status from the same interface.
What happens if the memory server crashes?
The plugin includes a keep-alive feature that automatically restarts the memory server in the background when it crashes or exits. You can configure the check interval and restart delay in the settings. By default, the idle timeout is set to 0 (never stop), so the server stays up continuously.