companion-memory
Manifest validLocal long-term memory core for DeepSeek Harness with plain-text notes, a bounded index, five tools, optional host-model consolidation and auditable evidence. It appends every user and assistant messa
dsh-companion-memory-core (v0)
Local, host-independent long-term memory core for DeepSeek Harness. Plain-text notes, a bounded index, auditable evidence. No runtime dependencies, no external services, no native modules.
Design notes live in the project plan and are not shipped in the npm package.
Current status
The v0 implementation covers the data contract, three-source store, bounded
index, keyword recall, layered disclosure, five tools, and host llm/stream
review. lib/ is generated by npm run build and shipped in the package.
Review borrows the host's ctx.llm.stream() through LlmReviewer; it stays
disabled by default via maintenanceMode: off. The idle-review chain (§7-3) is
covered end to end by a host-shaped stream test, so no model quota is spent in CI.
Tools and session collection are registered on the plugin's own host context:
the desktop build loads client entries as classic scripts, so an ESM client
bundle aborts web boot. v0 therefore ships no client entry; note browsing stays
on the tool surface. A custom pane is deferred: host remote namespaces are
Typert-generated, so a third-party plugin cannot register a new RPC group at
runtime.
When consolidation runs, the model route is borrowed from the current session
request header. Set reviewProvider / reviewModel in the profile config to
pin a specific one; leaving both empty follows whatever the conversation uses.
Every written note carries an evidence quote that is verified verbatim
against the input actually shown to the model — fabricated quotes are dropped
before they reach disk.
The host exposes no learning / contentMode / toolVerified admission
metadata, so unverified tool/result output is deliberately never archived.
User and assistant messages are the only long-term sources in v0.
The npm package name is dsh-companion-memory-core, distinct from the GitHub
repository name.
Layout
src/core/ host-independent: paths, schema, store, indexer, recall,
disclosure, context, review, writer, llm-adapter, llm-reviewer
src/host/dsh/ the only layer allowed to touch the harness
src/client/ reserved for v1; excluded from the build and the package
lib/ build output, the only code shipped in the npm package
Build and install
npm install --no-package-lock --legacy-peer-deps
npm run build # emits lib/**/*.js + .d.ts
npm test
npm pack # sanity-check the tarball contents
dsh plugin --profile test add .
Local verification should use a dedicated test profile, never the daily one.
Data location
Default ~/.companion/, overridable with config.memoryRoot or the
COMPANION_MEMORY_ROOT environment variable. Everything is plain text and
stays on the machine:
MEMORY.md bounded index (200 lines / 25 KB)
meta.json schema version, writer epoch, review watermark
notes/*.md one fact per file, with evidence and sourceRefs
cold/*.jsonl append-only raw conversation lines
journal/ reserved for v1
persona.md reserved for v1
profile.md reserved for v1
state.json reserved for v1
archive/ soft-archived notes
index/ rebuildable keyword index
Uninstalling the plugin never deletes this directory. memory_forget archives a
note and removes its index entry; it does not touch the host's own chat history.
Privacy and capability boundaries
- Memory is unencrypted plain text; any local process can read it. Never store credential values, only pointers to where they live.
- The core never reads credentials and never opens network connections.
- Review requests borrow the host's model through
LlmAdapter; the package ships no API key and no fallback provider. maintenanceMode: offmust produce zero model calls.
Before publishing
- Confirm peer ranges against the actual dsh release in use (verified against
desktop
0.2.2-rc.1/cordis 4.1.0). - Run
npm run build, verifylib/andicon.pngare in the tarball, thennpm publish. - Add the
dsh-plugintopic after the repository is at least one day old, then submit one catalog YAML entrydata/plugins/1326007879-sys__companion-memory.yml. Note the 24-hour npm release-age window. - Keep descriptions factual: stable memory, local notes, bounded index. Do not claim consciousness, emotions, or model training.
Out of scope for v0
Persona/state injection, moods, proactive messages, journaling, vectors, graph links, star map, cross-host adapters, encryption, hash-chain audit, standalone service, model training.
Comments
Loading…
Similar plugins
On-demand memory for DeepSeek Harness: session logs are distilled into layered markdown (a summary, an index and per-topic files), and a mem_query tool returns only the matched entries rather than the
★ 0
dsh plugin --profile web add dsh-memory-liteby adithyanraj03
Persistent memory for dsh in the style of Hermes Agent: a memory tool keeping a user profile and the model's own notes, delivered to every chat as a logged context message, plus session_search over earlier chats behind an approval prompt.
★ 0
NOASSERTION
JavaScript
Oct 26, 2026
dsh plugin --profile web add dsh-memory-recallby Frog755
Three-layer local memory for DeepSeek Harness: L1 snapshot memory (MEMORY.md/USER.md) read on demand through the memory_* tools + L2 searchable knowledge base (facts + SQLite FTS5, Chinese search via
★ 3
MIT
JavaScript
Sep 10, 2026
dsh plugin --profile web add @frog755/dsh-hybrid-memoryLayered long-term memory for DeepSeek Harness with automatic model distillation, source-linked encrypted session logs, and guarded compaction.
★ 0
dsh plugin --profile web add @marculiu/dsh-hermes-memoryby Fishsb
DSH 长期记忆插件:记忆库 + 会话蒸馏自动沉淀 + 设置面板,越用越懂你。守藏(Shoucang)单插件,panel + scheduler + 内嵌记忆技能。
★ 5
Apache-2.0
JavaScript
Sep 27, 2026
dsh plugin --profile web add dsh-shoucang-memoryby 2132774831
这是我为 DSH (DeepSeek Harness) 制作的一款插件,可以进行跨对话记忆支持手动导入
★ 3
↓ 101/wk
MIT
JavaScript
Nov 9, 2026
dsh plugin --profile web add dsh-local-memory