# AI use cases for DSH Noema (ZSeven-W/dsh-noema) Repo: [ZSeven-W/dsh-noema](https://github.com/ZSeven-W/dsh-noema) | Use cases: 4 | Page: https://dedupedai.com/use-cases/zseven-w-dsh-noema/ DSH Noema is a TypeScript plugin that gives the DeepSeek Harness agent durable, inspectable long-term memory backed by Noema, with recall tools, import from other AI coding tools, and a settings page. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Keep a DSH agent's knowledge across sessions: https://dedupedai.com/use-cases/zseven-w-dsh-noema/give-dsh-agent-memory-across-sessions/ - Import memory from nine other coding agent tools: https://dedupedai.com/use-cases/zseven-w-dsh-noema/import-memories-from-other-coding-agents/ - Review, correct, and remove stored agent memories: https://dedupedai.com/use-cases/zseven-w-dsh-noema/audit-and-prune-agent-memories/ - Build and hot-reload changes to the Noema plugin: https://dedupedai.com/use-cases/zseven-w-dsh-noema/develop-noema-plugin-with-hot-reload/ ## How to keep a DSH agent's knowledge across sessions with DSH Noema Repo: [ZSeven-W/dsh-noema](https://github.com/ZSeven-W/dsh-noema) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Install the Noema plugin so DSH recalls saved facts and decisions at the start of each session. **Who it is for:** A developer who uses DeepSeek Harness daily and is tired of re-explaining project conventions and past decisions to the agent in every new conversation. **The problem:** Each DSH conversation starts from zero, so the agent forgets constraints, preferences, and decisions made in earlier sessions. **The outcome:** The agent loads relevant memories at session start, and new durable facts it learns are saved as inspectable Markdown files you can read. ### Steps 1. Run `dsh plugin --profile web add @zseven-w/dsh-noema@latest` 2. Run `dsh web` and open Settings → Noema Memory to confirm Enable memory is on 3. Start a session and ask the agent to run noema_recall for the project you are working on 4. Ask the agent to save a fact with noema_remember, such as a preference or a decision you just made 5. Start a new session and check that noema_recall returns the fact you saved ### Prompt to paste into your agent ```text Using the dsh-noema plugin in DSH, call noema_remember to save the decision '' for the project at , then call noema_recall with a query about that project in a new session. Expected output: the recall result contains the saved decision. Verify that a Markdown memory file for it appears under NOEMA_ROOT, which defaults to ~/.agent-memory/. ``` ### Caveat The README says the plugin needs one server restart after it is first added to a profile, and the default memory location is ~/.agent-memory/ unless you set the Memory root (NOEMA_ROOT) setting. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/zseven-w-dsh-noema/give-dsh-agent-memory-across-sessions/ ## How to import memory from nine other coding agent tools with DSH Noema Repo: [ZSeven-W/dsh-noema](https://github.com/ZSeven-W/dsh-noema) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Pull rules and notes from Claude Code, Cursor, Codex and others into DSH memory without duplicates. **Who it is for:** A developer who has used several AI coding tools and wants their accumulated rules and notes available to the DSH agent. **The problem:** Useful project rules and preferences are scattered across the memory files of other coding tools and are not visible to DSH. **The outcome:** Each section of the selected files is saved as a durable memory, and re-running the import skips sections that were already imported. ### Steps 1. Run `dsh plugin --profile web add @zseven-w/dsh-noema@latest` and then `dsh web` if you have not installed the plugin yet 2. Open Settings → Noema Memory and tick the sources you want, such as claude-code or cursor 3. Decide whether to turn on the Import workspace files setting for project-scoped files 4. Click Import now and read the last-run summary 5. Ask the agent to run noema_search for a term from the imported files to confirm the memories were saved ### Prompt to paste into your agent ```text Using the dsh-noema plugin, run the noema_import tool with source set to and path set to . Expected output: an ok envelope whose text lists how many sections were imported. Verify by running noema_search for a phrase from one imported section, and confirm that a second run without force reports those sections as already imported. ``` ### Caveat The README lists ten sources in the import table but the settings section says nine memory sources, and Antigravity support is described as best-effort with no documented global memory store yet. Risk, credentials: Imported files are saved as durable memory, so check them for secrets or tokens before running the import. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/zseven-w-dsh-noema/import-memories-from-other-coding-agents/ ## How to review, correct, and remove stored agent memories with DSH Noema Repo: [ZSeven-W/dsh-noema](https://github.com/ZSeven-W/dsh-noema) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Check pending candidates, explain why memories are recalled, and delete stale entries. **Who it is for:** A team lead or maintainer who relies on a shared agent memory and needs to keep it accurate and free of outdated decisions. **The problem:** Stored memories can become wrong or stale, and it is hard to see why the agent recalls a particular memory. **The outcome:** Pending candidates are accepted, rejected, or edited, unwanted memories are tombstoned or deleted, and you can see the reason a memory was recalled. ### Steps 1. Open Settings → Noema Memory and use the Manage memories card to search and browse stored memories 2. Ask the agent to run noema_review_list to see pending review candidates 3. Ask the agent to run noema_review_decide to accept, reject, edit, or merge each candidate 4. Ask the agent to run noema_explain on a memory that was recalled unexpectedly 5. Ask the agent to run noema_forget on a memory that is no longer valid ### Prompt to paste into your agent ```text Using the dsh-noema plugin, run noema_review_list, then noema_review_decide on the candidate with id set to reject. Expected output: an ok envelope confirming the decision. Verify by running noema_review_list again and confirming the candidate is no longer pending. ``` ### Caveat The README says noema_forget can tombstone or hard-delete a memory but does not say which option is the default, so confirm the behavior before deleting important records. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/zseven-w-dsh-noema/audit-and-prune-agent-memories/ ## How to build and hot-reload changes to the Noema plugin with DSH Noema Repo: [ZSeven-W/dsh-noema](https://github.com/ZSeven-W/dsh-noema) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Link the plugin from source so rebuilds reload in the running DSH without a server restart. **Who it is for:** A developer who wants to modify the Noema plugin or its settings page and see changes without restarting DSH each time. **The problem:** Changing a plugin normally means restarting the host, which slows down iteration on the memory server and its UI. **The outcome:** After one initial restart, rebuilds reload the host plugin through Cordis HMR and hot-swap the browser bundle. ### Steps 1. Run `pnpm install` inside the DSH Noema source tree 2. Run `dsh plugin --profile web add link:/path/to/dsh-noema` and then `dsh web` 3. Enable the Cordis HMR entry in ~/.dsh/profiles/ /cordis.patch.yml with its root pointed at the lib folder 4. Run `pnpm run build` after editing host code and `ppnpm run build:client` after editing the browser bundle 5. Run `pnpm test` to build and run the node tests ### Prompt to paste into your agent ```text In the dsh-noema repository, make a small change to the settings description, run `pnpm run build`, and then run `pnpm test`. Expected output: the build and the node test suite both finish without errors. Verify that the running DSH reloads the plugin entry without a server restart. ``` ### Caveat The README says a fresh plugin needs exactly one server restart, and hot reload cannot load a plugin that was never in the booted tree, so new plugins still require that restart. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/zseven-w-dsh-noema/develop-noema-plugin-with-hot-reload/