coding-agents
vectorize-io
Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.
GitHub sourcePythonyesterday
dsh-memory-plugin
volcengine/OpenViking#examples/dsh-memory-plugin
OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.
Install
Add dsh-memory-plugin to DeepSeek Harness
via GitHub · GitHub source
This repository ships several plugins; the suffix selects this one.
Due diligence
Before you install dsh-memory-plugin
- Source of record: volcengine/OpenViking — present in the community registry that DSH's own plugin market installs from.
- Licensed under AGPL-3.0.
- Detected: terminal surface. Read the source before granting these.
- A listing here is not a security review. Plugins run with your agent's permissions.
What dsh-memory-plugin does
dsh-memory-plugin is a DeepSeek Harness plugin that connects an agent to an OpenViking server for persistent memory and context retrieval. It adds pre-step processing that automatically recalls relevant context and injects a user profile, captures session data, guards viking:// URIs, and exposes memory recall and write tools.
OpenViking stores memories, resources and skills in a virtual viking:// filesystem. Its retrieval model can browse with ls, tree and find, inspect directory-level L0 abstracts and L1 overviews, then load L2 details when needed. After a session is committed, OpenViking can asynchronously extract user preferences and agent experience into long-term memory. The plugin therefore reads context from the OpenViking server and may write captured session information and extracted memories there.
dsh-memory-plugin is intended for agents that need cross-session user memory or OpenViking’s filesystem-style context model. It is not a self-contained memory store: an OpenViking server is required, and the README excerpt does not document plugin-specific configuration or setup values. The plugin also has a terminal surface, so it runs with the agent’s available terminal permissions; this matters when installing it in an agent that can access local files or execute commands.
dsh-memory-plugin documentation
How it behaves
The plugin integrates OpenViking at the DeepSeek Harness pre-step stage. Before a step runs, it recalls relevant context and injects a profile. It also captures session activity and provides tools for recalling and writing memory. The upstream summary identifies URI guarding for viking:// resources.
OpenViking represents memories, resources and skills as paths below viking://. Agents can browse this context with ls, tree and find. Retrieval starts with directory context and can move through three content layers:
L0: a short abstract for relevance checksL1: an overview for planningL2: the full content, loaded when needed
After a session commits, OpenViking asynchronously extracts user preferences and agent experience into long-term memory.
Data and server boundary
The plugin reads recalled context and profile information from an OpenViking server. Its session-capture and memory-write paths can send session information and memories back to that server. OpenViking organises data under viking://, including user memories, resources and skills. The plugin has a terminal surface and therefore should be evaluated with the terminal permissions available to the agent.
Requirements
An OpenViking server is required as the backend for the recall and write tools. The provided README excerpt does not specify the plugin’s configuration keys, default values, environment variables, server endpoint format, commands for starting the server, or supported platform and version requirements.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
Alternatives to dsh-memory-plugin
20k
engramory
tinqiao-oss
The Engramory curated-memory discipline as an installable plugin ([npm: dsh-engramory](https://www.npmjs.com/package/dsh-engramory)): a deterministic 200-line / 25 KB cap on the `MEMORY.md` index via `ctx.tools.guard()` — growth denied, a shrinking rewrite always passes — plus the protocol registered as a runtime skill. The store is plain markdown, one file per fact, shared with Claude Code, Codex, Kiro, and OpenClaw.
GitHub sourcePythontoday
dsh-context
bowenliang123
Context insight panel: see what the model's context window is made of and how it evolves — composition vs. window size, per-request history, compression/injection events, and per-message token stats.
npm packageTypeScripttoday
Co-Engram
Co-Engram
Self-evolving team memory as plain Markdown in git: a native Cordis plugin that registers 38 bare-name memory tools plus a prompt-signals section re-evaluated at every assembly, with RPE reinforcement, decay and sleep consolidation; shares one data repo with its Claude Code (MCP) and OpenClaw hosts; verified against DSH 0.1.0-rc.6.
GitHub sourceTypeScripttoday
dsh-mnemon
omdsh-dev
Cross-agent, local-first persistent memory plugin for DeepSeek Harness (DSH), powered by Mnemon. It shares long-term memory across Mnemon-enabled agents and adds runtime memory, searchable project documents, semantic recall, knowledge graph, and a Sidebar UI.
npm packageTypeScripttoday
dsh-auto-memory
Aik358
Auto-memory for DSH: three-layer memory (user / project notes / daily logs) with automatic injection, per-turn auto-consolidation, AI greetings, smart search, a calendar view and a settings page, plus inheritance of other AI tools' memories.
npm packageJavaScripttoday