Who it is forA team lead or maintainer who relies on a shared agent memory and needs to keep it accurate and free of outdated decisions.
The problemStored memories can become wrong or stale, and it is hard to see why the agent recalls a particular memory.
The outcomePending candidates are accepted, rejected, or edited, unwanted memories are tombstoned or deleted, and you can see the reason a memory was recalled.
What you need first
- A working DeepSeek Harness (DSH) install; the README says it was tested with DSH 0.2.0-rc.2
- The dsh command line available in your shell
- Node.js and pnpm if you plan to build or develop the plugin from source
- Access to the memory files of any other AI coding tool you want to import
Steps
- Open Settings → Noema Memory and use the Manage memories card to search and browse stored memories
- Ask the agent to run noema_review_list to see pending review candidates
- Ask the agent to run noema_review_decide to accept, reject, edit, or merge each candidate
- Ask the agent to run noema_explain on a memory that was recalled unexpectedly
- Ask the agent to run noema_forget on a memory that is no longer valid
Prompt for your agent
Using the dsh-noema plugin, run noema_review_list, then noema_review_decide on the candidate with id <candidate 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.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for ZSeven-W/dsh-noema and "Review, correct, and remove stored agent memories"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer