dsh-memory-recall 0.1.0

package/LICENSE

@@ -0,0 +1,96 @@
+MIT License
+
+Copyright (c) 2026 adithyanraj03
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+-------------------------------------------------------------------------------
+
+Portions of src/threats.js, src/memory-tool.js and src/store.js are adapted
+from Hermes Agent (https://github.com/NousResearch/hermes-agent):
+the threat-pattern list, the memory tool's design and wording, and the
+§-delimited memory file format. Hermes Agent is distributed under this licence:
+
+MIT License
+
+Copyright (c) 2025 Nous Research
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+-------------------------------------------------------------------------------
+
+The brain icon in lib/client.js is from Lucide (https://lucide.dev), under the
+ISC License:
+
+Copyright (c) for portions of Lucide are held by Cole Bemis 2013-2022 as part
+of Feather (MIT). All other copyright (c) for Lucide are held by Lucide
+Contributors 2022.
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
+FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS
+OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
+THIS SOFTWARE.
+
+-------------------------------------------------------------------------------
+
+The solid brain glyph in lib/client.js is from Phosphor Icons
+(https://phosphoricons.com), under the MIT License:
+
+Copyright (c) 2023 Phosphor Icons
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,181 @@
+# dsh-memory-recall
+
+![language](https://img.shields.io/badge/language-javascript-f7dc6f) ![style](https://img.shields.io/badge/style-vanilla-gray) ![license](https://img.shields.io/badge/license-MIT-blue) ![node](https://img.shields.io/badge/node-%E2%89%A5%2022-brightgreen) ![dsh](https://img.shields.io/badge/dsh-web%20profile-orange) ![runtime](https://img.shields.io/badge/runtime-offline_%C2%B7_100%25_local-brightgreen) ![tests](https://img.shields.io/badge/tests-passing-brightgreen)
+
+A [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) plugin that gives the model a memory, in the style of [Hermes Agent](https://github.com/NousResearch/hermes-agent): what it learns about you and your projects carries into every new chat, and it can look back through your earlier chats — **only after you allow it**.
+
+**Everything stays on your machine.** Two small text files, dsh's own session index, no embeddings, no service, no telemetry.
+
+![The Memory panel: the model's notes, with a budget bar and inline edit](assets/memory-panel.png)
+
+It does five things:
+
+- **A `memory` tool** — the model keeps two short files: a **user profile** (who you are, how you like to work) and its **own notes** (environment facts, conventions, lessons). Every new chat starts with both in its prompt.
+- **A `session_search` tool** — the model reads your earlier chats to answer *"what did we decide last time?"*. dsh's own approval prompt asks you first, saying what it wants to look for.
+- **A 🧠 Saved to memory note in the chat** — every save shows what changed and how full memory is, so nothing is remembered behind your back.
+- **A sidebar 🧠 Memory panel** — everything kept, in two tabs, with edit, delete, add and search.
+- **Chats and workspaces in the `@` menu** — grouped by workspace, under their real titles, so you can hand the model a chat or point its search at one workspace.
+
+## Install
+
+Requires a working dsh (0.1.5 or later) with a `web` profile.
+
+```sh
+dsh plugin --profile web add dsh-memory-recall
+dsh --profile web
+```
+
+Or install from GitHub or a local folder instead:
+
+```sh
+dsh plugin --profile web add github:adithyanraj03/dsh-memory-recall
+dsh plugin --profile web add /path/to/dsh-memory-recall
+```
+
+Then **restart dsh** (`dsh --profile web`) if it was already running, and **hard-refresh the browser** (Ctrl+Shift+R / Cmd+Shift+R) — a plain refresh can serve a cached client bundle. **🧠 Memory** appears at the bottom of the sidebar.
+
+### Turn on dsh's full-text search (recommended)
+
+`session_search` uses dsh's own session index, which dsh ships **switched off**. Add this to your profile's `cordis.patch.yml` (`~/.dsh/profiles/web/cordis.patch.yml`):
+
+```yaml
+- id: session-query-sqlite
+  config:
+    path: '/absolute/path/to/.dsh/session-search.db'
+    openAt: first-search
+```
+
+`first-search` opens the index only when something first searches; a file path keeps it across restarts. The index is derived from your session logs, so deleting the file only costs a rebuild. An override replaces the row's whole config — keep both keys.
+
+Without it, `session_search` still works: it falls back to a literal scan of your 150 most recent chats — slower and unranked — and says so in its card.
+
+## What you get
+
+### Memory that carries over
+
+Just talk. The model saves what will matter later — that you use PowerShell, that a server lives on another machine, that the docs build breaks on a trailing colon — and each save appears in the chat. Click it to see exactly what changed and how full that store is:
+
+![Saves in the chat: an added note and an updated profile entry, each with its budget](assets/saved-chip.png)
+
+![All five states of the note: saving, saved, updated, full — making room, and a write blocked by the safety scan](assets/chip-1.png)
+
+You can also ask directly: *"remember that I prefer short answers"*, *"forget that I use npm"*.
+
+Memory is pasted into each new chat's prompt once, when the chat starts, and is **fixed for the life of that chat** — rewriting the prompt mid-chat would throw away dsh's cached prompt prefix. A save made mid-chat is on disk at once and reaches the prompt from the **next** new chat. The model is told this, so it does not save twice.
+
+### Looking back through earlier chats
+
+Refer to an earlier conversation — *"what did we decide about the rollback?"*, *"do it like last time"* — and the model calls `session_search`. dsh's approval prompt takes over the message box with what it wants to read, e.g. *Search your earlier chats for "deploy rollback".*, with **Allow** and **Deny**. The chats it found appear in a card, each with its date, the matching lines and a link to open it:
+
+![A recall card: three earlier chats found for "deploy rollback", with the matching lines](assets/recall-card.png)
+
+It returns the chats' actual messages — nothing summarised, nothing invented — cut to about 9,000 characters so one search cannot flood the context. The asking chat and sub-agent sessions are never results.
+
+### The Memory panel
+
+**🧠 Memory**, at the bottom of the sidebar above ⏱️ Scheduled when both are installed, opens everything that is kept:
+
+- **Notes** and **Profile** tabs, each with a ring and a bar showing how full it is.
+- **Edit** or **delete** any entry in place (hover it), with an inline confirm for delete.
+- **Add** an entry yourself, and **search** once a tab holds a few.
+- With the sidebar collapsed, it becomes a single icon, like Settings.
+
+![The Profile tab in the light theme](assets/memory-panel-light.png)
+
+Edits you make here are your own words, so they are not scanned (see [Safety](#safety)), but they still respect the budget. Hand edits to the files show in the panel at once and in the prompt from the next new chat.
+
+### Chats and workspaces in the @ menu
+
+Type `@` in the message box. Below dsh's own files and folders, your chats are listed **grouped by workspace**, under the titles your sidebar shows:
+
+- **Just `@`** — *This workspace* with its most recent chats, then *Workspaces* with every other one and how many chats it holds, then chats in no workspace.
+- **`@` + text** — matching workspaces, then matching chats under their workspace's heading.
+- **Tab, or the chevron, on a workspace** — all of its chats, with an *All workspaces* crumb back.
+
+**Pick a chat** and dsh attaches a read-only snapshot of it to your message, exactly as its own `@` chat rows do — no search and no permission prompt, because you chose it. **Pick a workspace** and it reaches the model as `[workspace "Web Search" — /path/to/Web Search]`; `session_search` then searches only that workspace's chats (after asking, as always).
+
+Every chat gets a readable name — its title, or the start of its first message if it never got one. Sub-agent sessions are left out, and nothing is capped at 50. These rows replace dsh's own flat `@` chat list while its file rows stay as they are; dsh offers no switch for that, so the plugin wraps its `@` source and restores it when unloaded.
+
+## How asking works
+
+- **Reading earlier chats asks first**, through dsh's own approval prompt.
+- **One Allow covers that reply.** A search is usually followed by a closer read of the best hit; asking twice for one question is noise. The permission ends when the reply finishes, so the next question asks again.
+- **Deny means nothing is read**, and the model is told not to ask again in that reply. If the prompt is withdrawn (you stopped the reply) or nobody can be asked, nothing is read either.
+- **Saving to memory does not ask** — it is always shown in the chat and can be undone in the Memory panel. This matches Hermes Agent's default.
+
+If dsh runs in `danger-full-access` mode its approval policy is `never`, which **rejects** every approval request without prompting — so recall is refused there. Set `askBeforeRecall: false` if you want recall without asking in that mode.
+
+## What goes into the prompt
+
+Each new chat gets one prompt section: a short note on how memory works, then the two stores, rendered as Hermes renders them:
+
+```
+══════════════════════════════════════════════
+USER PROFILE (who the user is) [14% — 189/1,375 chars]
+══════════════════════════════════════════════
+Works on Windows 11 in PowerShell; projects live under D:/code.
+§
+Prefers short answers with the command first, explanation after.
+```
+
+The budgets are small on purpose — **2,200 characters of notes and 1,375 of profile**, Hermes's defaults, together roughly 900 tokens — because they are paid in every chat. When a store is full, a save that would overflow it is refused whole, never cut; the model is shown the entries and consolidates in one batch that merges or drops stale entries and adds the new one, checked against the final size. Raise the budgets with `limits` (below) if you would rather pay more per chat.
+
+Sub-agent sessions do not get the section; they are the model's own workers.
+
+## Configuration
+
+All optional, on this plugin's row in the profile's `cordis.patch.yml`:
+
+```yaml
+- id: dsh-memory-recall
+  config:
+    limits:
+      memory: 4000
+      user: 1375
+```
+
+| Key | Default | Meaning |
+|---|---|---|
+| `dir` | `~/.dsh/dsh-memory-recall` | Where `USER.md` and `MEMORY.md` live |
+| `limits` | `{memory: 2200, user: 1375}` | Character budgets for the notes and the profile |
+| `recall` | `true` | `false` drops `session_search` and keeps memory |
+| `askBeforeRecall` | `true` | `false` reads earlier chats without asking |
+
+An override replaces the row's whole config, so restate every key you set. Restart dsh after changing it.
+
+## Safety
+
+Memory is re-read into every future chat, so a poisoned entry would keep instructing the model until someone deleted it. Every write **the model** makes is scanned for prompt-injection and exfiltration phrasing — *ignore previous instructions*, *don't tell the user*, piping secrets to a URL, SSH keys, edits to dsh's own config, hidden Unicode — and refused with the reason. The patterns are Hermes Agent's.
+
+Other guards:
+
+- A change re-reads the file first, so a hand edit is never overwritten by a stale copy; writes are atomic and one at a time.
+- Replace and remove need a piece of text unique to one entry; an ambiguous one is refused, not guessed.
+- A batch is all-or-nothing.
+
+## How it works
+
+- **Host side** (`src/index.js`): registers the `memory` and `session_search` tools, adds the memory section to each new top-level chat's system prompt on `agent/session-start`, and serves the panel's routes under `/plugin-data/dsh-memory-recall/`. Recall goes through dsh's `sessionQuery` service and its `approval` service; nothing talks to the network.
+- **Client side** (`lib/client.js`, plain JavaScript, no build step): the in-chat chip and recall card replace dsh's own rows for those two tools through the `tool.call.toolview` slot; the panel mounts into `sidebar.footer.action`; the `@` rows are an `inputTriggers` source.
+- **Files**:
+
+  ```
+  ~/.dsh/dsh-memory-recall/USER.md     the user profile
+  ~/.dsh/dsh-memory-recall/MEMORY.md   the model's notes
+  ```
+
+  Plain text, entries separated by a line holding only `§` — the same format as Hermes, readable and editable by hand.
+
+## Requirements
+
+- dsh 0.1.5 or later, with a `web` profile
+- Node 22+
+- No runtime dependencies — the client bundle requires only `react`
+
+## Credits
+
+The design — two bounded stores, a frozen per-chat snapshot, the batch-against-final-budget rule, `session_search`'s shapes, the §-delimited files and the threat patterns — comes from [Hermes Agent](https://github.com/NousResearch/hermes-agent) by Nous Research (MIT). The brain icons are Lucide's (ISC) and Phosphor's (MIT).
+
+## Licence
+
+MIT — see the [LICENSE](LICENSE) file, which also carries the notices for Hermes Agent, Lucide and Phosphor.

package/cordis.patch.yml

@@ -0,0 +1,16 @@
+# dsh-memory-recall: mount the host half — the memory store, the `memory` and
+# `session_search` tools, the per-chat memory snapshot, and the routes the
+# browser half reads. The Memory panel and the in-chat cards are mounted by the
+# `dsh.client` entry in package.json, not from here.
+#
+# `name` MUST be the package name: the loader imports this exact specifier.
+#
+# Config (all optional, set on this row):
+#   dir                     where USER.md and MEMORY.md live
+#                           (default ~/.dsh/dsh-memory-recall)
+#   limits: {memory, user}  character budgets (default 2200 / 1375, as Hermes)
+#   recall: false           drop session_search, keep memory
+#   askBeforeRecall: false  read earlier chats without asking first
+- insert:
+    - id: dsh-memory-recall
+      name: 'dsh-memory-recall'

package/dsh.plugin.json

@@ -0,0 +1,18 @@
+{
+  "id": "dsh-memory-recall",
+  "version": "0.1.0",
+  "main": "./src/index.js",
+  "description": "Persistent memory for dsh in the style of Hermes Agent: a memory tool that keeps a user profile and the model's own notes in every new chat's prompt, and a session_search tool that reads earlier chats only after the user approves, with a Memory panel to see and edit what is kept.",
+  "engines": {
+    "dsh": ">=0.1.5-rc.2"
+  },
+  "contributes": {
+    "tools": [
+      "memory",
+      "session_search"
+    ]
+  },
+  "client": {
+    "main": "./lib/client.js"
+  }
+}