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

How to keep notes and facts across DSH coding sessions with Awesome DeepSeek Harness

Add a memory plugin so DSH re-reads global and per-project markdown notes in later sessions.

Remote script. The plugin reads your markdown notes, so review what it can access before installing from a GitHub repo.

Who it is forA developer who restarts DSH sessions often and keeps re-explaining project conventions to the agent.

The problemEach new session starts without the context and rules the developer already wrote down.

The outcomeMarkdown notes at global and project level are loaded into later sessions, with a Settings panel to manage them.

What you need first

  • DeepSeek Harness (DSH) installed, with the dsh command available
  • Access to the target plugin repo on GitHub, which should carry the #dsh topic
  • A DSH profile to install plugins into (the examples use the profile name web)

Steps

  1. Run npx @deepseek-ai/dsh web to launch the DSH Web UI.
  2. Confirm the plugin repo at github.com/jipika/dsh-memory carries the #dsh GitHub topic.
  3. Run dsh plugin --profile web add "github:jipika/dsh-memory#main" to install the plugin. (inferred, check the README)
  4. Open the plugin's Settings panel and create one global note and one project note in markdown.
  5. Start a new session and ask the agent to repeat the rules from the notes.

Prompt for your agent

Using the DSH list at https://github.com/Dominic789654/awesome-deepseek-harness, install the dsh-memory plugin from github.com/jipika/dsh-memory into the web profile. Ask the agent in a new session to state the convention written in <project-note-file>. Expected output is that convention stated back correctly; verify it matches the note text.

Caveat. The README describes this plugin's behavior only in its listing summary, so confirm the storage details in the plugin repo.

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