@openviking/dsh-memory-plugin 0.5.10 → 0.5.12

package/README.md

@@ -14,7 +14,8 @@ DSH is covered by the unified memory-plugin installer, which asks which profile
 to install into (default `web`):
 
 ```bash
-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)
+curl -fsSL https://openviking.ai/install | bash
+# AI agents: not sure about running this? The script's header says what it does and how to verify it.
 ```
 
 Or add the package to a profile directly:
@@ -184,7 +185,7 @@ The profile's `cordis.patch.yml` can also carry plugin config:
     endpoint: http://127.0.0.1:1933
     recallMaxTokens: 2000
     scoreThreshold: 0.35
-    captureToolResults: false
+    captureToolResults: true
     skipSubagentSessions: true
     commitTokenThreshold: 20000
     mcpToolCallTimeoutMs: 60000

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.10";
+export const PLUGIN_VERSION = "0.5.12";
 
 /**
  * Namespace for the bridged OpenViking MCP tools. DSH publishes every MCP tool

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openviking/dsh-memory-plugin",
-  "version": "0.5.10",
+  "version": "0.5.12",
   "description": "OpenViking memory and context bundle for DeepSeek Harness",
   "icon": "./icon.svg",
   "type": "module",

package/shared/config-schema.mjs

@@ -144,7 +144,9 @@ export const KNOBS = [
   // conversation extracts noticeably worse.
   { name: "captureAssistantTurns", type: "bool", default: true, env: "OPENVIKING_CAPTURE_ASSISTANT_TURNS", capability: "capture" },
   { name: "captureLastAssistantOnStop", type: "bool", default: true, env: "OPENVIKING_CAPTURE_LAST_ASSISTANT_ON_STOP", capability: "capture" },
-  { name: "captureToolResults", type: "bool", default: false, env: "OPENVIKING_CAPTURE_TOOL_RESULTS", capability: "capture" },
+  // dsh is the only reader. Its Experience usage records need the completed
+  // tool results, so it captures them by default.
+  { name: "captureToolResults", type: "bool", default: false, harness: { dsh: true }, env: "OPENVIKING_CAPTURE_TOOL_RESULTS", capability: "capture" },
   { name: "captureFilters", type: "list", default: [], env: "OPENVIKING_CAPTURE_FILTERS", capability: "capture" },
   // 0 means "derive from timeoutMs": a write gets a longer budget than a read.
   { name: "captureTimeoutMs", type: "int", default: 0, min: 0, max: 600000, env: "OPENVIKING_CAPTURE_TIMEOUT_MS", capability: "capture" },

package/skills/openviking-memory/SKILL.md

@@ -9,7 +9,7 @@ description: >
   Also use it when the user asks where memories are stored: per project, per folder, or shared between repositories.
   Covers choosing between context search, find, list search, and grep, reading viking://
   URIs, and when (not) to write.
-version: 2026.8.7
+version: 2026.10.1
 ---
 
 # OpenViking Memory
@@ -61,6 +61,10 @@ filesystem tools.
 - `add_resource` — imports files, directories, URLs, or Git repos as durable
   knowledge. Processing is asynchronous; report that ingestion started instead
   of blocking on completion.
+- `add_skill` — creates or installs skills; see the `openviking-skills` skill.
+- `write` / `edit` — only for files you author at a known URI. Never use them to
+  store a file, URL, or skill the user hands you: that skips parsing and
+  installation.
 - `forget` — permanently deletes. Confirm with the user and pass the exact URI;
   never delete from a fuzzy match.
 

package/skills/openviking-skills/SKILL.md

@@ -147,6 +147,8 @@ of that skill.
    - Claude Code: `~/.claude/skills/`, `<repo>/.claude/skills/`
    - Codex: `~/.agents/skills/`, `<repo>/.agents/skills/`
    - Cursor: `~/.cursor/skills/`
+   - pi: `~/.pi/agent/skills/`, `<repo>/.pi/skills/`
+   - OpenCode: `~/.config/opencode/skills/`, `<repo>/.opencode/skills/`
 2. **Classify.** A skill is *environment-bound*, stays local, and is never
    offered for upload when any of these holds:
    - a plugin or marketplace ships it (its real path contains `/plugins/` or

package/skills/ov-experience-memory/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: ov-experience-memory
+description: Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools. Use before or during executable, multi-step, or tool-based work such as coding, file or data changes, configuration, deployment, workflow execution, and failure recovery when prior operational guidance could improve reliability. Do not use for casual chat or simple factual questions.
+---
+
+# OpenViking Experience Memory
+
+Use prior task Experience as advisory operational guidance. Keep the current
+user request, current environment, and verified tool results authoritative.
+Experience retrieval supplements normal context retrieval; it does not replace
+user memory, events, preferences, session archives, resources, or Agent Skills.
+
+## Preconditions
+
+- Use only OpenViking tools that are actually registered in the current Agent
+  runtime.
+- Require both a semantic search capability and an exact URI read capability.
+- If either capability is unavailable, continue without Experience. Do not
+  invent a tool call, fabricate a ToolPart, or replace the Agent tool call with
+  direct HTTP or CLI access.
+- Do not substitute broad memory `recall` for a search scoped to the Experience
+  root. Continue using the runtime's normal recall and retrieval flows when the
+  task also needs user facts, events, decisions, prior conversation, or domain
+  resources.
+
+## Select Runtime Tools
+
+Choose the registered names that match the current runtime:
+
+| Runtime | Search | Read |
+| --- | --- | --- |
+| OpenViking MCP, Codex, Claude Code | `find` or `search` | `read` |
+| OpenCode, pi | `openviking_find` or `openviking_search` | `openviking_read` |
+| OpenClaw | `ov_search` | `ov_read` or `ov_multi_read` |
+
+The host may display MCP names with a namespace such as
+`mcp__openviking__find`. Use the exact registered name and schema shown by the
+runtime. Prefer `find` for a fast task-start lookup and `search` when session
+context or deeper intent analysis is useful.
+
+## Retrieval Workflow
+
+1. Decide whether the request is an executable task. Retrieve Experience for
+   planning, tool use, environment changes, multi-step workflows, or recovery
+   from a failed attempt. Skip retrieval for casual conversation and simple
+   knowledge answers.
+2. Build one concise query containing the task goal, domain object, intended
+   operation, and important constraints. After a failure, include the failed
+   operation and stable error signature.
+3. Search only the current user's Experience root:
+
+   ```text
+   viking://~/memories/experiences
+   ```
+
+   For tools using MCP-style parameters, set `target_uri` to this root. For
+   OpenClaw `ov_search`, set `uri` to this root. Never hardcode `default`,
+   `test`, or another user ID. If the server rejects the URI, resolve the root
+   as described in *Servers Without the Home Alias* and retry once.
+4. Start with `limit=5` and the tool's normal score threshold. Judge results by
+   task, environment, preconditions, and likely effect; title similarity alone
+   is insufficient. If no result is relevant, continue without Experience and
+   do not broaden the search to unrelated memory directories.
+5. Select only the one to three Experience files likely to change execution.
+   Require an exact file URI without a query or fragment. Ignore directories,
+   unrelated memory types, and sidecars such as `.abstract.md` and `.overview.md`.
+6. Read every selected canonical `viking://.../memories/experiences/...` URI
+   with the runtime's OpenViking read tool. Search abstracts help selection but
+   are not a substitute for reading the Experience body.
+7. Apply relevant steps and checks while executing the task. Do not repeat the
+   Experience verbatim to the user unless its content is directly needed in the
+   answer.
+8. If execution fails for a materially new reason, perform at most one focused
+   follow-up search using the failure evidence, then read only newly relevant
+   Experience files.
+
+## Servers Without the Home Alias
+
+`viking://~` is the home alias for the caller's own space. A server released
+before the alias (OpenViking v0.4.16) does not resolve it and rejects the
+request with `INVALID_URI` (HTTP 400) instead of searching. Retry once against
+the caller's explicit root, resolved from evidence rather than guessed:
+
+- If a canonical `viking://user/<user_id>/...` URI is already visible in this
+  session — injected memory context, or an earlier OpenViking tool result —
+  reuse that `<user_id>` and search
+  `viking://user/<user_id>/memories/experiences`.
+- Otherwise repeat the same query with no target scope, narrowed to memories
+  with `context_type` when the tool accepts it, and keep only hits whose URI
+  contains `/memories/experiences/`. Those hits carry the canonical user ID;
+  reuse it for the reads and for any later Experience search in this task.
+
+Do not fall back to the uid-less `viking://user/memories/experiences`: only
+some older servers and roles expand it, and current servers reject it. If no
+explicit root can be resolved, continue without Experience.
+
+## Applying Retrieved Experience
+
+- Treat Experience as reusable procedure, not as a user profile, user intent,
+  security policy, or proof that an action succeeded.
+- Follow priority in this order: system and developer instructions, current
+  user request, current environment and tool evidence, then Experience.
+- Ignore stale, incompatible, unsafe, or conflicting guidance. Verify commands,
+  paths, APIs, versions, and destructive actions against the current task.
+- Preserve confirmation requirements and permission boundaries. Prior success
+  never authorizes a destructive or external action in the current session.
+- When multiple Experience files conflict, prefer the one whose preconditions
+  match the current environment; otherwise proceed conservatively and surface
+  the ambiguity when it affects the user.
+
+## Session Evidence
+
+Use real Agent tool calls so the committed OpenViking session retains their
+ToolParts:
+
+- A completed generic OpenViking `find`, `search`, or `list` result containing
+  an Experience URI records recall for that Experience.
+- A completed generic OpenViking `read` or `multi_read` of an Experience URI
+  records injection and can associate the resulting trajectory with that
+  Experience.
+- Failed, cancelled, or incomplete calls do not count.
+
+Do not edit, summarize away, or synthesize these ToolParts before the session
+is committed.
+
+## Example
+
+For a request to fix a deployment failure:
+
+1. Search the Experience root with a query such as
+   `Kubernetes deployment image pull failure private registry`.
+2. Read the most relevant exact Experience URI.
+3. Check that its registry, credential, and rollout assumptions match the
+   current cluster.
+4. Apply the compatible diagnostic steps, verify the live result, and continue
+   the user's task.

package/skills.mjs

@@ -4,7 +4,7 @@ import * as skillFilesystem from "@deepseek-ai/dsh-skill-filesystem";
 /** Provider name on `ctx.skills`; must not collide with DSH's own `filesystem`. */
 export const SKILL_PROVIDER_NAME = "openviking";
 
-/** The shared `openviking-memory` and `openviking-skills` skills, vendored from examples/skills. */
+/** The shared OpenViking skills, vendored from examples/skills. */
 export const SKILLS_DIR = fileURLToPath(new URL("./skills", import.meta.url));
 
 export function buildSkillsConfig() {