DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to review and correct the agent's memories as plain files with DSH Auto Memory

Open the memory folder to read, edit or version the facts your agent has stored.

Who it is forA developer who wants to check what the agent has learned about them and fix wrong facts directly.

The problemStored memories can be stale or wrong, and you need to see and change them without going through the agent.

The outcomeYou can read, edit, grep or commit each memory file, and the agent uses the corrected content on its next request.

What you need first

  • DeepSeek Harness (@deepseek-ai/dsh) version 0.1.5-rc.2 or newer, or the official desktop client (verified on 0.2.0-rc.2)
  • Node.js ^22.19 or >=24
  • A dsh profile to install the plugin into (the README uses the profile name demo)

Steps

  1. Locate the memory folder at $DSH_HOME/memory/, or the memoryDir value if you set one.
  2. Open MEMORY.md to see the index and open the linked memory files.
  3. Edit or delete the files you want to correct, keeping the YAML frontmatter intact.
  4. Commit the folder to git if you want history of memory changes. (inferred, check the README)

Prompt for your agent

Open the memory folder for the dsh-auto-memory plugin at <memory-folder-path>, list the memory files, and correct the entry named <memory-name>. Expected output: the file reflects the corrected fact. Verify that MEMORY.md still lists that memory and that the next dsh request uses the new content.

Caveat. The README says memories are ordinary files under $DSH_HOME/memory/, but it does not document the exact frontmatter fields, so edit by copying an existing file's structure.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page