memory-eternal 0.9.14 → 0.9.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +34 -34
- package/.codex-plugin/plugin.json +29 -29
- package/.cursor-plugin/plugin.json +28 -28
- package/README.en.md +366 -365
- package/README.md +390 -389
- package/index.js +65 -6
- package/lib/api.js +3 -0
- package/lib/client.js +17 -17
- package/lib/minhash.js +99 -99
- package/lib/vault.js +941 -941
- package/package.json +131 -131
- package/web/app.js +19 -19
package/README.en.md
CHANGED
|
@@ -1,365 +1,366 @@
|
|
|
1
|
-
# 🧠 memory-eternal — A "second brain" for your AI
|
|
2
|
-
|
|
3
|
-
<p align="center">
|
|
4
|
-
<img src="https://img.shields.io/badge/DeepSeek%20Harness-plugin-3B82F6" alt="DSH plugin" />
|
|
5
|
-
<img src="https://img.shields.io/npm/v/memory-eternal" alt="npm version" />
|
|
6
|
-
<img src="https://img.shields.io/github/stars/EternalNight996/memory-eternal?style=flat" alt="GitHub stars" />
|
|
7
|
-
<img src="https://img.shields.io/github/license/EternalNight996/memory-eternal" alt="license" />
|
|
8
|
-
<a href="https://dsh.market/"><img src="https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed.svg" alt="DSH Market listed" /></a>
|
|
9
|
-
</p>
|
|
10
|
-
|
|
11
|
-
<p align="center">
|
|
12
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-eternal.gif" width="880" alt="Auto-capture + visual library + knowledge graph (demo)" />
|
|
13
|
-
</p>
|
|
14
|
-
|
|
15
|
-
> **Auto-captures knowledge after every conversation and survives across sessions; recall fetches only the relevant chunks — saves tokens, less noise.**
|
|
16
|
-
> Fully self-built, zero third-party memory framework, no DSH source changes, one vault shared by every Agent, SQLite persistent storage, zero external dependencies.
|
|
17
|
-
|
|
18
|
-
<p align="center"><strong>⭐ Star it if you like it!</strong> <br/><sub>DSH one-liner: <code>dsh plugin --profile web add memory-eternal</code></sub></p>
|
|
19
|
-
|
|
20
|
-
<p align="center">
|
|
21
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-popup.png" width="32%" alt="Memory popup: knowledge cards / search / knowledge graph" />
|
|
22
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-settings.png" width="32%" alt="DSH Settings → Memory: all options" />
|
|
23
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-sidebar.png" width="32%" alt="Sidebar quick entry" />
|
|
24
|
-
</p>
|
|
25
|
-
|
|
26
|
-
---
|
|
27
|
-
|
|
28
|
-
## 🚀 Get Started in 5 Minutes
|
|
29
|
-
|
|
30
|
-
### 🟦 DeepSeek Harness (DSH) — focus
|
|
31
|
-
|
|
32
|
-
**Install** (official desktop app via the plugin marketplace, `dsh web` via one CLI line):
|
|
33
|
-
|
|
34
|
-
```bash
|
|
35
|
-
# 1) Official DeepSeek Harness desktop app (recommended): Settings -> Plugins -> search memory-eternal
|
|
36
|
-
# Equivalent CLI (that shell's profile is named "desktop"):
|
|
37
|
-
dsh plugin --profile desktop add memory-eternal
|
|
38
|
-
|
|
39
|
-
# 2) dsh web (browser):
|
|
40
|
-
dsh plugin --profile web add memory-eternal
|
|
41
|
-
|
|
42
|
-
# or update directly in the profile (pnpm workspace). Use pnpm — `npm install` throws EUNSUPPORTEDPROTOCOL
|
|
43
|
-
cd ~/.dsh/profiles/web && pnpm add memory-eternal@latest
|
|
44
|
-
|
|
45
|
-
# right after a release, @latest can be held back by pnpm's minimum-release-age gate or a cached
|
|
46
|
-
# packument (it silently stays on the old version): pin the version instead — pnpm adds it to the
|
|
47
|
-
# workspace's minimumReleaseAgeExclude automatically
|
|
48
|
-
cd ~/.dsh/profiles/web && pnpm add memory-eternal@0.9.6
|
|
49
|
-
|
|
50
|
-
# verify the version, then restart the host
|
|
51
|
-
node -e "console.log(require('memory-eternal/package.json').version)"
|
|
52
|
-
```
|
|
53
|
-
|
|
54
|
-
#### 🖥️ Desktop support policy (read this first)
|
|
55
|
-
|
|
56
|
-
- **The official DeepSeek Harness desktop build is the priority — and the only guaranteed target** (the official Electron release; its profile is named `desktop`). The v0.9.4 → v0.9.6 fixes all target it: the 0.1.7 settings-service rewrite, `schemastery 3.18.4` volatile live references, and window-titlebar avoidance (`data-windows-titlebar`, so a full-screen overlay can no longer cover minimize/maximize/close).
|
|
57
|
-
- **The author's own `dsh-desktop` (`dsh-desktop-shell` / `dsh-ui-*` / `dsh-plugin-marketplace`) is discontinued** and is no longer a support target — the official desktop build covers the same ground, and maintaining two shells only splits compatibility. Note that its profile still pins `dsh-desktop-shell@0.3.0`, which has been unpublished from npm and makes `pnpm install` fail outright; migrating to the official desktop build and dropping those dependencies is recommended.
|
|
58
|
-
- Compatibility matrix (both verified): the official `desktop` profile (schemastery **3.18.4**) and the `web` profile behind `dsh web` (schemastery **3.18.1**) share the same code path.
|
|
59
|
-
|
|
60
|
-
After **restarting the host**, three things are live immediately:
|
|
61
|
-
|
|
62
|
-
| Effect | Where |
|
|
63
|
-
|---|---|
|
|
64
|
-
| Auto-capture of knowledge cards | Happens every turn, no action needed |
|
|
65
|
-
| `memory_recall` tool | Agent calls it automatically when it needs history |
|
|
66
|
-
| Visual UI | Sidebar bottom `Memory` button / Settings → Memory |
|
|
67
|
-
|
|
68
|
-
**Entry**: The sidebar-footer `Memory` button opens the vault (its left rail includes Cards / Graph / Usage / **Audit Center** / Recycle Bin / **Memory Config**); "DSH Settings → Memory" is the pure config page.
|
|
69
|
-
|
|
70
|
-
**UI language**: The whole UI is bilingual (English / 中文) and follows **DSH Settings → Language** in real time — Cards, Graph, Audit Center, card templates, config panel all included; the standalone web page follows the browser language.
|
|
71
|
-
|
|
72
|
-
**Edit config**: Vault left rail "Memory Config" (or DSH Settings → Memory) → DSH memory config / cost control / auto-audit config / self-hosting — just hit "Save Config". `autoWebMode` / `watchdogAutoSpawn` changes require a DSH restart.
|
|
73
|
-
|
|
74
|
-
### 🟨 Claude Code
|
|
75
|
-
|
|
76
|
-
```bash
|
|
77
|
-
npm i -g memory-eternal # installs CLI + MCP (auto-writes ~/.claude.json + SessionEnd hook)
|
|
78
|
-
```
|
|
79
|
-
|
|
80
|
-
Ready after install: say "recall 数据库选型" in a session → auto-retrieves memory; on session end / before context compaction → auto-captures.
|
|
81
|
-
|
|
82
|
-
### 🟧 Codex CLI / Cursor
|
|
83
|
-
|
|
84
|
-
```bash
|
|
85
|
-
npm i -g memory-eternal # auto-writes Codex config.toml / Cursor mcp.json
|
|
86
|
-
```
|
|
87
|
-
|
|
88
|
-
Restart the tool → MCP is in the list; just use: `用 memory_recall 查一下项目历史决策`.
|
|
89
|
-
|
|
90
|
-
### 🟩 Browser (no Agent needed)
|
|
91
|
-
|
|
92
|
-
```bash
|
|
93
|
-
dsh-memory open # starts web + opens browser (default http://127.0.0.1:7999)
|
|
94
|
-
```
|
|
95
|
-
|
|
96
|
-
Stats / search / card grid (add-edit-merge-import-export) / knowledge graph — all here. Same UI as the DSH embed; data stays in sync.
|
|
97
|
-
|
|
98
|
-
> **zcode (Zhipu)**: no native MCP; bridge via [zcode-open-bridge](https://github.com/tizerluo/zcode-open-bridge) or use the CLI directly.
|
|
99
|
-
|
|
100
|
-
---
|
|
101
|
-
|
|
102
|
-
## 📖 Command Reference
|
|
103
|
-
|
|
104
|
-
```bash
|
|
105
|
-
dsh-memory recall "database selection" # retrieve
|
|
106
|
-
dsh-memory capture "important note..." # manual capture (- reads stdin)
|
|
107
|
-
dsh-memory sweep ~/.claude/projects # mine existing sessions
|
|
108
|
-
dsh-memory setup [--dry-run] # re-run / preview auto-mount (idempotent)
|
|
109
|
-
dsh-memory mcp # MCP stdio (mount to any MCP client)
|
|
110
|
-
dsh-memory serve [--port 7999] # run web in foreground
|
|
111
|
-
dsh-memory open # ensure web alive + open browser
|
|
112
|
-
dsh-memory watchdog [--port 7799] # watchdog keep-alive (standalone process)
|
|
113
|
-
```
|
|
114
|
-
|
|
115
|
-
When not running on DSH, the `dsh-memory` command comes from `npm i -g`.
|
|
116
|
-
|
|
117
|
-
---
|
|
118
|
-
|
|
119
|
-
## ⚙️ Self-hosting (plain words)
|
|
120
|
-
|
|
121
|
-
Three concepts, don't mix them:
|
|
122
|
-
|
|
123
|
-
- **How the web server stays alive** (`autoWebMode`) → `init`=pull once at DSH start (default); `interval`=DSH in-process timer probes & auto-restarts (0 extra memory); `manual`=fully manual, only from `dsh-memory open`.
|
|
124
|
-
- **Watchdog process** (`watchdogAutoSpawn`, default on) → a **standalone** node process that can pull web up even after DSH exits (~+47 MB RAM). Only turn on for 7×24 keep-alive.
|
|
125
|
-
- **Auto-mount MCP** (`autoMcpSetup`, default off) → whether to auto-write MCP into Claude Code/Codex/Cursor config. Off = don't touch your machine config; run `dsh-memory setup` manually when needed.
|
|
126
|
-
|
|
127
|
-
**Change these**: Vault left rail "Memory Config" (or DSH Settings → Memory) → edit the table and save; `autoWebMode` / `watchdogAutoSpawn` need a DSH restart.
|
|
128
|
-
|
|
129
|
-
**MCP is a protocol, not a resident service**: the agent spawns it per session and exits when done — no "auto-start on boot" concept.
|
|
130
|
-
|
|
131
|
-
### Three deployment intensities
|
|
132
|
-
|
|
133
|
-
| Scenario | Config | Memory |
|
|
134
|
-
|---|---|---|
|
|
135
|
-
| Personal dev (default) | `autoWebMode=init` + `watchdogAutoSpawn=off` | web 47 MB |
|
|
136
|
-
| Resident 7×24 | `watchdogAutoSpawn=on` | web + watchdog 47+47 MB |
|
|
137
|
-
| True boot auto-start (no DSH) | Windows Task Scheduler runs `dsh-memory watchdog --port 7799 --interval 5000 --max-restart 10` | same |
|
|
138
|
-
|
|
139
|
-
---
|
|
140
|
-
|
|
141
|
-
## ⚙️ Memory Config (plain words)
|
|
142
|
-
|
|
143
|
-
> All settings live in the **vault left rail "Memory Config"** (or DSH Settings → Memory) — edit and hit "Save". Here's the full page (plugin info / Agent MCP mount status / auto-audit config):
|
|
144
|
-
|
|
145
|
-
<p align="center">
|
|
146
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-config.png" width="880" alt="Memory config page" />
|
|
147
|
-
</p>
|
|
148
|
-
|
|
149
|
-
### 1. Most used
|
|
150
|
-
|
|
151
|
-
| Setting | Default | In plain words |
|
|
152
|
-
|---|---|---|
|
|
153
|
-
| Auto capture | on | auto-store useful content as cards after each turn |
|
|
154
|
-
| Auto recall | on | AI auto-queries memory when it needs history |
|
|
155
|
-
| Vault dir | `~/.dsh/memory-vault` | where memory lives, plain Markdown & git-able |
|
|
156
|
-
|
|
157
|
-
#### Multiple vaults (per-project isolation)
|
|
158
|
-
|
|
159
|
-
Two extra fields in `memory-eternal-config.json`:
|
|
160
|
-
|
|
161
|
-
```json
|
|
162
|
-
{
|
|
163
|
-
"vaultProfiles": [{ "name": "work", "path": "D:/vaults/work" }],
|
|
164
|
-
"activeVault": "work"
|
|
165
|
-
}
|
|
166
|
-
```
|
|
167
|
-
|
|
168
|
-
Resolution order: `MEMORY_VAULT_DIR` env → the `path` of the `vaultProfiles` entry whose `name` matches `activeVault` → `vaultDir` → default `~/.dsh/memory-vault`.
|
|
169
|
-
|
|
170
|
-
**Since v0.9.8 the CLI / MCP / hooks / standalone web / sweep share the host's exact order** — previously only the host honoured `activeVault`, so switching vaults left the terminal and hooks writing to the default vault and split your memory in two.
|
|
171
|
-
|
|
172
|
-
> Note: the settings page still has no form for `vaultProfiles` / `activeVault` (edit the config file by hand), and per-workspace auto-selection is not implemented yet.
|
|
173
|
-
|
|
174
|
-
### 2. Save money (important)
|
|
175
|
-
|
|
176
|
-
| Setting | Default | In plain words |
|
|
177
|
-
|---|---|---|
|
|
178
|
-
| **Distill cards** | on | **compress** a conversation into a sharp card (calls AI, costs money). **Off = store raw text, zero cost** |
|
|
179
|
-
| **Dedup feeds AI** | on | judge if new content is a duplicate (calls AI). **Off = simple dedup**, saves one AI call |
|
|
180
|
-
| Distill output cap | 900 | max chars per compress, bigger = sharper but pricier |
|
|
181
|
-
| Recall min score | 2 | how "close" a match must be to return; bigger = sharper but leaks more (cheaper) |
|
|
182
|
-
| Min capture chars | 200 | too-short chats aren't stored (avoids small-talk waste) |
|
|
183
|
-
| Daily quota | 60 | max cards per day, prevents AI burning money |
|
|
184
|
-
|
|
185
|
-
### 3. How the service runs
|
|
186
|
-
|
|
187
|
-
| Setting | Default | In plain words |
|
|
188
|
-
|---|---|---|
|
|
189
|
-
| Keep-alive `autoWebMode` | init | `init`=open web once at DSH start; `interval`=periodically check & restart if dead; `manual`=fully manual |
|
|
190
|
-
| Watchdog `watchdogAutoSpawn` | on | a **standalone process** keeps web alive (+47 MB). Personal use can turn off |
|
|
191
|
-
| Auto-mount MCP `autoMcpSetup` | off | **lets Claude Code / Codex / Cursor use your memory**. On = auto-configures them; Off = never touches your config, run `dsh-memory setup` manually |
|
|
192
|
-
|
|
193
|
-
> 💰 **To save money**: turn `Distill cards` off, lower `Distill output cap`, raise `Recall min score`.
|
|
194
|
-
|
|
195
|
-
### 🎯 One-click presets
|
|
196
|
-
|
|
197
|
-
Top of the config page: **🟢 A Light / 💰 B Budget / ⭐ C Premium** — click to fill, then Save:
|
|
198
|
-
|
|
199
|
-
| Plan | Scenario | Keep-alive | Watchdog | Distill | Distill cap | Recall min | Memory | LLM cost |
|
|
200
|
-
|---|---|---|---|---|---|---|---|---|
|
|
201
|
-
| 🟢 **A Light** | Personal dev (default) | init | off | on | 900 | 2 | ~47 MB | normal |
|
|
202
|
-
| 💰 **B Budget** | Tight budget / many Agents | init | off | **off** | 500 | 3 | ~47 MB | **~0** |
|
|
203
|
-
| ⭐ **C Premium** | Long projects / teams | interval | **on** | on | 1200 | 1 | ~94 MB | high |
|
|
204
|
-
|
|
205
|
-
---
|
|
206
|
-
|
|
207
|
-
## 🔔 Capture Log & Failure Alerts
|
|
208
|
-
|
|
209
|
-
Auto-capture is a silent background pipeline: when it broke, the only symptom used to be "no new cards" with no visible cause. Since v0.9.0 it speaks up.
|
|
210
|
-
|
|
211
|
-
- **Capture log**: Settings → Memory → Usage / Today shows the last 100 run entries: `🚀 boot` / `👂 session attached (which event API + event count)` / `✅ card created` / `➕ update appended` / `⏭ skipped (reason)` / `❌ failed (reason)`.
|
|
212
|
-
- **Active alerts**: any failure turns the strip red at the top of the memory library *and* injects "auto-capture failed + reason" into the agent context, so the agent tells you in its first sentence — no need to dig through logs.
|
|
213
|
-
- **Stall watchdog**: if turns start but no turn-stopping event arrives for 15 minutes (e.g. DSH renamed the event), a 10-minute sweep reports it.
|
|
214
|
-
- **Self-adapting event API**: the session event API is detected automatically (`ownEvents()` → `snapshotEvents()` → `events`), so a DSH upgrade that changes the API can no longer silently break capture.
|
|
215
|
-
|
|
216
|
-
---
|
|
217
|
-
|
|
218
|
-
## 🛡️ Audit Center & Recycle Bin
|
|
219
|
-
|
|
220
|
-
> **Agents cannot approve on your behalf (since v0.9.1).** Whenever audit is active, the plugin injects a red line into the agent context: new cards stay `pending`, and calling the `approve`/`reject` endpoints (or any equivalent bypass) is forbidden. The decision is always yours.
|
|
221
|
-
|
|
222
|
-
New cards go to the **Audit Center** (`pending`) by default and enter the main vault only after you approve them; rejected ones move to "Rejected", where you can restore or delete to the recycle bin. Cards matching an exemption (audit mode = skip all / exempt agents / exempt kinds) go straight in; recycle-bin cards are recoverable within 30 days, then auto-purged.
|
|
223
|
-
|
|
224
|
-
<p align="center">
|
|
225
|
-
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/audit-center.png" width="880" alt="Audit Center" />
|
|
226
|
-
</p>
|
|
227
|
-
|
|
228
|
-
- **Pending / Rejected** tabs, filtered by type / date / agent; select all and approve / reject / delete-to-recycle in one click.
|
|
229
|
-
- Rules in "Memory Config → Auto-audit config": `audit mode` (audit all / skip all) + `exempt agents` + `exempt kinds` + `recycle retention days`.
|
|
230
|
-
|
|
231
|
-
### 🥇 Why the audit system is more reliable (vs other memory products)
|
|
232
|
-
|
|
233
|
-
Most memory products (mem0 / Zep / agentmemory…) auto-ingest **everything** the moment a conversation ends, good or bad — noise, wrong facts, and sensitive content all go in and get recalled later, **polluting context and amplifying hallucinations**.
|
|
234
|
-
|
|
235
|
-
memory-eternal uses **human-in-the-loop auditing** — only trusted content enters the main vault:
|
|
236
|
-
|
|
237
|
-
| Dimension | Other memory products | memory-eternal audit system |
|
|
238
|
-
|---|---|---|
|
|
239
|
-
| Ingest | Auto-ingest all, no gate | New cards first enter the **Audit Center (`pending`)**, approved before entering the vault |
|
|
240
|
-
| Quality | No filtering of noise/errors | Only cards you've confirmed → more accurate recall, less noise |
|
|
241
|
-
| Traceability | No source/audit trail | Every card carries `submittedBy` author + `pending/approved/rejected` state |
|
|
242
|
-
| No-friction | — | Exempt agents / exempt kinds hit → trusted cards go straight in, zero wait |
|
|
243
|
-
| Safety | Delete = gone forever | Recycle-bin soft delete, recoverable within 30 days |
|
|
244
|
-
|
|
245
|
-
---
|
|
246
|
-
|
|
247
|
-
## 🧬 Why Fully Self-built
|
|
248
|
-
|
|
249
|
-
Most memory solutions lean on third-party frameworks / spin up an MCP service / lock memory in a private store. This plugin builds the skeleton itself — **zero third-party runtime deps**, logic readable line by line:
|
|
250
|
-
|
|
251
|
-
| Module | Self-built | Replaces |
|
|
252
|
-
|---|---|---|
|
|
253
|
-
| Dedup | lexical Jaccard bigram (0.62) + semantic dedup | duplicate-card prevention |
|
|
254
|
-
| Retrieval | CJK-aware: Chinese whole-word + char bigram | no full-text search engine needed |
|
|
255
|
-
| Graph | force-directed + `[[wikilink]]`/shared-tag edges | see knowledge links at a glance |
|
|
256
|
-
| Storage | plain `.md` with frontmatter | not locked in, readable, git-able, any tool can read |
|
|
257
|
-
|
|
258
|
-
> Same direction as popular projects (summarize→store→recall), but positioned differently: **local, self-built, zero-dep, readable & controllable**. If you already use mem0/Zep etc., just layer this as a "local persistent memory base".
|
|
259
|
-
|
|
260
|
-
---
|
|
261
|
-
|
|
262
|
-
## 🛠 Development / Test
|
|
263
|
-
|
|
264
|
-
```bash
|
|
265
|
-
npm i
|
|
266
|
-
npm test # unit tests: vault dedup/retrieval/graph + capture pipeline + API shapes
|
|
267
|
-
npm run build # builds lib/client.js (DSH embed) + web/app.js (standalone web bundle)
|
|
268
|
-
```
|
|
269
|
-
|
|
270
|
-
---
|
|
271
|
-
|
|
272
|
-
## 🐞 Reporting a bug
|
|
273
|
-
|
|
274
|
-
The left rail has a **🐞 Report a bug** entry: describe the problem, then either
|
|
275
|
-
|
|
276
|
-
- **Open prefilled issue on GitHub** — title, body, diagnostics and the `bug` label are filled in; one more click on **Submit** files it;
|
|
277
|
-
- **Copy AI prompt** — paste it into your AI chat and it will run `gh` to de-duplicate, file the issue and report the URL back.
|
|
278
|
-
|
|
279
|
-
> **Why not one-click submission?** GitHub forbids anonymous issue creation, a token inside the plugin would be extracted by decompiling, and OAuth / a relay needs hosted infrastructure — hence "pre-fill + one click".
|
|
280
|
-
> Diagnostics are **auto-redacted** (home directory → `~`; `sk-` / `ghp_` / `github_pat_` / `api_key:` → `***`), but do skim them before posting publicly.
|
|
281
|
-
|
|
282
|
-
If you cannot reach the UI, paste the prompt below into your AI chat and replace the last placeholder with your problem:
|
|
283
|
-
|
|
284
|
-
```text
|
|
285
|
-
I hit a problem while using memory-eternal (a DeepSeek Harness memory plugin). Please file it on GitHub for me.
|
|
286
|
-
|
|
287
|
-
Repo: https://github.com/EternalNight996/memory-eternal
|
|
288
|
-
|
|
289
|
-
Workflow:
|
|
290
|
-
|
|
291
|
-
1. Run `gh issue list --repo EternalNight996/memory-eternal --state open --limit 50` first: if a matching issue exists, add a comment with `gh issue comment <n> --body-file <file>` instead of opening a duplicate.
|
|
292
|
-
2. Otherwise create it with `gh issue create --repo EternalNight996/memory-eternal --title "[Bug] <one-line summary>" --body-file <file>`, using sections: Symptoms / Steps to reproduce / Expected / Actual / Environment (plugin, DSH, OS, Node) / Diagnostics.
|
|
293
|
-
3. If `gh` is not authenticated or unavailable, do NOT try to submit: output a GitHub new-issue link with the title and body pre-filled instead, and I will click submit myself.
|
|
294
|
-
4. Report the resulting issue URL back to me.
|
|
295
|
-
|
|
296
|
-
Keep my description verbatim - do not rewrite or summarise it. Put the diagnostics under the Diagnostics section as-is.
|
|
297
|
-
|
|
298
|
-
My description:
|
|
299
|
-
<write your problem here>
|
|
300
|
-
|
|
301
|
-
Diagnostics:
|
|
302
|
-
<paste the diagnostics copied from the in-app Report-a-bug dialog>
|
|
303
|
-
```
|
|
304
|
-
|
|
305
|
-
---
|
|
306
|
-
|
|
307
|
-
## 📋 Changelog
|
|
308
|
-
|
|
309
|
-
> **Withdrawn versions**: **v0.9.0 – v0.9.5 are all deprecated on npm, and the release tags for v0.9.1 / v0.9.2 / v0.9.3 / v0.9.4 have been removed from git** (v0.9.5 is merely superseded, so its tag stays) — v0.9.1/v0.9.2 ship the blank-memory-page defect, v0.9.0 false-alarms its capture warnings, v0.9.3 does not support DSH v0.1.7-rc.2 (the plugin stops mounting entirely: the settings service changed and the client-side `settingsScope` is gone), v0.9.4 crashes under the official desktop build (schemastery 3.18.4 volatile live references) with `cfg.vaultDir.trim is not a function`, and **v0.9.5's full-screen overlay covers the desktop shell's window controls (its top-right "×" sits on the window Close button — one click quits the whole shell)**. Use **v0.9.6+** (`npm i memory-eternal@latest`).
|
|
310
|
-
|
|
311
|
-
> **DSH compatibility**: `>=0.1.5-alpha.2 <0.2.0`. **v0.9.4 adds support for DSH v0.1.7-rc.2**, which replaced the settings service with a forms-only API and removed `@deepseek-ai/dsh-client-runtime` / `settingsScope`; **v0.9.5 adds support for schemastery ≥3.18.4 volatile live references** (the shape the official desktop profile uses, while the web profile still ships 3.18.1 — both work); **v0.9.6 keeps full-screen overlays clear of the desktop shell's window controls**. The 0.1.5 line still uses the legacy `settings.register` path; both paths are kept.
|
|
312
|
-
|
|
313
|
-
| Version | Date | Highlights |
|
|
314
|
-
|---|---|---|
|
|
315
|
-
| **v0.9.
|
|
316
|
-
| **v0.9.
|
|
317
|
-
| **v0.9.
|
|
318
|
-
| **v0.9.
|
|
319
|
-
| **v0.9.
|
|
320
|
-
| **v0.9.
|
|
321
|
-
| **v0.9.
|
|
322
|
-
| **v0.9.
|
|
323
|
-
| **v0.9.
|
|
324
|
-
| **v0.9.
|
|
325
|
-
| **v0.9.
|
|
326
|
-
| **v0.9.
|
|
327
|
-
| **v0.9.
|
|
328
|
-
| **v0.9.
|
|
329
|
-
| **v0.9.
|
|
330
|
-
| **v0.
|
|
331
|
-
| **v0.
|
|
332
|
-
| **v0.3.
|
|
333
|
-
| v0.
|
|
334
|
-
| v0.
|
|
335
|
-
| v0.1.
|
|
336
|
-
| v0.1.
|
|
337
|
-
|
|
338
|
-
|
|
339
|
-
|
|
340
|
-
|
|
341
|
-
|
|
342
|
-
|
|
343
|
-
|
|
344
|
-
|
|
345
|
-
|
|
346
|
-
|
|
347
|
-
|
|
348
|
-
|
|
349
|
-
|
|
350
|
-
|
|
351
|
-
|
|
352
|
-
|
|
353
|
-
>
|
|
354
|
-
|
|
355
|
-
|
|
356
|
-
|
|
357
|
-
|
|
358
|
-
|
|
359
|
-
|
|
360
|
-
|
|
361
|
-
|
|
362
|
-
|
|
363
|
-
|
|
364
|
-
>
|
|
365
|
-
>
|
|
1
|
+
# 🧠 memory-eternal — A "second brain" for your AI
|
|
2
|
+
|
|
3
|
+
<p align="center">
|
|
4
|
+
<img src="https://img.shields.io/badge/DeepSeek%20Harness-plugin-3B82F6" alt="DSH plugin" />
|
|
5
|
+
<img src="https://img.shields.io/npm/v/memory-eternal" alt="npm version" />
|
|
6
|
+
<img src="https://img.shields.io/github/stars/EternalNight996/memory-eternal?style=flat" alt="GitHub stars" />
|
|
7
|
+
<img src="https://img.shields.io/github/license/EternalNight996/memory-eternal" alt="license" />
|
|
8
|
+
<a href="https://dsh.market/"><img src="https://raw.githubusercontent.com/2BingLing/dsh-market/master/assets/readme/badge-listed.svg" alt="DSH Market listed" /></a>
|
|
9
|
+
</p>
|
|
10
|
+
|
|
11
|
+
<p align="center">
|
|
12
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-eternal.gif" width="880" alt="Auto-capture + visual library + knowledge graph (demo)" />
|
|
13
|
+
</p>
|
|
14
|
+
|
|
15
|
+
> **Auto-captures knowledge after every conversation and survives across sessions; recall fetches only the relevant chunks — saves tokens, less noise.**
|
|
16
|
+
> Fully self-built, zero third-party memory framework, no DSH source changes, one vault shared by every Agent, SQLite persistent storage, zero external dependencies.
|
|
17
|
+
|
|
18
|
+
<p align="center"><strong>⭐ Star it if you like it!</strong> <br/><sub>DSH one-liner: <code>dsh plugin --profile web add memory-eternal</code></sub></p>
|
|
19
|
+
|
|
20
|
+
<p align="center">
|
|
21
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-popup.png" width="32%" alt="Memory popup: knowledge cards / search / knowledge graph" />
|
|
22
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-settings.png" width="32%" alt="DSH Settings → Memory: all options" />
|
|
23
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-sidebar.png" width="32%" alt="Sidebar quick entry" />
|
|
24
|
+
</p>
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## 🚀 Get Started in 5 Minutes
|
|
29
|
+
|
|
30
|
+
### 🟦 DeepSeek Harness (DSH) — focus
|
|
31
|
+
|
|
32
|
+
**Install** (official desktop app via the plugin marketplace, `dsh web` via one CLI line):
|
|
33
|
+
|
|
34
|
+
```bash
|
|
35
|
+
# 1) Official DeepSeek Harness desktop app (recommended): Settings -> Plugins -> search memory-eternal
|
|
36
|
+
# Equivalent CLI (that shell's profile is named "desktop"):
|
|
37
|
+
dsh plugin --profile desktop add memory-eternal
|
|
38
|
+
|
|
39
|
+
# 2) dsh web (browser):
|
|
40
|
+
dsh plugin --profile web add memory-eternal
|
|
41
|
+
|
|
42
|
+
# or update directly in the profile (pnpm workspace). Use pnpm — `npm install` throws EUNSUPPORTEDPROTOCOL
|
|
43
|
+
cd ~/.dsh/profiles/web && pnpm add memory-eternal@latest
|
|
44
|
+
|
|
45
|
+
# right after a release, @latest can be held back by pnpm's minimum-release-age gate or a cached
|
|
46
|
+
# packument (it silently stays on the old version): pin the version instead — pnpm adds it to the
|
|
47
|
+
# workspace's minimumReleaseAgeExclude automatically
|
|
48
|
+
cd ~/.dsh/profiles/web && pnpm add memory-eternal@0.9.6
|
|
49
|
+
|
|
50
|
+
# verify the version, then restart the host
|
|
51
|
+
node -e "console.log(require('memory-eternal/package.json').version)"
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
#### 🖥️ Desktop support policy (read this first)
|
|
55
|
+
|
|
56
|
+
- **The official DeepSeek Harness desktop build is the priority — and the only guaranteed target** (the official Electron release; its profile is named `desktop`). The v0.9.4 → v0.9.6 fixes all target it: the 0.1.7 settings-service rewrite, `schemastery 3.18.4` volatile live references, and window-titlebar avoidance (`data-windows-titlebar`, so a full-screen overlay can no longer cover minimize/maximize/close).
|
|
57
|
+
- **The author's own `dsh-desktop` (`dsh-desktop-shell` / `dsh-ui-*` / `dsh-plugin-marketplace`) is discontinued** and is no longer a support target — the official desktop build covers the same ground, and maintaining two shells only splits compatibility. Note that its profile still pins `dsh-desktop-shell@0.3.0`, which has been unpublished from npm and makes `pnpm install` fail outright; migrating to the official desktop build and dropping those dependencies is recommended.
|
|
58
|
+
- Compatibility matrix (both verified): the official `desktop` profile (schemastery **3.18.4**) and the `web` profile behind `dsh web` (schemastery **3.18.1**) share the same code path.
|
|
59
|
+
|
|
60
|
+
After **restarting the host**, three things are live immediately:
|
|
61
|
+
|
|
62
|
+
| Effect | Where |
|
|
63
|
+
|---|---|
|
|
64
|
+
| Auto-capture of knowledge cards | Happens every turn, no action needed |
|
|
65
|
+
| `memory_recall` tool | Agent calls it automatically when it needs history |
|
|
66
|
+
| Visual UI | Sidebar bottom `Memory` button / Settings → Memory |
|
|
67
|
+
|
|
68
|
+
**Entry**: The sidebar-footer `Memory` button opens the vault (its left rail includes Cards / Graph / Usage / **Audit Center** / Recycle Bin / **Memory Config**); "DSH Settings → Memory" is the pure config page.
|
|
69
|
+
|
|
70
|
+
**UI language**: The whole UI is bilingual (English / 中文) and follows **DSH Settings → Language** in real time — Cards, Graph, Audit Center, card templates, config panel all included; the standalone web page follows the browser language.
|
|
71
|
+
|
|
72
|
+
**Edit config**: Vault left rail "Memory Config" (or DSH Settings → Memory) → DSH memory config / cost control / auto-audit config / self-hosting — just hit "Save Config". `autoWebMode` / `watchdogAutoSpawn` changes require a DSH restart.
|
|
73
|
+
|
|
74
|
+
### 🟨 Claude Code
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
npm i -g memory-eternal # installs CLI + MCP (auto-writes ~/.claude.json + SessionEnd hook)
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Ready after install: say "recall 数据库选型" in a session → auto-retrieves memory; on session end / before context compaction → auto-captures.
|
|
81
|
+
|
|
82
|
+
### 🟧 Codex CLI / Cursor
|
|
83
|
+
|
|
84
|
+
```bash
|
|
85
|
+
npm i -g memory-eternal # auto-writes Codex config.toml / Cursor mcp.json
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
Restart the tool → MCP is in the list; just use: `用 memory_recall 查一下项目历史决策`.
|
|
89
|
+
|
|
90
|
+
### 🟩 Browser (no Agent needed)
|
|
91
|
+
|
|
92
|
+
```bash
|
|
93
|
+
dsh-memory open # starts web + opens browser (default http://127.0.0.1:7999)
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
Stats / search / card grid (add-edit-merge-import-export) / knowledge graph — all here. Same UI as the DSH embed; data stays in sync.
|
|
97
|
+
|
|
98
|
+
> **zcode (Zhipu)**: no native MCP; bridge via [zcode-open-bridge](https://github.com/tizerluo/zcode-open-bridge) or use the CLI directly.
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
## 📖 Command Reference
|
|
103
|
+
|
|
104
|
+
```bash
|
|
105
|
+
dsh-memory recall "database selection" # retrieve
|
|
106
|
+
dsh-memory capture "important note..." # manual capture (- reads stdin)
|
|
107
|
+
dsh-memory sweep ~/.claude/projects # mine existing sessions
|
|
108
|
+
dsh-memory setup [--dry-run] # re-run / preview auto-mount (idempotent)
|
|
109
|
+
dsh-memory mcp # MCP stdio (mount to any MCP client)
|
|
110
|
+
dsh-memory serve [--port 7999] # run web in foreground
|
|
111
|
+
dsh-memory open # ensure web alive + open browser
|
|
112
|
+
dsh-memory watchdog [--port 7799] # watchdog keep-alive (standalone process)
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
When not running on DSH, the `dsh-memory` command comes from `npm i -g`.
|
|
116
|
+
|
|
117
|
+
---
|
|
118
|
+
|
|
119
|
+
## ⚙️ Self-hosting (plain words)
|
|
120
|
+
|
|
121
|
+
Three concepts, don't mix them:
|
|
122
|
+
|
|
123
|
+
- **How the web server stays alive** (`autoWebMode`) → `init`=pull once at DSH start (default); `interval`=DSH in-process timer probes & auto-restarts (0 extra memory); `manual`=fully manual, only from `dsh-memory open`.
|
|
124
|
+
- **Watchdog process** (`watchdogAutoSpawn`, default on) → a **standalone** node process that can pull web up even after DSH exits (~+47 MB RAM). Only turn on for 7×24 keep-alive.
|
|
125
|
+
- **Auto-mount MCP** (`autoMcpSetup`, default off) → whether to auto-write MCP into Claude Code/Codex/Cursor config. Off = don't touch your machine config; run `dsh-memory setup` manually when needed.
|
|
126
|
+
|
|
127
|
+
**Change these**: Vault left rail "Memory Config" (or DSH Settings → Memory) → edit the table and save; `autoWebMode` / `watchdogAutoSpawn` need a DSH restart.
|
|
128
|
+
|
|
129
|
+
**MCP is a protocol, not a resident service**: the agent spawns it per session and exits when done — no "auto-start on boot" concept.
|
|
130
|
+
|
|
131
|
+
### Three deployment intensities
|
|
132
|
+
|
|
133
|
+
| Scenario | Config | Memory |
|
|
134
|
+
|---|---|---|
|
|
135
|
+
| Personal dev (default) | `autoWebMode=init` + `watchdogAutoSpawn=off` | web 47 MB |
|
|
136
|
+
| Resident 7×24 | `watchdogAutoSpawn=on` | web + watchdog 47+47 MB |
|
|
137
|
+
| True boot auto-start (no DSH) | Windows Task Scheduler runs `dsh-memory watchdog --port 7799 --interval 5000 --max-restart 10` | same |
|
|
138
|
+
|
|
139
|
+
---
|
|
140
|
+
|
|
141
|
+
## ⚙️ Memory Config (plain words)
|
|
142
|
+
|
|
143
|
+
> All settings live in the **vault left rail "Memory Config"** (or DSH Settings → Memory) — edit and hit "Save". Here's the full page (plugin info / Agent MCP mount status / auto-audit config):
|
|
144
|
+
|
|
145
|
+
<p align="center">
|
|
146
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/memory-config.png" width="880" alt="Memory config page" />
|
|
147
|
+
</p>
|
|
148
|
+
|
|
149
|
+
### 1. Most used
|
|
150
|
+
|
|
151
|
+
| Setting | Default | In plain words |
|
|
152
|
+
|---|---|---|
|
|
153
|
+
| Auto capture | on | auto-store useful content as cards after each turn |
|
|
154
|
+
| Auto recall | on | AI auto-queries memory when it needs history |
|
|
155
|
+
| Vault dir | `~/.dsh/memory-vault` | where memory lives, plain Markdown & git-able |
|
|
156
|
+
|
|
157
|
+
#### Multiple vaults (per-project isolation)
|
|
158
|
+
|
|
159
|
+
Two extra fields in `memory-eternal-config.json`:
|
|
160
|
+
|
|
161
|
+
```json
|
|
162
|
+
{
|
|
163
|
+
"vaultProfiles": [{ "name": "work", "path": "D:/vaults/work" }],
|
|
164
|
+
"activeVault": "work"
|
|
165
|
+
}
|
|
166
|
+
```
|
|
167
|
+
|
|
168
|
+
Resolution order: `MEMORY_VAULT_DIR` env → the `path` of the `vaultProfiles` entry whose `name` matches `activeVault` → `vaultDir` → default `~/.dsh/memory-vault`.
|
|
169
|
+
|
|
170
|
+
**Since v0.9.8 the CLI / MCP / hooks / standalone web / sweep share the host's exact order** — previously only the host honoured `activeVault`, so switching vaults left the terminal and hooks writing to the default vault and split your memory in two.
|
|
171
|
+
|
|
172
|
+
> Note: the settings page still has no form for `vaultProfiles` / `activeVault` (edit the config file by hand), and per-workspace auto-selection is not implemented yet.
|
|
173
|
+
|
|
174
|
+
### 2. Save money (important)
|
|
175
|
+
|
|
176
|
+
| Setting | Default | In plain words |
|
|
177
|
+
|---|---|---|
|
|
178
|
+
| **Distill cards** | on | **compress** a conversation into a sharp card (calls AI, costs money). **Off = store raw text, zero cost** |
|
|
179
|
+
| **Dedup feeds AI** | on | judge if new content is a duplicate (calls AI). **Off = simple dedup**, saves one AI call |
|
|
180
|
+
| Distill output cap | 900 | max chars per compress, bigger = sharper but pricier |
|
|
181
|
+
| Recall min score | 2 | how "close" a match must be to return; bigger = sharper but leaks more (cheaper) |
|
|
182
|
+
| Min capture chars | 200 | too-short chats aren't stored (avoids small-talk waste) |
|
|
183
|
+
| Daily quota | 60 | max cards per day, prevents AI burning money |
|
|
184
|
+
|
|
185
|
+
### 3. How the service runs
|
|
186
|
+
|
|
187
|
+
| Setting | Default | In plain words |
|
|
188
|
+
|---|---|---|
|
|
189
|
+
| Keep-alive `autoWebMode` | init | `init`=open web once at DSH start; `interval`=periodically check & restart if dead; `manual`=fully manual |
|
|
190
|
+
| Watchdog `watchdogAutoSpawn` | on | a **standalone process** keeps web alive (+47 MB). Personal use can turn off |
|
|
191
|
+
| Auto-mount MCP `autoMcpSetup` | off | **lets Claude Code / Codex / Cursor use your memory**. On = auto-configures them; Off = never touches your config, run `dsh-memory setup` manually |
|
|
192
|
+
|
|
193
|
+
> 💰 **To save money**: turn `Distill cards` off, lower `Distill output cap`, raise `Recall min score`.
|
|
194
|
+
|
|
195
|
+
### 🎯 One-click presets
|
|
196
|
+
|
|
197
|
+
Top of the config page: **🟢 A Light / 💰 B Budget / ⭐ C Premium** — click to fill, then Save:
|
|
198
|
+
|
|
199
|
+
| Plan | Scenario | Keep-alive | Watchdog | Distill | Distill cap | Recall min | Memory | LLM cost |
|
|
200
|
+
|---|---|---|---|---|---|---|---|---|
|
|
201
|
+
| 🟢 **A Light** | Personal dev (default) | init | off | on | 900 | 2 | ~47 MB | normal |
|
|
202
|
+
| 💰 **B Budget** | Tight budget / many Agents | init | off | **off** | 500 | 3 | ~47 MB | **~0** |
|
|
203
|
+
| ⭐ **C Premium** | Long projects / teams | interval | **on** | on | 1200 | 1 | ~94 MB | high |
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
## 🔔 Capture Log & Failure Alerts
|
|
208
|
+
|
|
209
|
+
Auto-capture is a silent background pipeline: when it broke, the only symptom used to be "no new cards" with no visible cause. Since v0.9.0 it speaks up.
|
|
210
|
+
|
|
211
|
+
- **Capture log**: Settings → Memory → Usage / Today shows the last 100 run entries: `🚀 boot` / `👂 session attached (which event API + event count)` / `✅ card created` / `➕ update appended` / `⏭ skipped (reason)` / `❌ failed (reason)`.
|
|
212
|
+
- **Active alerts**: any failure turns the strip red at the top of the memory library *and* injects "auto-capture failed + reason" into the agent context, so the agent tells you in its first sentence — no need to dig through logs.
|
|
213
|
+
- **Stall watchdog**: if turns start but no turn-stopping event arrives for 15 minutes (e.g. DSH renamed the event), a 10-minute sweep reports it.
|
|
214
|
+
- **Self-adapting event API**: the session event API is detected automatically (`ownEvents()` → `snapshotEvents()` → `events`), so a DSH upgrade that changes the API can no longer silently break capture.
|
|
215
|
+
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
## 🛡️ Audit Center & Recycle Bin
|
|
219
|
+
|
|
220
|
+
> **Agents cannot approve on your behalf (since v0.9.1).** Whenever audit is active, the plugin injects a red line into the agent context: new cards stay `pending`, and calling the `approve`/`reject` endpoints (or any equivalent bypass) is forbidden. The decision is always yours.
|
|
221
|
+
|
|
222
|
+
New cards go to the **Audit Center** (`pending`) by default and enter the main vault only after you approve them; rejected ones move to "Rejected", where you can restore or delete to the recycle bin. Cards matching an exemption (audit mode = skip all / exempt agents / exempt kinds) go straight in; recycle-bin cards are recoverable within 30 days, then auto-purged.
|
|
223
|
+
|
|
224
|
+
<p align="center">
|
|
225
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/screen/audit-center.png" width="880" alt="Audit Center" />
|
|
226
|
+
</p>
|
|
227
|
+
|
|
228
|
+
- **Pending / Rejected** tabs, filtered by type / date / agent; select all and approve / reject / delete-to-recycle in one click.
|
|
229
|
+
- Rules in "Memory Config → Auto-audit config": `audit mode` (audit all / skip all) + `exempt agents` + `exempt kinds` + `recycle retention days`.
|
|
230
|
+
|
|
231
|
+
### 🥇 Why the audit system is more reliable (vs other memory products)
|
|
232
|
+
|
|
233
|
+
Most memory products (mem0 / Zep / agentmemory…) auto-ingest **everything** the moment a conversation ends, good or bad — noise, wrong facts, and sensitive content all go in and get recalled later, **polluting context and amplifying hallucinations**.
|
|
234
|
+
|
|
235
|
+
memory-eternal uses **human-in-the-loop auditing** — only trusted content enters the main vault:
|
|
236
|
+
|
|
237
|
+
| Dimension | Other memory products | memory-eternal audit system |
|
|
238
|
+
|---|---|---|
|
|
239
|
+
| Ingest | Auto-ingest all, no gate | New cards first enter the **Audit Center (`pending`)**, approved before entering the vault |
|
|
240
|
+
| Quality | No filtering of noise/errors | Only cards you've confirmed → more accurate recall, less noise |
|
|
241
|
+
| Traceability | No source/audit trail | Every card carries `submittedBy` author + `pending/approved/rejected` state |
|
|
242
|
+
| No-friction | — | Exempt agents / exempt kinds hit → trusted cards go straight in, zero wait |
|
|
243
|
+
| Safety | Delete = gone forever | Recycle-bin soft delete, recoverable within 30 days |
|
|
244
|
+
|
|
245
|
+
---
|
|
246
|
+
|
|
247
|
+
## 🧬 Why Fully Self-built
|
|
248
|
+
|
|
249
|
+
Most memory solutions lean on third-party frameworks / spin up an MCP service / lock memory in a private store. This plugin builds the skeleton itself — **zero third-party runtime deps**, logic readable line by line:
|
|
250
|
+
|
|
251
|
+
| Module | Self-built | Replaces |
|
|
252
|
+
|---|---|---|
|
|
253
|
+
| Dedup | lexical Jaccard bigram (0.62) + semantic dedup | duplicate-card prevention |
|
|
254
|
+
| Retrieval | CJK-aware: Chinese whole-word + char bigram | no full-text search engine needed |
|
|
255
|
+
| Graph | force-directed + `[[wikilink]]`/shared-tag edges | see knowledge links at a glance |
|
|
256
|
+
| Storage | plain `.md` with frontmatter | not locked in, readable, git-able, any tool can read |
|
|
257
|
+
|
|
258
|
+
> Same direction as popular projects (summarize→store→recall), but positioned differently: **local, self-built, zero-dep, readable & controllable**. If you already use mem0/Zep etc., just layer this as a "local persistent memory base".
|
|
259
|
+
|
|
260
|
+
---
|
|
261
|
+
|
|
262
|
+
## 🛠 Development / Test
|
|
263
|
+
|
|
264
|
+
```bash
|
|
265
|
+
npm i
|
|
266
|
+
npm test # unit tests: vault dedup/retrieval/graph + capture pipeline + API shapes
|
|
267
|
+
npm run build # builds lib/client.js (DSH embed) + web/app.js (standalone web bundle)
|
|
268
|
+
```
|
|
269
|
+
|
|
270
|
+
---
|
|
271
|
+
|
|
272
|
+
## 🐞 Reporting a bug
|
|
273
|
+
|
|
274
|
+
The left rail has a **🐞 Report a bug** entry: describe the problem, then either
|
|
275
|
+
|
|
276
|
+
- **Open prefilled issue on GitHub** — title, body, diagnostics and the `bug` label are filled in; one more click on **Submit** files it;
|
|
277
|
+
- **Copy AI prompt** — paste it into your AI chat and it will run `gh` to de-duplicate, file the issue and report the URL back.
|
|
278
|
+
|
|
279
|
+
> **Why not one-click submission?** GitHub forbids anonymous issue creation, a token inside the plugin would be extracted by decompiling, and OAuth / a relay needs hosted infrastructure — hence "pre-fill + one click".
|
|
280
|
+
> Diagnostics are **auto-redacted** (home directory → `~`; `sk-` / `ghp_` / `github_pat_` / `api_key:` → `***`), but do skim them before posting publicly.
|
|
281
|
+
|
|
282
|
+
If you cannot reach the UI, paste the prompt below into your AI chat and replace the last placeholder with your problem:
|
|
283
|
+
|
|
284
|
+
```text
|
|
285
|
+
I hit a problem while using memory-eternal (a DeepSeek Harness memory plugin). Please file it on GitHub for me.
|
|
286
|
+
|
|
287
|
+
Repo: https://github.com/EternalNight996/memory-eternal
|
|
288
|
+
|
|
289
|
+
Workflow:
|
|
290
|
+
|
|
291
|
+
1. Run `gh issue list --repo EternalNight996/memory-eternal --state open --limit 50` first: if a matching issue exists, add a comment with `gh issue comment <n> --body-file <file>` instead of opening a duplicate.
|
|
292
|
+
2. Otherwise create it with `gh issue create --repo EternalNight996/memory-eternal --title "[Bug] <one-line summary>" --body-file <file>`, using sections: Symptoms / Steps to reproduce / Expected / Actual / Environment (plugin, DSH, OS, Node) / Diagnostics.
|
|
293
|
+
3. If `gh` is not authenticated or unavailable, do NOT try to submit: output a GitHub new-issue link with the title and body pre-filled instead, and I will click submit myself.
|
|
294
|
+
4. Report the resulting issue URL back to me.
|
|
295
|
+
|
|
296
|
+
Keep my description verbatim - do not rewrite or summarise it. Put the diagnostics under the Diagnostics section as-is.
|
|
297
|
+
|
|
298
|
+
My description:
|
|
299
|
+
<write your problem here>
|
|
300
|
+
|
|
301
|
+
Diagnostics:
|
|
302
|
+
<paste the diagnostics copied from the in-app Report-a-bug dialog>
|
|
303
|
+
```
|
|
304
|
+
|
|
305
|
+
---
|
|
306
|
+
|
|
307
|
+
## 📋 Changelog
|
|
308
|
+
|
|
309
|
+
> **Withdrawn versions**: **v0.9.14 is deprecated** (its client-rendering changes hurt the feel and were reverted; its server-side algorithm work shipped in **v0.9.15**, whose rendering is identical to v0.9.13). **v0.9.0 – v0.9.5 are all deprecated on npm, and the release tags for v0.9.1 / v0.9.2 / v0.9.3 / v0.9.4 have been removed from git** (v0.9.5 is merely superseded, so its tag stays) — v0.9.1/v0.9.2 ship the blank-memory-page defect, v0.9.0 false-alarms its capture warnings, v0.9.3 does not support DSH v0.1.7-rc.2 (the plugin stops mounting entirely: the settings service changed and the client-side `settingsScope` is gone), v0.9.4 crashes under the official desktop build (schemastery 3.18.4 volatile live references) with `cfg.vaultDir.trim is not a function`, and **v0.9.5's full-screen overlay covers the desktop shell's window controls (its top-right "×" sits on the window Close button — one click quits the whole shell)**. Use **v0.9.6+** (`npm i memory-eternal@latest`).
|
|
310
|
+
|
|
311
|
+
> **DSH compatibility**: `>=0.1.5-alpha.2 <0.2.0`. **v0.9.4 adds support for DSH v0.1.7-rc.2**, which replaced the settings service with a forms-only API and removed `@deepseek-ai/dsh-client-runtime` / `settingsScope`; **v0.9.5 adds support for schemastery ≥3.18.4 volatile live references** (the shape the official desktop profile uses, while the web profile still ships 3.18.1 — both work); **v0.9.6 keeps full-screen overlays clear of the desktop shell's window controls**. The 0.1.5 line still uses the legacy `settings.register` path; both paths are kept.
|
|
312
|
+
|
|
313
|
+
| Version | Date | Highlights |
|
|
314
|
+
|---|---|---|
|
|
315
|
+
| **v0.9.16** | 2026-09-30 | **Fixed config saves silently not persisting (issue #12) + full config coverage.** ① **Save path**: the host `dsh-settings.write()` requires the revision held by the panel to match `describe()` **exactly**; once stale it throws `SettingsConflictError` and the save fails — the plugin now re-reads the latest revision and **retries once** (marked ♻ in the message). ② **Late volatile echo**: after a successful write the patch is overlaid on the local view (reopening the panel shows the new value immediately) and the overlay is dropped once the host snapshot catches up; the host POST now **re-reads after writing** and returns `pending` with an honest note ("written; restart DSH to apply from the config file") when the echo has not landed. ③ **Immediate save feedback** (requested earlier): ⏳ Saving / ✅ Saved / ⚠ error now appears right next to the Save button, including whether a retry or an echo was involved, and the button label no longer wrongly says "Exporting…". ④ **Full config coverage**: seven fields that previously could only be edited by hand are now in the panel — the **master switch `enabled`**, single-vault `vaultDir`, distillation route `captureProvider` / `captureModel`, cooldown `captureCooldownMs`, semantic recall `recallEmbedding` and `sessionBudgetChars`; the host `/config` gained 6 keys and the standalone web `/config` gained 9. ⑤ New **permanent guard tests**: `tests/config-coverage.test.mjs` asserts every Config field is covered by the host API, the standalone web API and the settings panel (missing one turns the suite red), and `tests/settings-save.test.mjs` (5 checks) pins revision retry, overlay fallback and "never swallow errors". `npm test` now runs **121 checks** |
|
|
316
|
+
| **v0.9.15** | 2026-09-29 | **Server-side graph speed-ups only — rendering is identical to v0.9.13.** ① **On-disk graph cache** keyed by fingerprint at `<vault>/memory-eternal-graph-cache.json` (atomic write, invalidated by fingerprint, skipped above 8MB, failures only cost a rebuild): measured cold start **422ms → 11ms** at 596 cards; ② **hashed bigrams + counting-sorted rare-gram index**: `bigramHashSet()` packs each bigram into a 32-bit integer (`Set<number>`; **capture de-duplication still uses the string version, so semantics are unchanged**), and the rare-gram index is built with a counting sort (202 → **54ms**); ③ **MinHash + LSH** candidate generation (48-dim signatures, 24 bands, unioned with the rare-gram index and then **verified exactly**): Jaccard calls 15,148 → 6,797 and the similarity stage 210 → 130ms. Full cold build **600 → 422ms**, edges unchanged from v0.9.13 (tag 2777 / similar 4). **Zero client changes** — no sprites, no static layer, no skeleton degradation (the v0.9.14 client work was reverted and deprecated because it hurt the feel). Adds `lib/minhash.js` + `tests/minhash.test.mjs` (4 checks); `npm test` runs **108 checks** |
|
|
317
|
+
| **v0.9.13** | 2026-09-28 | **Seven fixes from user feedback.** ① **Version tracking**: Plugin info now shows **running (loaded by host) / on disk / npm latest** side by side, with an amber warning when disk is newer ("X is installed on disk but the running process still has Y — restart to apply") plus a "Check for updates" button (server-side npm lookup, 10-minute cache, 4s timeout). ② **Copy failure**: the memory dialog runs inside an iframe without clipboard-write permission, so `navigator.clipboard.writeText` is always rejected — it now tries the Clipboard API, falls back to `document.execCommand('copy')`, and finally shows the text in a read-only box with a Select-all button; the iframe also gets `allow="clipboard-write; clipboard-read"`. ③ **Silent save**: the result now appears right next to the Save button (⏳ Saving… / ✅ Saved / ⚠ error) and the button label changed from the wrong "Exporting…" to "Saving…". ④ **Recycle bin**: restore / purge / empty-all now report success and failure, and the empty state explains itself and disables the buttons. ⑤ **Button feedback everywhere**: the audit centre's approve / reject / delete used to swallow everything in `catch {}`; it now counts successes/failures and reports them (and warns when nothing is selected). ⑥ **Graph zoom jank**: new `src/client/graph-lod.js` — **viewport culling** (off-screen nodes/edges are skipped) + a **label budget** (≤120 nodes draw all; ≤300 draw 160; ≤600 draw 90; more draw 60, prioritising focus, hover, search hits and highest degree) + **text-width caching** + **shadows off for large graphs**. ⑦ Adds `tests/graph-lod.test.mjs` (5 checks); `npm test` now runs **108 checks** |
|
|
318
|
+
| **v0.9.12** | 2026-09-28 | **New "Report a bug" entry (🐞 in the left rail)**: the dialog takes your description and then either ① **opens a pre-filled GitHub issue** (title, body, diagnostics and the `bug` label already filled — one more click on Submit files it), or ② **copies a ready-made AI prompt** (paste it into your chat and the AI runs `gh issue list` to de-duplicate, files the issue and reports the URL back). **Why not one-click submission?** GitHub forbids anonymous issue creation, a token shipped inside the plugin would be extracted by decompiling, and OAuth/relay needs hosted infrastructure — hence "pre-fill + one click". Diagnostics come from the new `/memory-eternal/api/diagnostics` endpoint and are **auto-redacted** (home directory → `~`; `sk-` / `ghp_` / `github_pat_` / `api_key:` → `***`; truncated to 2400 chars), and the issue URL is truncated by **binary search** so it can never exceed the length limit (`URLSearchParams` inflates CJK by roughly 9x). Adds `lib/feedback.js` (pure functions) and `tests/feedback.test.mjs` (4 checks: redaction, diagnostic fields and length cap, pre-filled URL encoding/truncation, bilingual prompt); `npm test` now runs **103 checks** |
|
|
319
|
+
| **v0.9.11** | 2026-09-28 | **Fixed `watchdog --reap` killing itself**: when you run `node lib/watchdog.js --reap` directly, the caller's own command line also contains `watchdog.js` on the same port and is not in the lock — so the reaper SIGTERMed **itself**, showing up as "no output at all + exit code 1" (going through `dsh-memory watchdog --reap` was unaffected because its command line lacks `watchdog.js`, which is why it only showed up on the direct path). The protected set now always includes `keepPid`, the current pid and the parent pid, and any other process whose command line carries `--reap` is skipped; output now uses `fs.writeSync(2, …)` so `process.exit` cannot truncate it. Regression test added for "self and parent must never be killed" (using a real idle child process as the target instead of a fake pid). `npm test` runs **98 checks** |
|
|
320
|
+
| **v0.9.10** | 2026-09-28 | **Multi-vault + watchdog wrap-up, plus graph frame-time work.** ① **Multi-vault (#10)**: `vaultProfiles` / `activeVault` finally have a settings-page form (add/remove vaults, set directories, pick the active one, and see the effective directory / source / workspace); vault resolution moved into `lib/vault-resolve.js` and is **shared by the host and CLI / MCP / hooks / standalone web / sweep**, with new `vaultProfiles[].match.workspace` **auto-selection by project directory** (longest prefix wins, opt-in, still single-vault by default); `memory_recall` gained a `scope` argument (vault name / path prefix / `all` for cross-vault aggregation) and cross-vault results are labelled with their source vault. ② **Watchdog (#11)**: the lock is now **per-port** (several ports/vaults no longer overwrite each other) and `dsh-memory watchdog --reap` collects orphans left by earlier versions (only same-port processes that are not in the lock; the live registered instance and user-started watchdogs are left alone). ③ **Graph frame time**: edges are bucketed by colour + alpha + width and stroked with a single **Path2D** per bucket (2.7k edges: 2.7k draw calls → a handful), and node radial gradients are **cached per colour\|radius and reused via translate** (593/frame → essentially none after the first frame). ④ New `tests/vault-resolve.test.mjs` (7 checks), watchdog tests grown to 7; `npm test` now runs **98 checks** |
|
|
321
|
+
| **v0.9.9** | 2026-09-28 | **Fixed the sidebar "Memory" entry being pushed out of view (issue #2)**: the slot host comes in two shapes — the shell's own horizontal row (`.footerActions`) and a `div[data-slot="sidebar.footer.action"]` that other plugins (`dsh-diff-approval`, `dsh-footer-order`, …) turn into `flex-direction: column`. The old CSS applied `flex-wrap: wrap` plus `.me-footer { flex: 1 1 100% }` to both: inside a column container `wrap` means "new column" and `basis: 100%` means **100% height**, so the button was pushed into an overflow column and clipped to a sliver. `flex-wrap` is now scoped to the horizontal `.footerActions` only and `.me-footer` uses the direction-agnostic `flex: 0 0 auto`, guarded by a new SSR assertion. Also: bilingual READMEs gained a "Community & Support" section (group QR + WeChat pay/reward codes), plus `SPONSOR.md` and `.github/FUNDING.yml` |
|
|
322
|
+
| **v0.9.8** | 2026-09-28 | **Backlog burn-down release.** ① **Capture reliability** (issues #3 / #4): distillation no longer hardcodes `providers[0]` — new `captureProvider` / `captureModel` config plus ordered fallback across providers; adapter errors carried by the stream's terminal `finish` block (missing credential, rate limit, …) are now **visible failures** (code/message in the capture log, red health state, raw-card fallback annotated with the cause) instead of a vague "distillation produced nothing"; the stall detector moved from cumulative-counter deltas to a **sliding window** (alerts only when turns keep starting with zero finishes inside 20 min), fixing both false alarms and misses. ② **Independent-process vault consistency** (dsh-memory-eternal#5): CLI / MCP / hooks / standalone web / sweep now share the host's resolution order (`MEMORY_VAULT_DIR` → `activeVault` → `vaultDir` → default), so switching vaults no longer splits your memory in two. ③ **Watchdog singleton lock** (dsh-memory-eternal#6): a new process exits when a live watchdog already owns the port, and stale pid records are cleaned, ending the orphan pile-up on every restart. ④ **Graph performance**: tag edges became "Top-K by shared tags" (measured **24,193 → 2,763** edges at 593 cards), similarity switched to a **rare-bigram inverted index** (cold **948 → ~520ms**, warm 2-4ms), payload **3,531KB → 579KB**, and the client dim pass now uses an **adjacency set** (**52ms → <1ms** per frame). ⑤ Five new test files (routing/finish, stall window, vault resolution, watchdog lock, graph perf baseline); `npm test` now covers **85 checks** |
|
|
323
|
+
| **v0.9.7** | 2026-09-28 | **Cards open fully expanded (and can be collapsed) + new body typography**: the reader no longer folds to 300px by default — it **opens showing the whole card**, with a one-click collapse for long ones (and an "Expand ⌄" hint when folded). Frontmatter is lifted out of the body into **colored chips** (kind / audit status / tags / dates / source; kind reuses the graph palette) instead of leaking raw YAML. Body rendering is rewritten (`src/client/markdown.js`, shared by the host and the standalone web page): headings get an **emoji + color group by meaning** (conclusion ✅green / risk ⚠️amber / root cause 🔍blue / plan 🛠️purple / example 💡pink), consecutive `- ` lines become a real `<ul>`, `1.` becomes an `<ol>` with numbered circles, `- [x]` becomes a checkbox, `>` becomes an emoji callout, `---` becomes a divider, short `key: value` lines get an aligned style, and `**bold**` gets a highlighter underline; fenced code is protected so `#` / `-` inside it are no longer re-typeset. **Adds 7 typography unit tests** (XSS escaping, link-protocol allowlist, prose colons must not be misread as key/value). Also carries the PR #8 port: Electron-host subprocess node resolution (`lib/node-bin.js`, fixing "standalone web server never starts → sidebar popup white screen") and API routes registered after `webServer` is ready (fixing "settings page stuck loading") |
|
|
324
|
+
| **v0.9.6** | 2026-09-28 | **Fixed the full-screen overlay covering the desktop shell's window controls (clicking Close quit the whole shell)**: the desktop shell draws minimize / maximize / close at the top of the page and, per the DSH convention, marks `<html>` with `data-windows-titlebar` and publishes `--dsh-windows-titlebar-height` (both confirmed present inside the official desktop build's `app.asar`); the memory overlay used `inset:0` plus an inline `100vh`, covering that whole strip, and our own top-right "×" landed exactly on the shell's window Close — one click quit the entire desktop shell. The full-screen state now uses the `.me-modal-full` class (no inline `100vh`, which CSS cannot override), and under `[data-windows-titlebar]` the `.me-overlay-top` / `.me-overlay` / `.me-modal-full` surfaces are pushed down by `--dsh-windows-titlebar-height` with height `calc(100vh - that)`. Browsers without the attribute get a 0px offset, so behaviour is unchanged there. The export-graph full-screen preview also moved from `100vh` to `100%` so it cannot overflow the shortened overlay. Adds 1 render regression asserting all three avoidance rules ship in the bundle |
|
|
325
|
+
| **v0.9.5** | 2026-09-28 | **Fixed the plugin failing to mount under the official desktop build (schemastery 3.18.4)**: the desktop profile resolves **schemastery 3.18.4**, which turns every `volatile` Config field into a cosmokit **live reference** (`{ get(): snapshot }` branded with `Symbol.for('cosmokit.volatile.write')`), while 0.9.4 treated those fields as plain values — `cfg.vaultDir.trim()` threw `TypeError: cfg.vaultDir.trim is not a function` and the plugin died inside `apply` (the exact desktop error). The plugin now **deep-unwraps** references per the cosmokit protocol (snapshot each reference, recurse through arrays/objects), so `settings.get()` only ever exposes plain values; each read unwraps afresh, so in-place volatile hot updates stay immediately visible, and `JSON.stringify` no longer writes `{}` into the shared config file. Adds 2 regressions (the real 3.18.4 reference shape + nested arrays/objects) and verifies `apply` under the **desktop build's real module-resolution layout** (schemastery 3.18.4 + real cosmokit) |
|
|
326
|
+
| **v0.9.4** | 2026-09-28 | **DSH v0.1.7-rc.2 support (fixes "the plugin goes dark after the upgrade")**: (1) **The settings service was replaced** — in 0.1.7 `ctx.settings` is a forms-only API (`describe/update/replace/mutate/configure`) with no `register()`; the old `ctx.settings.register(...)` call throws a `TypeError`, so the plugin never mounts (memory page gone, auto-capture dead). A cross-version shim keeps `register` for older hosts while new hosts read the **live config reference** the loader passes in, subscribe to `loader/volatile-update` for hot updates, and write back through `settings.update(entry id, patch, revision)` (revision conflicts map to HTTP 409); it also registers `configure({ auto:false })` so the host does not generate a duplicate form page. (2) **Volatile field marking moved after construction**: no more chained `.volatile()` — that method only exists in schemastery ≥3.18.4, while the plugin actually resolves **3.18.1** at the profile level, so the chain threw `volatile is not a function` at import time and killed the plugin. (3) **Dead client references removed**: `inject` no longer lists `settingsScope`, which disappeared together with `@deepseek-ai/dsh-client-runtime` (0.1.7 has no such service, so the client plugin waited forever and never activated — taking the memory page and the sidebar button with it); `dsh.client.inject` dropped its non-existent package names. (4) New **`tests/settings-compat.test.mjs`** (8 cases: 0.1.7-shaped mount / live-reference reads / volatile hot update / write-back and revision conflict / legacy `register` path / field volatile markers) wired into `npm test`. Verified by booting a **real DSH v0.1.7-rc.2**: the host plugin mounts (config written to `memory-eternal-config.json`) and the client bundle composes into the boot graph (`plugins/??memory-eternal/client.js`) |
|
|
327
|
+
| **v0.9.3** | 2026-09-12 | **Fixed the blank memory page ("no UI")**: v0.9.1 placed the infinite-scroll `useEffect` **before** the `loadCards` definition — React evaluates the dependency array during render, hitting a TDZ error (`Cannot access 'loadCards' before initialization`) that **crashed the whole memory page on first render**. It now comes after the definition. Added a **render smoke test** (`tests/ssr.test.mjs`: renders the built bundle through all four entry points — cards / settings / usage / graph — wired into `npm test`) so "green build, blank page" bugs cannot ship again |
|
|
328
|
+
| **v0.9.2** | 2026-09-12 | **Log visibility + false-alarm fix**: the capture log is now **persisted to disk** (`~/.dsh/memory-eternal-capture.jsonl`, last 500 entries) — the standalone web page no longer says "log only available inside the DSH host" but shows the records, and history survives a host restart (read back on boot); fixed **stall-detector false alarms flooding the panel** (mismatched turn counters are normal: sub-agent turns and cancelled turns emit no `turn-stopping`; it now requires "turns running **and** no capture activity for 15 minutes" to alert once, and the alarm clears as soon as activity resumes — no more one `fail` line every 10 minutes permanently turning health red); when distillation returns nothing / unparseable JSON the content is **saved as a raw card instead of being dropped** |
|
|
329
|
+
| **v0.9.1** | 2026-09-12 | **Performance & UX batch**: memory page loads lazily per view (opening Settings no longer drags in 250KB of cards + 890KB of graph; first paint needs ~0.5KB); graph generation **3232ms → 43ms** (bigram sets computed once + lossless mathematical-bound pruning + tag inverted index) plus a server-side cache with **fingerprint invalidation** (write/audit/delete rebuilds immediately, no stale reads); site-wide **brotli q5** (graph 877KB → **54KB**, 34% smaller than gzip; cards 246KB → 83KB → 20KB with br) and large responses compressed with both br and gzip keeping the smaller, so no response is ever worse than gzip; `/cards` gained **real pagination** (offset/limit/total + server-side title sort, globally ordered across pages) loading 100 cards first and fetching more on scroll; the "Agent cards" panel in Usage/Today filters by agent server-side (30 rows); **audit red line**: the plugin injects "never call approve/reject on the user's behalf" into the agent context; the watchdog now **reaps redundant instances on fallback ports** (a duplicate web process holding 76MB was reaped in testing) |
|
|
330
|
+
| **v0.9.0** | 2026-09-12 | **Fixed silent auto-capture death (6 days without a single card)**: after a DSH upgrade the session event API moved from `events` to `ownEvents()/snapshotEvents()`; the listener read nothing, returned silently and left no trace — now it tries `ownEvents()` → `snapshotEvents()` → `events` and logs a per-session attach entry. Daily quota now counts **real writes only** (previously every "not worth saving" verdict burned quota, exhausting the 24h budget after 40 attempts); `captureCooldownMs` actually applies; a single capture input is tail-capped at 20k chars. New **capture log** panel and **active failure alerts** (red strip + agent-context injection + turn-stopping stall sweep). Removed the automatic "Daily review" digest (timer / `/todayBrief` route / UI button). |
|
|
331
|
+
| **v0.8.0** | 2026-09-06 | **Full UI i18n**: follows the DSH system language live (zh/en) across cards, graph, audit center, config panel and new-card templates; SQLite EBUSY fix for the Windows test suite |
|
|
332
|
+
| **v0.3.1** | 2026-09-03 | Knowledge graph loads on demand (fetch on open, unregister on close) |
|
|
333
|
+
| **v0.3.0** | 2026-09-03 | **SQLite storage layer** (`node:sqlite`, zero deps) + DB-level audit guard `enforceAudit()` + `audit_log` table + automatic `.md` migration |
|
|
334
|
+
| v0.2.0 | 2026-09-03 | Recall with body text (`search()` returns the `excerpt` field) |
|
|
335
|
+
| v0.1.2 | 2026-09-03 | Audit guard hardening (`writeCard` defaults to `pending`, `mergeCards` goes through audit) |
|
|
336
|
+
| v0.1.1 | 2026-09-03 | Recall body fix (`excerpt` field + body logic) |
|
|
337
|
+
| v0.1.0 | 2026-08-31 | First release: auto capture + auto recall + graphical knowledge base + knowledge graph + audit center + recycle bin |
|
|
338
|
+
|
|
339
|
+
---
|
|
340
|
+
|
|
341
|
+
## 💬 Community & Support
|
|
342
|
+
|
|
343
|
+
**Questions, feature requests, or just want to talk about DSH plugin development — join the group chat:**
|
|
344
|
+
|
|
345
|
+
<img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/support/group-qr.jpg" width="260" alt="DeepSeek Harness community group QR code" />
|
|
346
|
+
|
|
347
|
+
**If this plugin saved you some time, you can buy the author a coffee (either code works):**
|
|
348
|
+
|
|
349
|
+
| WeChat Pay | WeChat Reward |
|
|
350
|
+
|---|---|
|
|
351
|
+
| <img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/support/wechat-pay.jpg" width="230" alt="WeChat Pay QR code" /> | <img src="https://raw.githubusercontent.com/EternalNight996/memory-eternal/main/assets/support/wechat-reward.jpg" width="230" alt="WeChat reward QR code" /> |
|
|
352
|
+
|
|
353
|
+
> Donations are entirely optional and change nothing about the plugin; it stays open source and free (MIT).
|
|
354
|
+
> Picking the first custom entry in the repo's **Sponsor** dropdown lands on [SPONSOR.md](SPONSOR.md), which shows the same codes.
|
|
355
|
+
|
|
356
|
+
---
|
|
357
|
+
|
|
358
|
+
## 📄 License
|
|
359
|
+
|
|
360
|
+
MIT
|
|
361
|
+
|
|
362
|
+
---
|
|
363
|
+
|
|
364
|
+
> **Make your AI truly remember: dialogue auto-captured, knowledge at your fingertips.** ⭐ Star it if you like, Let's make AI not forget.
|
|
365
|
+
>
|
|
366
|
+
> 中文 README: [README.md](README.md)
|