@openviking/dsh-memory-plugin 0.5.5 → 0.5.7

package/README.md

@@ -34,7 +34,7 @@ It also needs `node examples/memory-plugin-shared/sync.mjs` run first: the
 
 ## Requirements
 
-- `@deepseek-ai/dsh` `0.1.0-rc.6`, `0.1.5-rc.1`, or `0.1.5-rc.2`; stable `0.1.x` releases are also admitted by the peer range
+- `@deepseek-ai/dsh` `0.1.0-rc.6`, `0.1.5-rc.1`, `0.1.5-rc.2`, or `0.1.7-rc.2`; stable `0.1.x` releases are also admitted by the peer range
 - Node.js `^22.19.0` or `>=24`
 - A reachable OpenViking server
 
@@ -48,9 +48,10 @@ individual DSH core packages to the profile. DSH initializes profiles with
 available through its module fallback at boot. A missing-peer warning during
 `dsh plugin add` alone does not prove startup is broken.
 
-The peer range is `>=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1`. The second clause
-explicitly admits the `0.1.5` release candidates: semver does not include them
-in the first clause merely because they compare above `0.1.0-rc.6`. Other
+The peer range is `>=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1 || ^0.1.7-rc.2`. Each
+pre-release clause admits one series explicitly: semver does not include a
+release candidate in the first clause merely because it compares above
+`0.1.0-rc.6`, so every verified pre-release series is listed on its own. Other
 pre-release series need separate verification. Local devDependencies and
 `overrides` stay pinned to rc.6 to exercise the minimum supported contract.
 
@@ -137,7 +138,7 @@ effect for the tools when DSH restarts the bundle, as it does for the runtime.
 
 Two consequences follow from the proxy being one process per profile:
 
-- **The actor peer is process-level.** Recall, capture, and commit still resolve a peer per session from that session's workspace repository, but tool calls carry the peer resolved at boot. Set `OPENVIKING_PEER_ID` when one process serves several repositories and you need tool calls attributed exactly.
+- **MCP actor scope is process-level.** With the default `recallPeerScope: all`, MCP tool calls omit the actor peer header. With `actor`, they use the peer resolved at boot. Automatic recall, capture, and commit resolve their peer from each session's workspace.
 - **`remember` is not session-scoped.** The server's MCP `remember` stores into
   its own short-lived session rather than the live `dsh-<session-id>` stream —
   the same behavior the Claude Code, Codex, and Cursor integrations have.
@@ -189,7 +190,7 @@ The patch can also carry plugin config:
           name: '@openviking/dsh-memory-plugin'
           config:
             endpoint: http://127.0.0.1:1933
-            recallTokenBudget: 2000
+            recallMaxTokens: 2000
             scoreThreshold: 0.35
             captureToolResults: false
             skipSubagentSessions: true
@@ -197,6 +198,30 @@ The patch can also carry plugin config:
             mcpToolCallTimeoutMs: 60000
 ```
 
+Recall normally uses `POST /api/v1/search/search` with `mode: "context"`.
+`recallMaxTokens` (`OPENVIKING_RECALL_MAX_TOKENS`) sets this request's
+`max_tokens` budget for server-assembled context. When it is unset, the plugin
+omits `max_tokens` and uses the server's default budget.
+
+`recallLimit` (`OPENVIKING_RECALL_LIMIT`) scales the category quotas for context
+recall; it is not a strict cap on the final number of entries. When explicitly
+set, it allocates at least one slot to each of the six categories: events,
+entities, preferences, experiences, resources, and skills. For example,
+`recallLimit: 4` sends six one-slot quotas, so the result can contain more than
+four entries. Lowering it does not expand the set of categories searched.
+Actual results still depend on matching content, score filtering, deduplication,
+and the token budget. When unset, the server's coding preset supplies the quotas.
+
+The older size settings apply to fallback recall, not the primary context request:
+
+- `recallTokenBudget` (`OPENVIKING_RECALL_TOKEN_BUDGET`) controls the estimated
+  token budget of the locally rendered block when both server-side context and
+  the legacy `/api/v1/search/recall` endpoint are unavailable and recall falls
+  back to raw search results.
+- `recallMaxContentChars` (`OPENVIKING_RECALL_MAX_CONTENT_CHARS`) limits each
+  item's content in that local fallback. It also sets the legacy `/recall`
+  request's `max_chars` to `max(1000, recallMaxContentChars * recallLimit)`.
+
 ## Behavior
 
 - `agent/session-start` injects the OpenViking profile, the available-memory index, and the `<available-skills>` catalog through `agent.inject()`.
@@ -210,7 +235,18 @@ The patch can also carry plugin config:
 - `tools/pre-execute` denies a DSH filesystem tool (`read`, `glob`, `grep`, `edit`, `write`, `str_replace_editor`) whose path argument is a `viking://` URI, pointing the model at the bridged `mcp__openviking__*` tools instead. A `write` or `edit` under a skill directory (`viking://~/skills/...`, `viking://user/<id>/skills/...`, `viking://agent/skills/...`) points at `mcp__openviking__add_skill` instead, which creates or replaces a whole skill from its `SKILL.md` text. A `grep` whose pattern is `viking://` text still runs.
 - `tools/post-execute` lets a `bash` command that carries a `viking://` URI run unchanged and attaches a notice for the model: use the bridged tools if it meant OpenViking content, or ignore the notice when the URI is intentional data such as an `ov` argument or an HTTP payload.
 
-Each DSH session maps to `dsh-<session-id>` in OpenViking. Workspace-derived actor peers are resolved per session and sent on every session-specific request: the peer is the git identity of the session's workspace — the normalized `origin` URL (`git@github.com:volcengine/OpenViking.git` becomes `github.com-volcengine-openviking`), else the repository root path, that fallback keeping the older rule where every non-letter-or-digit character becomes `-`. Outside a git repository no peer is sent at all, and what is remembered there goes to the user-level space `viking://user/<you>/memories`. One repository therefore keeps one peer across subdirectories, worktrees, clones and machines, while a fork's different origin keeps it separate. DSH does not read workspace `.openviking/config.json` files, so a `peer.id` written there has no effect; pin a peer with `OPENVIKING_PEER_ID` instead. Memories written under the older path-derived peer stay reachable: the default `recallPeerScope: all` sweeps every peer under the user.
+Each DSH session maps to `dsh-<session-id>` in OpenViking. Workspace-derived actor peers are resolved per session and sent on every session-specific request: the peer is the git identity of the session's workspace — the normalized `origin` URL (`git@github.com:volcengine/OpenViking.git` becomes `github.com-volcengine-openviking`), else the repository root path, that fallback keeping the older rule where every non-letter-or-digit character becomes `-`. With the default peer settings, no peer is sent outside a git repository, and what is remembered there goes to the user-level space `viking://user/<you>/memories`. One repository therefore keeps one peer across subdirectories, worktrees, clones and machines, while a fork's different origin keeps it separate. Memories written under the older path-derived peer stay reachable: the default `recallPeerScope: all` sweeps every peer under the user.
+
+Workspace peer settings are loaded from `session.header.cwd` when the session first uses memory. A workspace can set `peer.id` to name its project explicitly, or `peer.source` to choose a preset or template chain. For example, `<root>/.openviking/config.json` can contain:
+
+```json
+{
+  "version": 1,
+  "peer": { "id": "my-project" }
+}
+```
+
+The shared loader also applies `config.local.json` and machine registry overrides. Explicit host `peerId`, environment overrides and pinned `ovcli.conf` credentials retain their existing precedence. The resolved peer stays fixed for the session's runtime state; new sessions load the current workspace settings. A session without a cwd falls back to the process's working directory.
 
 ## Tools
 

package/config.mjs

@@ -1,7 +1,7 @@
 import { buildPluginConfig } from "./shared/plugin-config.mjs";
 import { loadCredentialFiles } from "./shared/credentials.mjs";
 
-export const PLUGIN_VERSION = "0.5.5";
+export const PLUGIN_VERSION = "0.5.7";
 
 /**
  * Namespace for the bridged OpenViking MCP tools. DSH publishes every MCP tool

package/icon.svg

@@ -0,0 +1,17 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" role="img" aria-label="OpenViking" focusable="false">
+  <title>OpenViking</title>
+  <style>
+    /* Monochrome mark. The plugin card renders this file as an image document,
+       which cannot read the page palette, so the two inks are declared here and
+       the scheme flip comes from the only signal an image document gets:
+       prefers-color-scheme. The base fill attribute keeps the black ink in
+       renderers that lack that query, and the class is named after the product
+       to stay unique if this file is ever inlined. */
+    @media (prefers-color-scheme: dark) {
+      .openviking-mark { fill: #ffffff; }
+    }
+  </style>
+  <path class="openviking-mark" fill="#000000" d="M21.9136 11.2875C21.8311 15.6708 18.953 19.691 14.5292 21.0217C10.1055 22.3524 5.48691 20.587 3 16.9758L6.35328 15.9668C8.52232 18.6563 12.1802 19.9123 15.6932 18.8558C19.2062 17.7993 21.5646 14.7335 21.8903 11.2938L21.9136 11.2867V11.2875Z"/>
+  <path class="openviking-mark" fill="#000000" d="M11.9754 2.26476C14.2745 3.4155 19.0247 7.27598 19.1416 14.5217L9.68011 17.3709C10.3938 16.4998 11.0303 15.5158 11.5546 14.4446L15.4019 13.2751C16.6438 8.11275 14.2504 4.18838 11.9941 2.3115C11.9878 2.29592 11.9816 2.28034 11.9754 2.26398V2.26476ZM11.9941 2.31228C13.7548 6.71269 13.2274 11.0251 11.5546 14.4446L8.98047 15.2268C12.4085 10.0457 12.4865 5.64375 11.9699 2.29125C11.9785 2.29826 11.9863 2.30527 11.9941 2.3115V2.31228Z"/>
+  <path class="openviking-mark" fill="#000000" d="M11.9909 2.31144C13.7517 6.71185 13.2243 11.0242 11.5515 14.4437L8.97656 15.2259C12.4046 10.0449 12.4826 5.64291 11.966 2.29041C11.9746 2.29742 11.9824 2.30443 11.9902 2.31066L11.9909 2.31144Z"/>
+</svg>

package/index.mjs

@@ -12,7 +12,11 @@ export const inject = ["agents", "sessions", "tools"];
 export function apply(ctx, input = {}) {
   const config = resolveConfig(input);
   const client = new OpenVikingClient(config);
-  const runtime = new OpenVikingRuntime(client, config, ctx.logger);
+  const runtime = new OpenVikingRuntime(client, config, ctx.logger, cwd => (
+    // Rebuild from the host input, not the config already merged for boot's cwd.
+    // The shared loader preserves host/env precedence over workspace peers.
+    resolveConfig(input, process.env, cwd).effectivePeer
+  ));
   const skipMemory = session => (
     config.skipSubagentSessions && session?.header?.origin === "subagent"
   );

package/locale/en.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "OpenViking Memory",
+    "description": "Long-term semantic memory for DeepSeek Harness: auto-recall before each step, session capture and commit, viking:// URI protection, and the OpenViking MCP tools and skills."
+  }
+}

package/locale/zh.json

@@ -0,0 +1,6 @@
+{
+  "meta": {
+    "title": "OpenViking 记忆",
+    "description": "为 DeepSeek Harness 提供长期语义记忆：每步自动召回、会话采集与提交、viking:// URI 保护，以及 OpenViking MCP 工具与技能。"
+  }
+}

package/package.json

@@ -1,13 +1,17 @@
 {
   "name": "@openviking/dsh-memory-plugin",
-  "version": "0.5.5",
+  "version": "0.5.7",
   "description": "OpenViking memory and context bundle for DeepSeek Harness",
+  "icon": "./icon.svg",
   "type": "module",
   "main": "index.mjs",
   "exports": {
-    ".": "./index.mjs"
+    ".": "./index.mjs",
+    "./package.json": "./package.json",
+    "./locale/*.json": "./locale/*.json"
   },
   "files": [
+    "icon.svg",
     "index.mjs",
     "client.mjs",
     "config.mjs",
@@ -21,6 +25,7 @@
     "servers/",
     "shared/",
     "skills/",
+    "locale/",
     "cordis.patch.yml",
     "README.md"
   ],
@@ -37,9 +42,9 @@
     "prepublishOnly": "npm run prepack && npm run check && npm test"
   },
   "peerDependencies": {
-    "@deepseek-ai/dsh-llm": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1",
-    "@deepseek-ai/dsh-mcp-client": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1",
-    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1"
+    "@deepseek-ai/dsh-llm": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1 || ^0.1.7-rc.2",
+    "@deepseek-ai/dsh-mcp-client": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1 || ^0.1.7-rc.2",
+    "@deepseek-ai/dsh-skill-filesystem": ">=0.1.0-rc.6 <0.2.0 || ^0.1.5-rc.1 || ^0.1.7-rc.2"
   },
   "devDependencies": {
     "@deepseek-ai/dsh-llm": "0.1.0-rc.6",

package/runtime.mjs

@@ -18,10 +18,11 @@ import {
 } from "./capture.mjs";
 
 export class OpenVikingRuntime {
-  constructor(client, config, logger = console) {
+  constructor(client, config, logger = console, resolveSessionPeer = null) {
     this.client = client;
     this.config = config;
     this.logger = logger;
+    this.resolveSessionPeer = resolveSessionPeer;
     this.states = new Map();
     this.drainTimer = null;
     this.drainRunning = false;
@@ -33,7 +34,7 @@ export class OpenVikingRuntime {
     let state = this.states.get(session.id);
     if (state) return state;
     const cwd = session.header?.cwd || process.cwd();
-    const peer = resolveEffectivePeerId({
+    const peer = this.resolveSessionPeer?.(cwd) ?? resolveEffectivePeerId({
       cfg: {
         peerId: this.config.explicitPeerId,
         peerSource: this.config.peerSource,