Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
Python agent-contextagent-memoryagent-pluginsagentic-ragcontext-databasedsh-pluginknowledge-basememorymemory-managementself-evolvingvector-database
docs: install through openviking.ai/install in guides, plugin READMEs and doctor hints (#5478)
t0sakiebc8e5dfc800
diff --git a/agent-plugins/README.md b/agent-plugins/README.mdindex 09286b923..9c154ea70 100644--- a/agent-plugins/README.md+++ b/agent-plugins/README.md@@ -56,12 +56,11 @@ Config file changes are picked up by the running proxy without a restart. DebuggThis package is the portable recall + write surface: skills plus MCP tools, driven by the model. Agent Plugins 1.0 deliberately excludes hooks, commands, and agents, so **automatic conversation capture and automatic pre-prompt recall are out of scope here** — the `skills/openviking-memory` skill instead teaches the model to recall at task start and persist durable facts via `remember`/`write` itself.-**If your harness has a hook system, prefer the dedicated plugin** — hook-driven recall and capture cost no tool calls and don't depend on the model choosing to remember. One installer covers Claude Code, Codex, Cursor, TRAE / TRAE CN, ZCode, OpenCode, and pi; it prompts for language, harnesses, download source, and credentials, and is idempotent:+**If your harness has a hook system, prefer the dedicated plugin** — hook-driven recall and capture cost no tool calls and don't depend on the model choosing to remember. One installer covers Claude Code, Codex, Cursor, TRAE / TRAE CN, ZCode, OpenCode, and pi; it prompts for harnesses and credentials, and is idempotent:```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)-# GitHub hard to reach? Same installer from the Volcengine TOS mirror:-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/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.```- [claude-code-memory-plugin](../examples/claude-code-memory-plugin/) (Claude Code)diff --git a/docs/en/agent-integrations/02-claude-code.md b/docs/en/agent-integrations/02-claude-code.mdindex 2e41896d4..83e2637ae 100644--- a/docs/en/agent-integrations/02-claude-code.md+++ b/docs/en/agent-integrations/02-claude-code.md@@ -6,16 +6,11 @@ Source: [examples/claude-code-memory-plugin](https://github.com/volcengine/OpenV## Install-Claude Code and Codex share one installer. It asks for your language (English/中文), which harnesses to install, the download source, and your OpenViking credentials; every step is idempotent—re-running it is entirely safe.+Claude Code and Codex share one installer. It asks which harnesses to install and for your OpenViking credentials; every step is idempotent—re-running it is entirely safe.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)-```--In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror (or pick "TOS mirror" at the download-source prompt):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/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.```> **Plugin updates**: on Claude Code 2.1.224 or later, the installer registers a marketplace served by the OpenViking documentation site with auto-update turned on, so new plugin versions download in the background and load after a restart. Older Claude Code gets a local directory marketplace, which cannot auto-update — re-run the installer to update. (Codex installs from a git repository on the same site and keeps remote updates.)diff --git a/docs/en/agent-integrations/04-codex.md b/docs/en/agent-integrations/04-codex.mdindex 130626038..c7a5194a5 100644--- a/docs/en/agent-integrations/04-codex.md+++ b/docs/en/agent-integrations/04-codex.md@@ -6,25 +6,14 @@ Source: [examples/codex-memory-plugin](https://github.com/volcengine/OpenViking/## Install-Claude Code and Codex share one installer. It asks for your language (English/中文), which harnesses to install, the download source, and your OpenViking credentials; every step is idempotent.+Claude Code and Codex share one installer. It asks which harnesses to install and for your OpenViking credentials; every step is idempotent.```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.```-TraeCode CLI 2.0 accepts this Codex-format plugin directly. Its default-installer entry is `--harness trae-cli`:--```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cli-```--In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror (or pick "TOS mirror" at the download-source prompt). Codex installs from a TOS-hosted git repo and keeps remote update support:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```+Codex installs from a git repository published with each OpenViking release and keeps remote update support. TraeCode CLI 2.0 accepts this Codex-format plugin directly: select **TraeCode CLI 2.0** when the installer asks which harnesses to install.No shell wrapper is needed anymore — the plugin ships a stdio MCP proxy that reads `~/.openviking/ovcli.conf` (or `OPENVIKING_*` env vars) at runtime, same as the hooks. After installing, launch Codex (`trae-cli` for TraeCode CLI 2.0):diff --git a/docs/en/agent-integrations/08-community-plugins.md b/docs/en/agent-integrations/08-community-plugins.mdindex 37e7a1560..fc09f20da 100644--- a/docs/en/agent-integrations/08-community-plugins.md+++ b/docs/en/agent-integrations/08-community-plugins.md@@ -20,15 +20,8 @@ ZCode does not expose `PreCompact`, `SessionEnd`, or subagent lifecycle hooks. TPrerequisites: Node.js 18+, a running OpenViking server, and ZCode.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness zcode-```--Use the TOS mirror where GitHub is unavailable:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness zcode --dist tos+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.```The installer detects `~/.zcode/` or the `zcode` binary, installs the runtime under `~/.openviking/agent-integrations/zcode/`, and merges hooks and MCP configuration into `~/.zcode/cli/config.json`.@@ -43,7 +36,7 @@ After restarting ZCode, verify that:| Hooks not firing | Hook configuration is disabled or stale | Re-run the installer and restart ZCode || Recall returns nothing | OpenViking is unavailable or has not extracted memories yet | Check `curl http://127.0.0.1:1933/health` and wait for extraction || MCP tools not appearing | The MCP proxy failed to start | Check the absolute `mcp.servers.openviking` command in `~/.zcode/cli/config.json` |-| Duplicate captures | An older installation left duplicate hook entries | Run `install.sh --harness zcode --uninstall`, then reinstall |+| Duplicate captures | An older installation left duplicate hook entries | Run `curl -fsSL https://openviking.ai/install \| bash -s -- --uninstall --yes --harness zcode`, then reinstall |Implementation details and currently verified ZCode assumptions are documented in the plugin's [README](https://github.com/volcengine/OpenViking/tree/main/examples/agent-hook-plugin) and [DESIGN.md](https://github.com/volcengine/OpenViking/blob/main/examples/agent-hook-plugin/DESIGN.md).@@ -65,22 +58,19 @@ transcript decoding, output formatting, and commit policy:Prerequisites: Node.js 18+, a running OpenViking server, and Kimi Code CLI.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness kimicode-```--Use the TOS mirror where GitHub is unavailable:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness kimicode --dist tos+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.```The installer assembles a self-contained runtime under`$KIMI_CODE_HOME/plugins/managed/openviking-memory/` (default Kimi home:`~/.kimi-code/`), then updates only the `openviking-memory` entry in`plugins/installed.json`. Existing plugin records are preserved. Re-run the-same command to upgrade, or add `--uninstall` to remove only this plugin.+same command to upgrade. To remove only this plugin:++```bash+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness kimicode+```The verified host contract and version are recorded in[`hosts/kimicode/DESIGN.md`](https://github.com/volcengine/OpenViking/blob/main/examples/agent-hook-plugin/hosts/kimicode/DESIGN.md).diff --git a/docs/en/agent-integrations/10-opencode.md b/docs/en/agent-integrations/10-opencode.mdindex c0de111a9..a35494506 100644--- a/docs/en/agent-integrations/10-opencode.md+++ b/docs/en/agent-integrations/10-opencode.md@@ -29,19 +29,14 @@ curl http://localhost:1933/health### One-line installer (recommended)-OpenCode shares the unified installer with Claude Code and Codex. It asks for your language (English/中文), which harnesses to install, the download source, and your OpenViking credentials; every step is idempotent—re-running it is entirely safe.+OpenCode shares the unified installer with Claude Code and Codex. It asks which harnesses to install and for your OpenViking credentials; every step is idempotent—re-running it is entirely safe.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) --harness opencode+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.```-In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror (or pick "TOS mirror" at the download-source prompt):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--The installer registers the npm plugin (or a local file plugin on the TOS channel), writes the `openviking` MCP server entry into `~/.config/opencode/opencode.json`, and configures `~/.openviking/ovcli.conf`.+The installer copies the plugin into `~/.config/opencode/plugins/` as a local file plugin, writes the `openviking` MCP server entry into `~/.config/opencode/opencode.json`, and configures `~/.openviking/ovcli.conf`.### Manual npm installdiff --git a/docs/en/agent-integrations/11-pi.md b/docs/en/agent-integrations/11-pi.mdindex 4e621a364..4879087b1 100644--- a/docs/en/agent-integrations/11-pi.md+++ b/docs/en/agent-integrations/11-pi.md@@ -27,16 +27,11 @@ Tool calls and results are captured as dedicated `tool` parts, and `tool_output`## Install-pi shares the unified installer with the other memory plugins. It asks for your language, harnesses, download source, and OpenViking credentials; every step is idempotent.+pi shares the unified installer with the other memory plugins. It asks which harnesses to install and for your OpenViking credentials; every step is idempotent.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) --harness pi-```--In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/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.```The installer installs the locked npm dependencies before replacing the extension in `~/.pi/agent/extensions/openviking` and configures `~/.openviking/ovcli.conf`. That directory is one of pi's auto-discovery roots, so pi loads the extension on the next start — no `pi install` needed. (Running `pi install` on the same path would load it twice — once via auto-discovery, once via the `packages` entry — producing a duplicate `/viking` command.)diff --git a/docs/en/agent-integrations/12-cursor.md b/docs/en/agent-integrations/12-cursor.mdindex 76bb50dff..562a42f38 100644--- a/docs/en/agent-integrations/12-cursor.md+++ b/docs/en/agent-integrations/12-cursor.md@@ -9,15 +9,8 @@ Prerequisites: macOS or Linux, Node.js 18+, and preferably the latest stable CurWhen prompted for the connection, Volcengine Cloud users should select **Volcengine OpenViking Cloud** and enter their API key. Select **Self-hosted / local** only when an OpenViking server is running locally.```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness cursor-```--If GitHub is unavailable, use the TOS mirror:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness cursor --dist tos+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.```Quit Cursor completely and restart it after installation.@@ -50,16 +43,10 @@ Project identity uses Cursor's `workspace_roots`, keeping workspace peers separa## Upgrade and uninstall-Re-run the install command from the same distribution channel to upgrade. Use the same channel for uninstall:+Re-run the install command to upgrade. To uninstall, run:```bash-# GitHub-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness cursor --uninstall --yes--# TOS-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness cursor --uninstall --yes+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness cursor```Uninstall removes only OpenViking-managed Cursor Hooks, MCP, Rule, Skills, and runtime files. Other configuration is preserved.diff --git a/docs/en/agent-integrations/13-trae.md b/docs/en/agent-integrations/13-trae.mdindex 2e475f8e1..de1c3f5bf 100644--- a/docs/en/agent-integrations/13-trae.md+++ b/docs/en/agent-integrations/13-trae.md@@ -9,35 +9,11 @@ Prerequisites: macOS or Linux, Node.js 18+, and a TRAE/TRAE CN release that suppWhen prompted for the connection, Volcengine Cloud users should select **Volcengine OpenViking Cloud** and enter their API key. Select **Self-hosted / local** only when an OpenViking server is running locally.```bash-# TRAE-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae--# TRAE CN-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cn--# Both-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae,trae-cn--# TraeCode CLI 2.0-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cli+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.```-If GitHub is unavailable, use the TOS mirror:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae,trae-cn --dist tos--# TraeCode CLI 2.0-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae-cli --dist tos-```--Quit and restart the corresponding client after installation.+When the installer asks which harnesses to install, select **TRAE**, **TRAE CN**, **TraeCode CLI 2.0**, or several of them. Quit and restart the corresponding client after installation.### TraeCode CLI 2.0: trust the hooks on first launch@@ -87,16 +63,10 @@ For Hook diagnostics, start the client with `OPENVIKING_DEBUG=1` and inspect:## Upgrade and uninstall-Re-run the corresponding install command to upgrade. Use the original distribution channel for uninstall:+Re-run the install command to upgrade. To uninstall TRAE CN:```bash-# GitHub, TRAE CN example-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cn --uninstall --yes--# TOS, TRAE CN example-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae-cn --uninstall --yes+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness trae-cn```Replace `trae-cn` with `trae` for TRAE. For TraeCode CLI 2.0, use `trae-cli plugin uninstall openviking-memory@openviking`. Running the installer with `--harness trae-cli --uninstall` only removes the deprecated standalone Hooks integration from older installations.@@ -110,7 +80,7 @@ Replace `trae-cn` with `trae` for TRAE. For TraeCode CLI 2.0, use `trae-cli plug| MCP does not connect | Check the URL/API key in `~/.openviking/ovcli.conf`, then restart the client. || A new session cannot recall the previous turn | Inspect the Hook log and confirm that `Stop` ran without `/commit` connection or authentication errors. || The same content is captured more than once | Check user and project Hooks for older `trae-auto-recall.mjs` or `trae-auto-capture.mjs` entries. Re-running the installer removes OpenViking-managed legacy entries. |-| TraeCode CLI 2.0 does not list the plugin | Run `trae-cli plugin list`; if `openviking-memory` is absent, rerun the installer with `--harness trae-cli`. |+| TraeCode CLI 2.0 does not list the plugin | Run `trae-cli plugin list`; if `openviking-memory` is absent, rerun the installer and select **TraeCode CLI 2.0**. |## See alsodiff --git a/docs/en/agent-integrations/15-agent-plugins.md b/docs/en/agent-integrations/15-agent-plugins.mdindex 144b29080..7e6ef487a 100644--- a/docs/en/agent-integrations/15-agent-plugins.md+++ b/docs/en/agent-integrations/15-agent-plugins.md@@ -73,16 +73,11 @@ The bundled `openviking-skills` skill covers the skills stored in OpenViking its**If your harness has its own hook system, prefer the dedicated plugin.** Hook-driven recall and capture happen without the model spending tool calls or deciding to remember, which is both cheaper and more reliable than the skill-driven loop. Use this Agent Plugins package for harnesses that have no hooks, or when you want one package that works across many clients.-One installer covers Claude Code, Codex, Cursor, TRAE / TRAE CN, ZCode, OpenCode, and pi. It asks for your language, which harnesses to install, the download source, and your OpenViking credentials, and every step is idempotent:+One installer covers Claude Code, Codex, Cursor, TRAE / TRAE CN, ZCode, OpenCode, and pi. It asks which harnesses to install and for your OpenViking credentials, and every step is idempotent:```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)-```--In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/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.```| Harness | Dedicated integration |diff --git a/docs/en/agent-integrations/16-capability-reference.md b/docs/en/agent-integrations/16-capability-reference.mdindex cb7a2cbc4..a0030f264 100644--- a/docs/en/agent-integrations/16-capability-reference.md+++ b/docs/en/agent-integrations/16-capability-reference.md@@ -180,8 +180,8 @@ Core modules at a glance (detailed further in the per-dimension sections):| trae / trae-cn | Config-driven (`~/.trae{,-cn}/hooks.json` + platform-specific mcp.json) | One-line `--harness trae,trae-cn` | `tr-` / `trcn-` | env + ovcli.conf `plugin.trae` / `plugin.trae_cn` | ❌ || zcode | Config-driven (merged into `~/.zcode/cli/config.json`, forcing `hooks.enabled=true`) | One-line `--harness zcode` | `zc-<sess_…>` | env + ovcli.conf `plugin.zcode` | ❌ || kimicode | Native Kimi Code plugin (`kimi.plugin.json`, managed copy + `installed.json`) | One-line `--harness kimicode` | `kc-<session_id>` | env + ovcli.conf `plugin.kimicode` + workspace files | ❌ |-| opencode | npm plugin `@openviking/opencode-plugin` (its config hook dynamically injects the MCP entry) | One-line `--harness opencode` (uses npm registration with a proxy snapshot fallback) / manual npm / from source | `oc-<id>`; subagents use `oc-<parent>__subagent-<child>` | env + ovcli.conf `plugin.opencode` | ✅ |-| dsh | In-process Cordis plugin (`cordis.patch.yml` entry) | Unified installer (asks for the profile, default `web`), or `dsh plugin --profile web add @openviking/dsh-memory-plugin` | `dsh-<session.id as-is>`; each subagent is assigned its own session | env + ovcli.conf `plugin.dsh` + the cordis patch config, which is the lowest behavior layer (credentials still come from the patch first) | ❌ |+| opencode | npm plugin `@openviking/opencode-plugin` (its config hook dynamically injects the MCP entry) | One-line `--harness opencode` (copies a local file plugin into `~/.config/opencode/plugins/`) / manual npm / from source | `oc-<id>`; subagents use `oc-<parent>__subagent-<child>` | env + ovcli.conf `plugin.opencode` | ✅ |+| dsh | In-process Cordis plugin (`cordis.patch.yml` entry) | Unified installer (profile `web` unless `--dsh-profile` names another), or `dsh plugin --profile web add @openviking/dsh-memory-plugin` | `dsh-<session.id as-is>`; each subagent is assigned its own session | env + ovcli.conf `plugin.dsh` + the cordis patch config, which is the lowest behavior layer (credentials still come from the patch first) | ❌ || pi | Native pi extension (loaded from a directory, with TypeScript transpiled on the fly via jiti) | One-line `--harness pi` (copied into the auto-discovery directory, no `pi install` needed) | `pi-<piSessionId>` | env + ovcli.conf `plugin.pi` (credential fields are resolved via the shared credential chain) | ✅ || openclaw | context-engine plugin (`ownsCompaction:true`) + 15 tools + 5 slash + 4 hooks + HTTP routes | ClawHub: run `openclaw plugins install clawhub:@openviking/openclaw-plugin` alongside `openclaw openviking setup` / npm installer / TOS offline bundle | A UUID is lowercased as-is, otherwise `sha256(sessionKey)`; `memory_store` temporary sessions use `memory-store-<ts>-<rand>` | `plugins.entries.openviking.config` in `openclaw.json` (strictly validated: unknown keys or invalid values force the plugin into setup-only mode) + a few env vars | ✅ `openclaw openviking setup` (interactive/non-interactive + key role probing + version compatibility check) || hermes | Hermes bundled MemoryProvider (ships with Hermes; no plugin installation required) | Run `hermes memory setup openviking` (interactive curses wizard), or manually run `hermes config set memory.provider openviking` + `.env` | Generated by Hermes and used unchanged | `.env` (`OPENVIKING_*`) or linked ovcli.conf (`use_ovcli_config` mode clears the 5 corresponding variables from .env) + config.yaml | ✅ (multi-level menu) |@@ -618,7 +618,7 @@ Each card serves as a quick-reference entry point. It records only the facts and- **Form**: This is the only in-process, native Cordis plugin (`export function apply`). Its tool surface is the server's MCP surface, mounted through `@deepseek-ai/dsh-mcp-client` and the shared stdio proxy (published as `mcp__openviking__*`), while its hooks call REST directly. It features 6 events: agent/session-start (emit) / agent/pre-step (waterfall) / session/event / session/flush / tools/pre-execute / tools/post-execute. Version 0.5.1.- **Capability highlights**: `ctx.provide("openvikingMemory")` allows other Cordis plugins to build upon it. Pre-step injection is transmitted as a user message, aligning with the `complete:true` rendering mode of the DSH persona.-- **Behavior notes**: The unified installer covers dsh and asks which profile to install into (default `web`, overridable with `--dsh-profile`); npm is the bundle's only distribution channel, so the github/tos choice does not apply and every mode except `dev` installs the published package; `dev` packs the checkout first, because `dsh plugin` forwards to pnpm and a linked source tree cannot resolve the dsh peers the bundle imports. The teardown commit is allocated 3 seconds with no threshold, and it does not trigger on SIGHUP or a consecutive Ctrl+C ([§3.3.3](#_3-3-3-shutdown-method-×-harness-outcome-matrix)). Compaction remains invisible to the plugin: injected content shrinks alongside the host's compaction, and the profile is not re-injected. Each subagent is assigned its own session ([§3.3.5](#_3-3-5-subagent-session-comparison)). The tool surface is the server's own MCP surface, reached through the same stdio proxy the other integrations use and published under `mcp__openviking__*`, so a server upgrade adds tools without a bundle release; the trade-off is that the proxy runs once per profile, so tool calls carry a process-level actor peer and `remember` is not session-scoped (recall, capture, and commit still resolve a peer per session). The bundle also ships the shared `openviking-memory` and `openviking-skills` skills. `uri-guard` lowercases tool names before matching: `tools/pre-execute` denies a file tool whose path is a `viking://` URI (a write or edit on a skill URI is pointed to `mcp__openviking__add_skill`), and `tools/post-execute` adds a notice (`form: "notice"`) when a `bash` command carries one.+- **Behavior notes**: The unified installer covers dsh and installs into the `web` profile unless `--dsh-profile` names another; npm is the bundle's only distribution channel, so every mode except `dev` installs the published package; `dev` packs the checkout first, because `dsh plugin` forwards to pnpm and a linked source tree cannot resolve the dsh peers the bundle imports. The teardown commit is allocated 3 seconds with no threshold, and it does not trigger on SIGHUP or a consecutive Ctrl+C ([§3.3.3](#_3-3-3-shutdown-method-×-harness-outcome-matrix)). Compaction remains invisible to the plugin: injected content shrinks alongside the host's compaction, and the profile is not re-injected. Each subagent is assigned its own session ([§3.3.5](#_3-3-5-subagent-session-comparison)). The tool surface is the server's own MCP surface, reached through the same stdio proxy the other integrations use and published under `mcp__openviking__*`, so a server upgrade adds tools without a bundle release; the trade-off is that the proxy runs once per profile, so tool calls carry a process-level actor peer and `remember` is not session-scoped (recall, capture, and commit still resolve a peer per session). The bundle also ships the shared `openviking-memory` and `openviking-skills` skills. `uri-guard` lowercases tool names before matching: `tools/pre-execute` denies a file tool whose path is a `viking://` URI (a write or edit on a skill URI is pointed to `mcp__openviking__add_skill`), and `tools/post-execute` adds a notice (`form: "notice"`) when a `bash` command carries one.- **Configuration**: Configured via environment variables, `ovcli.conf` (`plugin.dsh`), the workspace files, and the cordis patch, which is the lowest layer for behavior knobs. Credentials are the exception: an endpoint, key, account, user, or peer named in the patch overrides the credential chain.- **Dimension index**: tool surface [§1.1](#_1-1-active-tool-surface-agentic-calls) | recall [§3.2](#_3-2-automatic-recall-and-injection) | commit [§3.3.2](#_3-3-2-regular-commit-triggers)/[§3.3.3](#_3-3-3-shutdown-method-×-harness-outcome-matrix) | degradation [§3.6](#_3-6-degradation-and-fault-tolerance).diff --git a/docs/en/agent-integrations/17-dsh.md b/docs/en/agent-integrations/17-dsh.mdindex 47a671a70..e5ef8398f 100644--- a/docs/en/agent-integrations/17-dsh.md+++ b/docs/en/agent-integrations/17-dsh.md@@ -6,19 +6,14 @@ Source: [examples/dsh-memory-plugin](https://github.com/volcengine/OpenViking/tr## Install-DSH shares the installer with the other memory plugins. It asks for your language (English/中文), which harnesses to install, the download source, and your OpenViking credentials; every step is idempotent—re-running it is entirely safe.+DSH shares the installer with the other memory plugins. It asks which harnesses to install and for your OpenViking credentials; every step is idempotent—re-running it is entirely safe.```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.```-In regions where GitHub is hard to reach, run the same installer from the Volcengine TOS mirror (or pick "TOS mirror" at the download-source prompt):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--When DSH is selected, the installer asks which profile to install into and defaults to `web`. Pass `--dsh-profile <name>` to answer it up front.+The installer puts the plugin into the `web` profile. To use another profile, pass `--dsh-profile <name>`: `curl -fsSL https://openviking.ai/install | bash -s -- --dsh-profile <name>`.After using it for a while, start a new conversation and ask about something you mentioned earlier—it will remember.diff --git a/docs/images/agents/en/claude-code.md b/docs/images/agents/en/claude-code.mdindex 776fa6d96..0a32d3304 100644--- a/docs/images/agents/en/claude-code.md+++ b/docs/images/agents/en/claude-code.md@@ -5,10 +5,11 @@ Because Claude Code may block installation scripts from unknown sources, automat1. Run the installer in your terminal:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness claude --dist tos+ 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.```-2. The installer will ask for language (English / Chinese), OpenViking credentials, and whether to enable the Statusline.+2. The installer will ask which harnesses to install for (select **Claude Code**), your OpenViking credentials, and whether to enable the Statusline.3. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:```textdiff --git a/docs/images/agents/en/codex.md b/docs/images/agents/en/codex.mdindex d0c54350d..8585c8c00 100644--- a/docs/images/agents/en/codex.md+++ b/docs/images/agents/en/codex.md@@ -3,10 +3,11 @@1. Run the installer in your terminal:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness codex --dist tos+ 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.```-2. The installer will ask for language (English / Chinese) and OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:+2. The installer will ask which harnesses to install for (select **Codex**) and for OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/images/agents/en/cursor.md b/docs/images/agents/en/cursor.mdindex 6e0f2f457..c8ef31d6e 100644--- a/docs/images/agents/en/cursor.md+++ b/docs/images/agents/en/cursor.md@@ -3,10 +3,11 @@1. Run the installer in your terminal:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/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.```-2. The installer will ask for language (English / Chinese) and OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:+2. The installer will ask which harnesses to install for (select **Cursor**) and for OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/images/agents/en/deepseek-harness.md b/docs/images/agents/en/deepseek-harness.mdindex ed4c9856d..88ca026ec 100644--- a/docs/images/agents/en/deepseek-harness.md+++ b/docs/images/agents/en/deepseek-harness.md@@ -3,18 +3,13 @@Run the installer:```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.```-If GitHub is difficult to reach, use the Volcengine TOS mirror:+The installer asks for the harness and OpenViking credentials:-```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--The installer asks for the language, harness, download source, and OpenViking credentials:--1. Select **DeepSeek Harness**. The plugin defaults to the `web` profile; use `--dsh-profile <name>` for another profile.+1. Select **DeepSeek Harness**. The plugin goes into the `web` profile; for another profile, run the command with `bash -s -- --dsh-profile <name>` in place of `bash`.2. Select **Volcengine OpenViking Cloud** and enter the API key:{{OPENVIKING_API_KEY_BLOCK}}@@ -29,7 +24,7 @@ The installer asks for the language, harness, download source, and OpenViking cr| Issue | What to check ||---|---|| No context injection or OpenViking tools | Run `dsh --profile web --dump-config` and confirm it contains `openviking-memory`; otherwise rerun the installer or run `dsh plugin --profile web add @openviking/dsh-memory-plugin` |-| Installed into the wrong profile | The installer defaults to `web`; rerun it with `--dsh-profile <name>` |+| Installed into the wrong profile | The installer uses `web`; rerun it with `bash -s -- --dsh-profile <name>` in place of `bash` || `ERESOLVE @deepseek-ai/dsh-*` during install | Prerelease tags may be out of sync; install `@deepseek-ai/[email protected]` exactly || Package reported missing from npm | pnpm rejects releases younger than 24 hours by default; wait and retry, or add the exact version to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` || Recall returns no history | Run `curl http://localhost:1933/health` to confirm the server is healthy, then check the endpoint and make sure the prompt is at least 3 characters long |diff --git a/docs/images/agents/en/opencode.md b/docs/images/agents/en/opencode.mdindex b33b38d12..cf5d3823e 100644--- a/docs/images/agents/en/opencode.md+++ b/docs/images/agents/en/opencode.md@@ -3,10 +3,11 @@1. Run the installer in your terminal:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness opencode --dist tos+ 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.```-2. The installer will ask for language (English / Chinese) and OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:+2. The installer will ask which harnesses to install for (select **OpenCode**) and for OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:```text{{OPENVIKING_API_KEY}}@@ -22,7 +23,7 @@| Problem | Fix ||---|---|-| Plugin is not loaded | Check `~/.config/opencode/opencode.json` includes `@openviking/opencode-plugin` |+| Plugin is not loaded | Check that `~/.config/opencode/plugins/openviking.js` exists; if not, re-run Install || Wrong server / 401 | Check `~/.openviking/ovcli.conf` and the API key || Recall is empty | Confirm the cloud instance has memories |diff --git a/docs/images/agents/en/trae.md b/docs/images/agents/en/trae.mdindex 87a55a008..ea01ded2b 100644--- a/docs/images/agents/en/trae.md+++ b/docs/images/agents/en/trae.md@@ -1,26 +1,13 @@## Step 1: Install-1. Run the command that matches your client:-- **Trae International**-- ```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae --dist tos- ```-- **Trae China**-- ```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae-cn --dist tos- ```-- **TraeCode CLI 2.0**+1. Run the installer in your terminal:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae-cli --dist tos+ 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.```-2. The installer will ask for language (English / Chinese) and OpenViking credentials. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:+2. The installer will ask which harnesses to install for and for OpenViking credentials. Select **TRAE** for Trae International, **TRAE CN** for Trae China, or **TraeCode CLI 2.0**. In the OpenViking credential step, choose **VolcEngine OpenViking Cloud Service [api.vikingdb.cn-beijing.volces.com]** and enter the API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/images/agents/zh/claude-code.md b/docs/images/agents/zh/claude-code.mdindex cf5a4ec78..94b06168d 100644--- a/docs/images/agents/zh/claude-code.md+++ b/docs/images/agents/zh/claude-code.md@@ -5,10 +5,11 @@1. 在终端执行如下安装命令:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness claude --dist tos+ curl -fsSL https://openviking.ai/install | bash+ # AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-2. 安装器会依次询问以下信息:语言(English / 中文)、OpenViking 凭据、是否开启 Statusline 状态栏。+2. 安装器会依次询问以下信息:要安装的 harness(勾选 **Claude Code**)、OpenViking 凭据、是否开启 Statusline 状态栏。3. 在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:```textdiff --git a/docs/images/agents/zh/codex.md b/docs/images/agents/zh/codex.mdindex ea245d858..d9c43b888 100644--- a/docs/images/agents/zh/codex.md+++ b/docs/images/agents/zh/codex.md@@ -3,10 +3,11 @@1. 在终端执行如下安装命令:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness codex --dist tos+ curl -fsSL https://openviking.ai/install | bash+ # AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-2. 安装器会依次询问以下信息:语言(English / 中文)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:+2. 安装器会依次询问以下信息:要安装的 harness(勾选 **Codex**)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/images/agents/zh/cursor.md b/docs/images/agents/zh/cursor.mdindex 8e32162a2..3971a70ec 100644--- a/docs/images/agents/zh/cursor.md+++ b/docs/images/agents/zh/cursor.md@@ -3,10 +3,11 @@1. 在终端执行如下安装命令:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)+ curl -fsSL https://openviking.ai/install | bash+ # AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-2. 安装器会依次询问以下信息:语言(English / 中文)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:+2. 安装器会依次询问以下信息:要安装的 harness(勾选 **Cursor**)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/images/agents/zh/deepseek-harness.md b/docs/images/agents/zh/deepseek-harness.mdindex cb53ea04e..e882ab6c3 100644--- a/docs/images/agents/zh/deepseek-harness.md+++ b/docs/images/agents/zh/deepseek-harness.md@@ -3,18 +3,13 @@运行安装器:```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 agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-若 GitHub 访问受限,可改用火山引擎 TOS 镜像:+安装器会依次询问 Harness 和 OpenViking 凭据:-```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--安装器会依次询问语言、Harness、下载源和 OpenViking 凭据:--1. Harness 选择 **DeepSeek Harness**。插件默认安装到 `web` profile,也可通过 `--dsh-profile <name>` 指定其他 profile。+1. Harness 选择 **DeepSeek Harness**。插件会装到 `web` profile;要装到其他 profile,把命令末尾的 `bash` 换成 `bash -s -- --dsh-profile <name>`。2. 连接方式选择 **火山引擎 OpenViking 云服务**,并填入 API Key:{{OPENVIKING_API_KEY_BLOCK}}@@ -29,7 +24,7 @@ bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shar| 现象 | 排查方向 ||---|---|| 没有上下文注入,也没有 OpenViking 工具 | 执行 `dsh --profile web --dump-config`,确认输出中包含 `openviking-memory`;若缺失,重新运行安装器或执行 `dsh plugin --profile web add @openviking/dsh-memory-plugin` |-| 插件安装到了错误的 profile | 安装器默认使用 `web`;通过 `--dsh-profile <name>` 重新运行 |+| 插件安装到了错误的 profile | 安装器默认使用 `web`;把命令末尾的 `bash` 换成 `bash -s -- --dsh-profile <name>` 重新运行 || 安装时报 `ERESOLVE @deepseek-ai/dsh-*` | 各包预发布 tag 可能不同步,请精确安装 `@deepseek-ai/[email protected]` || 安装时提示包不在 npm registry 中 | pnpm 默认拒绝发布不满 24 小时的版本;可稍后重试,或把精确版本加入 `pnpm-workspace.yaml` 的 `minimumReleaseAgeExclude` || 无法召回历史记忆 | 先执行 `curl http://localhost:1933/health` 确认服务端正常;再检查端点配置,并确认 prompt 不少于 3 个字符 |diff --git a/docs/images/agents/zh/opencode.md b/docs/images/agents/zh/opencode.mdindex f11c1d31c..0833fd84d 100644--- a/docs/images/agents/zh/opencode.md+++ b/docs/images/agents/zh/opencode.md@@ -3,10 +3,11 @@1. 在终端执行以下安装命令:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness opencode --dist tos+ curl -fsSL https://openviking.ai/install | bash+ # AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-2. 安装器会依次询问以下信息:语言(English / 中文)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:+2. 安装器会依次询问以下信息:要安装的 harness(勾选 **OpenCode**)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:```text{{OPENVIKING_API_KEY}}@@ -22,7 +23,7 @@| 问题 | 处理 ||---|---|-| 插件没加载 | 检查 `~/.config/opencode/opencode.json` 是否包含 `@openviking/opencode-plugin` |+| 插件没加载 | 检查 `~/.config/opencode/plugins/openviking.js` 是否存在;不存在就重新执行安装 || 连错服务 / 401 | 检查 `~/.openviking/ovcli.conf` 和 API Key || 召回为空 | 确认云端实例里已有记忆 |diff --git a/docs/images/agents/zh/trae.md b/docs/images/agents/zh/trae.mdindex 6b08d9e55..1e6671549 100644--- a/docs/images/agents/zh/trae.md+++ b/docs/images/agents/zh/trae.md@@ -1,26 +1,13 @@## 步骤1:安装-1. 根据所使用的客户端,在终端执行对应的安装命令:-- **Trae 国际版**-- ```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae --dist tos- ```-- **Trae 中国版**-- ```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae-cn --dist tos- ```-- **TraeCode CLI 2.0**+1. 在终端执行如下安装命令:```bash- bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) --harness trae-cli --dist tos+ curl -fsSL https://openviking.ai/install | bash+ # AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-2. 安装器会依次询问以下信息:语言(English / 中文)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:+2. 安装器会依次询问以下信息:要安装的 harness(Trae 国际版勾选 **TRAE**,Trae 中国版勾选 **TRAE CN**,或勾选 **TraeCode CLI 2.0**)、OpenViking 凭据。在 OpenViking 凭据配置中,选择连接至「火山引擎 OpenViking 云服务 [api.vikingdb.cn-beijing.volces.com]」,并填入 API KEY:```text{{OPENVIKING_API_KEY}}diff --git a/docs/zh/agent-integrations/02-claude-code.md b/docs/zh/agent-integrations/02-claude-code.mdindex 7fe7cb861..3db726c06 100644--- a/docs/zh/agent-integrations/02-claude-code.md+++ b/docs/zh/agent-integrations/02-claude-code.md@@ -6,16 +6,11 @@## 安装-Claude Code 和 Codex 共用同一个安装脚本。它会依次询问界面语言(English/中文)、要安装的 harness、下载源和 OpenViking 凭据;所有步骤幂等,重复运行安全。+Claude Code 和 Codex 共用同一个安装脚本。它会询问要安装的 harness 和 OpenViking 凭据;所有步骤幂等,重复运行安全。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)-```--GitHub 访问受限的地区,从火山引擎 TOS 镜像运行同一个安装脚本(或在下载源提问时选择「TOS 镜像」):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```> **插件更新**:Claude Code 2.1.224 及以上版本,安装脚本注册的是 OpenViking 文档站托管的 marketplace 并开启自动更新,新版插件在后台下载,重启 Claude Code 后生效。更早的 Claude Code 注册的是本地目录 marketplace,**无法自动更新**——更新请重跑安装脚本。(Codex 安装自同一站点上的 git 仓库,保留远程更新能力。)diff --git a/docs/zh/agent-integrations/04-codex.md b/docs/zh/agent-integrations/04-codex.mdindex 44419dcbf..1ccdab493 100644--- a/docs/zh/agent-integrations/04-codex.md+++ b/docs/zh/agent-integrations/04-codex.md@@ -6,24 +6,14 @@## 安装-Claude Code 和 Codex 共用同一个安装脚本。它会依次询问界面语言(English/中文)、要安装的 harness、下载源和 OpenViking 凭据;所有步骤幂等,可安全地重复执行。+Claude Code 和 Codex 共用同一个安装脚本。它会询问要安装的 harness 和 OpenViking 凭据;所有步骤幂等,可安全地重复执行。```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 agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-TraeCode CLI 2.0 可以直接安装这一 Codex 格式插件,默认安装入口是 `--harness trae-cli`:--```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cli-```--GitHub 访问受限的地区,从火山引擎 TOS 镜像运行同一个安装脚本(或在下载源提问时选择「TOS 镜像」)。Codex 走 TOS 时安装自 TOS 托管的 git 仓库,保留远程更新能力:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```+Codex 从随 OpenViking 发布的 git 仓库安装插件,保留远程更新能力。TraeCode CLI 2.0 可以直接安装这一 Codex 格式插件:安装器询问要安装的 harness 时,勾选 **TraeCode CLI 2.0** 即可。现在不再需要任何 shell wrapper——插件自带的 stdio MCP 代理会在运行时读取 `~/.openviking/ovcli.conf`(或 `OPENVIKING_*` 环境变量),与 hooks 使用同一套配置链。安装完成后启动 Codex(TraeCode CLI 2.0 是 `trae-cli`):diff --git a/docs/zh/agent-integrations/08-community-plugins.md b/docs/zh/agent-integrations/08-community-plugins.mdindex 202e8019d..79bfa5a1d 100644--- a/docs/zh/agent-integrations/08-community-plugins.md+++ b/docs/zh/agent-integrations/08-community-plugins.md@@ -20,15 +20,8 @@ ZCode 不提供 `PreCompact`、`SessionEnd` 和 subagent 生命周期 Hook。因前置条件:Node.js 18+、正在运行的 OpenViking 服务,以及 ZCode。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness zcode-```--GitHub 不可用的地区可使用 TOS 镜像:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness zcode --dist tos+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```安装器通过 `~/.zcode/` 或 `zcode` 二进制检测 ZCode,将运行时安装到 `~/.openviking/agent-integrations/zcode/`,并把 Hook 与 MCP 配置合并到 `~/.zcode/cli/config.json`。@@ -43,7 +36,7 @@ bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shar| Hook 未执行 | Hook 配置被禁用或已过期 | 重跑安装器并重启 ZCode || 召回为空 | OpenViking 不可用或记忆尚未提取 | 检查 `curl http://127.0.0.1:1933/health`,并等待提取完成 || MCP 工具未出现 | MCP proxy 启动失败 | 检查 `~/.zcode/cli/config.json` 中 `mcp.servers.openviking` 的绝对路径命令 |-| 重复捕获 | 旧安装留下了重复 Hook 条目 | 先运行 `install.sh --harness zcode --uninstall`,再重新安装 |+| 重复捕获 | 旧安装留下了重复 Hook 条目 | 先运行 `curl -fsSL https://openviking.ai/install \| bash -s -- --uninstall --yes --harness zcode`,再重新安装 |实现细节与当前已验证的 ZCode 假设见插件目录中的 [README](https://github.com/volcengine/OpenViking/tree/main/examples/agent-hook-plugin) 和 [DESIGN.md](https://github.com/volcengine/OpenViking/blob/main/examples/agent-hook-plugin/DESIGN.md)。@@ -63,21 +56,18 @@ Kimi Code 集成是原生 managed plugin。它复用 OpenViking 的共享 Hook前置条件:Node.js 18+、正在运行的 OpenViking 服务,以及 Kimi Code CLI。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness kimicode-```--GitHub 不可用的地区可使用 TOS 镜像:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness kimicode --dist tos+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```安装器会在 `$KIMI_CODE_HOME/plugins/managed/openviking-memory/`下组装自包含运行时(Kimi home 默认为 `~/.kimi-code/`),并且只更新`plugins/installed.json` 中的 `openviking-memory` 记录,不动其他插件。-重跑同一命令可升级;加上 `--uninstall` 只卸载该插件。+重跑同一命令可升级。只卸载该插件:++```bash+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness kimicode+```已验证的宿主契约和版本见[`hosts/kimicode/DESIGN.md`](https://github.com/volcengine/OpenViking/blob/main/examples/agent-hook-plugin/hosts/kimicode/DESIGN.md)。diff --git a/docs/zh/agent-integrations/10-opencode.md b/docs/zh/agent-integrations/10-opencode.mdindex ae2b2ac95..0530e1b92 100644--- a/docs/zh/agent-integrations/10-opencode.md+++ b/docs/zh/agent-integrations/10-opencode.md@@ -29,19 +29,14 @@ curl http://localhost:1933/health### 一键安装(推荐)-OpenCode 与 Claude Code、Codex 共用同一个安装器。它会询问语言(English/中文)、要安装的 harness、下载源和 OpenViking 凭据;每一步都是幂等的,重复运行完全安全。+OpenCode 与 Claude Code、Codex 共用同一个安装器。它会询问要安装的 harness 和 OpenViking 凭据;每一步都是幂等的,重复运行完全安全。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) --harness opencode+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-在 GitHub 访问困难的地区,可从火山引擎 TOS 镜像运行同一个安装器(或在下载源选择步骤选"TOS mirror"):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--安装器会注册 npm 插件(TOS 渠道则安装本地文件插件),把 `openviking` MCP server 条目写进 `~/.config/opencode/opencode.json`,并配置 `~/.openviking/ovcli.conf`。+安装器会把插件作为本地文件插件复制到 `~/.config/opencode/plugins/`,把 `openviking` MCP server 条目写进 `~/.config/opencode/opencode.json`,并配置 `~/.openviking/ovcli.conf`。### 手动 npm 安装diff --git a/docs/zh/agent-integrations/11-pi.md b/docs/zh/agent-integrations/11-pi.mdindex e44539933..cf56b1c41 100644--- a/docs/zh/agent-integrations/11-pi.md+++ b/docs/zh/agent-integrations/11-pi.md@@ -27,16 +27,11 @@## 安装-pi 与其他记忆插件共用同一个安装器。它会询问语言、要安装的 harness、下载源和 OpenViking 凭据;每一步都是幂等的。+pi 与其他记忆插件共用同一个安装器。它会询问要安装的 harness 和 OpenViking 凭据;每一步都是幂等的。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) --harness pi-```--在 GitHub 访问困难的地区,可从火山引擎 TOS 镜像运行同一个安装器:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```安装器会先安装 lockfile 中锁定的 npm 依赖,再将扩展放到 `~/.pi/agent/extensions/openviking`,并配置 `~/.openviking/ovcli.conf`。该目录是 pi 的自动发现根目录之一,复制到位后 pi 会在下次启动时自动加载,无需再执行 `pi install`。(对同一路径再跑 `pi install` 会让扩展被加载两遍——一次来自自动发现,一次来自 `packages` 条目——出现重复的 `/viking` 命令。)diff --git a/docs/zh/agent-integrations/12-cursor.md b/docs/zh/agent-integrations/12-cursor.mdindex 12498d68b..c0c9f5706 100644--- a/docs/zh/agent-integrations/12-cursor.md+++ b/docs/zh/agent-integrations/12-cursor.md@@ -9,15 +9,8 @@安装器询问连接方式时,火山引擎云服务用户请选择 **火山引擎 OpenViking 云服务** 并填写 API Key。只有本机已运行 OpenViking 服务时才选择 **自建 / 本地**。```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness cursor-```--GitHub 访问受限时使用 TOS 镜像:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness cursor --dist tos+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```安装完成后完全退出并重新启动 Cursor。@@ -50,16 +43,10 @@ skill 清单先列你自己的 skill,再列账号内共享的 skill;共享 s## 升级与卸载-重复运行对应渠道的安装命令即可升级。卸载时也应使用原安装渠道:+重复运行安装命令即可升级。卸载时运行:```bash-# GitHub-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness cursor --uninstall --yes--# TOS-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness cursor --uninstall --yes+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness cursor```卸载仅移除 OpenViking 管理的 Cursor Hook、MCP、Rule、Skill 和运行文件,保留其他配置。diff --git a/docs/zh/agent-integrations/13-trae.md b/docs/zh/agent-integrations/13-trae.mdindex aa2ba33f0..9d78ac2d4 100644--- a/docs/zh/agent-integrations/13-trae.md+++ b/docs/zh/agent-integrations/13-trae.md@@ -9,35 +9,11 @@安装器询问连接方式时,火山引擎云服务用户请选择 **火山引擎 OpenViking 云服务** 并填写 API Key。只有本机已运行 OpenViking 服务时才选择 **自建 / 本地**。```bash-# TRAE-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae--# TRAE CN-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cn--# 同时安装-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae,trae-cn--# TraeCode CLI 2.0-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cli+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-GitHub 访问受限时使用 TOS 镜像:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae,trae-cn --dist tos--# TraeCode CLI 2.0-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae-cli --dist tos-```--安装后完全退出并重启对应客户端。+安装器询问要安装的 harness 时,勾选 **TRAE**、**TRAE CN** 或 **TraeCode CLI 2.0**,也可以多选。安装后完全退出并重启对应客户端。### TraeCode CLI 2.0:首次启动信任 hooks@@ -87,16 +63,10 @@ skill 清单先列你自己的 skill,再列账号内共享的 skill,每条## 升级与卸载-重复运行对应安装命令即可升级。卸载时也应使用原安装渠道:+重复运行安装命令即可升级。卸载 TRAE CN:```bash-# GitHub,以 TRAE CN 为例-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh) \- --harness trae-cn --uninstall --yes--# TOS,以 TRAE CN 为例-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh) \- --harness trae-cn --uninstall --yes+curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness trae-cn```将 `trae-cn` 替换为 `trae` 可管理 TRAE 集成。TraeCode CLI 2.0 请执行 `trae-cli plugin uninstall openviking-memory@openviking`。安装器的 `--harness trae-cli --uninstall` 只用于移除旧安装中已弃用的独立 Hooks 集成。@@ -110,7 +80,7 @@ bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shar| MCP 未连接 | 检查 `~/.openviking/ovcli.conf` 中的 URL/API Key,然后重启客户端。 || 新会话无法回忆上一轮内容 | 查看 Hook 日志,确认 `Stop` 已执行且 `/commit` 没有连接或鉴权错误。 || 同一内容被捕获多次 | 检查用户级与项目级 Hook 中是否仍有旧版 `trae-auto-recall.mjs` 或 `trae-auto-capture.mjs`;重跑安装器会移除由 OpenViking 管理的旧条目。 |-| TraeCode CLI 2.0 未列出插件 | 运行 `trae-cli plugin list`;若没有 `openviking-memory`,使用 `--harness trae-cli` 重跑安装器。 |+| TraeCode CLI 2.0 未列出插件 | 运行 `trae-cli plugin list`;若没有 `openviking-memory`,重跑安装器并勾选 **TraeCode CLI 2.0**。 |## 参见diff --git a/docs/zh/agent-integrations/15-agent-plugins.md b/docs/zh/agent-integrations/15-agent-plugins.mdindex 630a7ef5c..0f888fa90 100644--- a/docs/zh/agent-integrations/15-agent-plugins.md+++ b/docs/zh/agent-integrations/15-agent-plugins.md@@ -73,16 +73,11 @@ Agent Plugins 1.0 只覆盖 skills 和 MCP servers;hooks、commands、agents**如果你的 harness 支持 hooks 机制,推荐使用专属插件。** hook 驱动的召回与捕获不需要模型花费工具调用、也不依赖模型「想起来要记」,比技能驱动的闭环更省 token、也更可靠。本 Agent Plugins 包适用于没有 hooks 的 harness,或你希望用同一个包覆盖多个客户端的场景。-Claude Code、Codex、Cursor、TRAE / TRAE CN、ZCode、OpenCode、pi 共用同一个安装脚本。它会依次询问界面语言、要安装的 harness、下载源和 OpenViking 凭据,所有步骤幂等,重复运行安全:+Claude Code、Codex、Cursor、TRAE / TRAE CN、ZCode、OpenCode、pi 共用同一个安装脚本。它会询问要安装的 harness 和 OpenViking 凭据,所有步骤幂等,重复运行安全:```bash-bash <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/install.sh)-```--GitHub 访问受限的地区,从火山引擎 TOS 镜像运行同一个脚本:--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)+curl -fsSL https://openviking.ai/install | bash+# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```| Harness | 专属集成 |diff --git a/docs/zh/agent-integrations/16-capability-reference.md b/docs/zh/agent-integrations/16-capability-reference.mdindex 73054b6ce..e09592b7a 100644--- a/docs/zh/agent-integrations/16-capability-reference.md+++ b/docs/zh/agent-integrations/16-capability-reference.md@@ -182,8 +182,8 @@ per-harness 章节(档案卡)只写差异;所有共享事实均在本章| trae / trae-cn | 配置驱动(`~/.trae{,-cn}/hooks.json` + 平台相关 mcp.json) | 一键 `--harness trae,trae-cn` | `tr-` / `trcn-` | env + ovcli.conf `plugin.trae` / `plugin.trae_cn` | ❌ || zcode | 配置驱动(合并进 `~/.zcode/cli/config.json`,并强制 `hooks.enabled=true`) | 一键 `--harness zcode` | `zc-<sess_…>` | env + ovcli.conf `plugin.zcode` | ❌ || kimicode | Kimi Code 原生插件(`kimi.plugin.json`,managed copy + `installed.json`) | 一键 `--harness kimicode` | `kc-<session_id>` | env + ovcli.conf `plugin.kimicode` + workspace 文件 | ❌ |-| opencode | npm 插件 `@openviking/opencode-plugin`(config hook 自注入 MCP 条目) | 一键 `--harness opencode`(npm 注册 + 代理快照兜底)/ 手动 npm / 源码 | `oc-<id>`;subagent 格式为 `oc-<parent>__subagent-<child>` | env + ovcli.conf `plugin.opencode` | ✅ |-| dsh | Cordis 同进程插件(`cordis.patch.yml` 条目) | 统一安装器(会询问 profile,默认 `web`),或执行 `dsh plugin --profile web add @openviking/dsh-memory-plugin` | `dsh-<session.id 原样>`;subagent 各自独立会话 | env + ovcli.conf `plugin.dsh` + cordis patch config(行为旋钮的最低层;凭据仍以 patch 优先) | ❌ |+| opencode | npm 插件 `@openviking/opencode-plugin`(config hook 自注入 MCP 条目) | 一键 `--harness opencode`(复制为 `~/.config/opencode/plugins/` 下的本地文件插件)/ 手动 npm / 源码 | `oc-<id>`;subagent 格式为 `oc-<parent>__subagent-<child>` | env + ovcli.conf `plugin.opencode` | ✅ |+| dsh | Cordis 同进程插件(`cordis.patch.yml` 条目) | 统一安装器(默认装到 `web` profile,可用 `--dsh-profile` 指定),或执行 `dsh plugin --profile web add @openviking/dsh-memory-plugin` | `dsh-<session.id 原样>`;subagent 各自独立会话 | env + ovcli.conf `plugin.dsh` + cordis patch config(行为旋钮的最低层;凭据仍以 patch 优先) | ❌ || pi | pi 原生扩展(目录装载,jiti 直译 TS) | 一键 `--harness pi`(复制到自动发现目录,无需 `pi install`) | `pi-<piSessionId>` | env + ovcli.conf `plugin.pi`(凭据字段由凭据链统一解析) | ✅ || openclaw | context-engine 插件(`ownsCompaction:true`)+ 15 工具 + 5 slash + 4 hook + HTTP 路由 | ClawHub 执行 `openclaw plugins install clawhub:@openviking/openclaw-plugin` 搭配 `openclaw openviking setup` / npm 安装器 / TOS 离线包 | UUID 原样小写,否则 `sha256(sessionKey)`;`memory_store` 临时会话 `memory-store-<ts>-<rand>` | `openclaw.json` 的 `plugins.entries.openviking.config`(严格校验:存在未知键/非法值时插件进入 setup-only 模式)+ 少量 env | ✅ `openclaw openviking setup`(交互/非交互 + key 角色探测 + 版本兼容检查) || hermes | Hermes bundled MemoryProvider(随 Hermes 发布,无需装插件) | 执行 `hermes memory setup openviking`(curses 向导)或手动 `hermes config set memory.provider openviking` + `.env` | 由 Hermes 生成,插件原样使用 | `.env`(`OPENVIKING_*`)或 ovcli.conf 联动(`use_ovcli_config` 模式会清空 .env 里的 5 个对应变量)+ config.yaml | ✅(多层菜单) |@@ -600,7 +600,7 @@ MCP `write` / REST `content/write` 的三道 guard(`content_write.py`):可- **形态**:唯一同进程 Cordis 原生插件(`export function apply`),工具面就是服务端的 MCP 面,经 `@deepseek-ai/dsh-mcp-client` 与共享 stdio 代理接入(以 `mcp__openviking__*` 发布),hook 侧 REST 直连。6 事件:agent/session-start(emit)/ agent/pre-step(waterfall)/ session/event / session/flush / tools/pre-execute / tools/post-execute。版本 0.5.1。- **能力亮点**:`ctx.provide("openvikingMemory")` 供其他 Cordis 插件二次开发;pre-step 注入走 user 消息,适配 DSH persona 的 `complete:true` 渲染模式。-- **行为要点**:统一安装器已覆盖 dsh,会询问装到哪个 profile(默认 `web`,可用 `--dsh-profile` 指定);npm 是该插件唯一的分发渠道,因此 github/tos 选择对它不适用,除 `dev` 外的模式一律装已发布的包;`dev` 会先把 checkout 打包再装——`dsh plugin` 转发给 pnpm,link 一个源码目录无法解析插件 import 的 dsh peer;teardown commit 3s 无阈值,SIGHUP/二次 Ctrl+C 不触发([§3.3.3](#_3-3-3-关闭方式-×-harness-终局矩阵));compaction 不感知(注入内容随宿主压缩收缩,profile 不重投);subagent 各自独立会话([§3.3.5](#_3-3-5-subagent-会话对照));工具面即服务端自身的 MCP 面,经与其他集成同一个 stdio 代理接入、以 `mcp__openviking__*` 发布,服务端升级即可增加工具而无需发版;代价是代理每个 profile 只起一个进程,因此工具调用带的是进程级 actor peer、`remember` 也不绑当前会话(召回/捕获/commit 仍按会话解析 peer);另随包附带共享的 `openviking-memory` 与 `openviking-skills` 两个 skill;uri-guard 先把工具名转成小写再匹配,tools/pre-execute 拒绝路径是 `viking://` URI 的文件工具(针对 skill URI 的 write/edit 会被引导到 `mcp__openviking__add_skill`),bash 命令带 `viking://` URI 时由 tools/post-execute 附加提示(`form: "notice"`)。+- **行为要点**:统一安装器已覆盖 dsh,默认装到 `web` profile,可用 `--dsh-profile` 指定其他 profile;npm 是该插件唯一的分发渠道,因此除 `dev` 外的模式一律装已发布的包;`dev` 会先把 checkout 打包再装——`dsh plugin` 转发给 pnpm,link 一个源码目录无法解析插件 import 的 dsh peer;teardown commit 3s 无阈值,SIGHUP/二次 Ctrl+C 不触发([§3.3.3](#_3-3-3-关闭方式-×-harness-终局矩阵));compaction 不感知(注入内容随宿主压缩收缩,profile 不重投);subagent 各自独立会话([§3.3.5](#_3-3-5-subagent-会话对照));工具面即服务端自身的 MCP 面,经与其他集成同一个 stdio 代理接入、以 `mcp__openviking__*` 发布,服务端升级即可增加工具而无需发版;代价是代理每个 profile 只起一个进程,因此工具调用带的是进程级 actor peer、`remember` 也不绑当前会话(召回/捕获/commit 仍按会话解析 peer);另随包附带共享的 `openviking-memory` 与 `openviking-skills` 两个 skill;uri-guard 先把工具名转成小写再匹配,tools/pre-execute 拒绝路径是 `viking://` URI 的文件工具(针对 skill URI 的 write/edit 会被引导到 `mcp__openviking__add_skill`),bash 命令带 `viking://` URI 时由 tools/post-execute 附加提示(`form: "notice"`)。- **配置**:env + ovcli.conf `plugin.dsh` + workspace 文件 + cordis patch(行为旋钮的最低层);凭据是例外,patch 里写的 endpoint / key / account / user / peer 仍然压过凭据链。- **维度索引**:工具面 [§1.1](#_1-1-主动工具面-agentic-调用能力) |召回 [§3.2](#_3-2-自动召回与注入) |commit [§3.3.2](#_3-3-2-常规-commit-触发条件)/[§3.3.3](#_3-3-3-关闭方式-×-harness-终局矩阵) |降级 [§3.6](#_3-6-降级与容错)。diff --git a/docs/zh/agent-integrations/17-dsh.md b/docs/zh/agent-integrations/17-dsh.mdindex d10bb3ca6..3e77c2b83 100644--- a/docs/zh/agent-integrations/17-dsh.md+++ b/docs/zh/agent-integrations/17-dsh.md@@ -6,19 +6,14 @@## 安装-DSH 与其他记忆插件共用同一个安装器。它会依次询问语言(English/中文)、要安装的 harness、下载源和 OpenViking 凭据;每一步都是幂等的,重复运行完全安全。+DSH 与其他记忆插件共用同一个安装器。它会询问要安装的 harness 和 OpenViking 凭据;每一步都是幂等的,重复运行完全安全。```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 agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```-GitHub 访问困难的地区,可以从火山引擎 TOS 镜像运行同一个安装器(或在下载源选项里选「TOS 镜像」):--```bash-bash <(curl -fsSL https://ovrelease.tos-cn-beijing.volces.com/memory-plugin-shared/install.sh)-```--选择 DSH 后,安装器会询问装到哪个 profile,默认 `web`。也可以用 `--dsh-profile <name>` 提前指定。+安装器会把插件装到 `web` profile。要装到其他 profile,用 `--dsh-profile <name>` 指定:`curl -fsSL https://openviking.ai/install | bash -s -- --dsh-profile <name>`。用一段时间后,开一个新会话问问之前提过的事情——它会记得。diff --git a/examples/agent-hook-plugin/hosts/cursor/openviking.integration.json b/examples/agent-hook-plugin/hosts/cursor/openviking.integration.jsonindex f9ac8024b..0c50afc16 100644--- a/examples/agent-hook-plugin/hosts/cursor/openviking.integration.json+++ b/examples/agent-hook-plugin/hosts/cursor/openviking.integration.json@@ -1,7 +1,7 @@{"schemaVersion": 1,"id": "openviking-memory",- "version": "0.5.6",+ "version": "0.5.7","clients": ["cursor"],diff --git a/examples/agent-hook-plugin/hosts/kimicode/kimi.plugin.json b/examples/agent-hook-plugin/hosts/kimicode/kimi.plugin.jsonindex 839bb1791..247e06fa5 100644--- a/examples/agent-hook-plugin/hosts/kimicode/kimi.plugin.json+++ b/examples/agent-hook-plugin/hosts/kimicode/kimi.plugin.json@@ -1,6 +1,6 @@{"name": "openviking-memory",- "version": "0.5.6",+ "version": "0.5.7","description": "Long-term semantic memory for Kimi Code CLI, powered by OpenViking.","author": {"name": "OpenViking",diff --git a/examples/agent-hook-plugin/hosts/kimicode/openviking.integration.json b/examples/agent-hook-plugin/hosts/kimicode/openviking.integration.jsonindex cf451adf9..1a98645af 100644--- a/examples/agent-hook-plugin/hosts/kimicode/openviking.integration.json+++ b/examples/agent-hook-plugin/hosts/kimicode/openviking.integration.json@@ -1,7 +1,7 @@{"schemaVersion": 1,"id": "openviking-memory",- "version": "0.5.6",+ "version": "0.5.7","clients": ["kimicode"],diff --git a/examples/agent-hook-plugin/hosts/trae/openviking.integration.json b/examples/agent-hook-plugin/hosts/trae/openviking.integration.jsonindex c2fb6921a..0ac0540e3 100644--- a/examples/agent-hook-plugin/hosts/trae/openviking.integration.json+++ b/examples/agent-hook-plugin/hosts/trae/openviking.integration.json@@ -1,7 +1,7 @@{"schemaVersion": 1,"id": "openviking-memory",- "version": "0.5.6",+ "version": "0.5.7","clients": ["trae","trae-cn"diff --git a/examples/agent-hook-plugin/hosts/zcode/openviking.integration.json b/examples/agent-hook-plugin/hosts/zcode/openviking.integration.jsonindex 8a1b95342..f772d7974 100644--- a/examples/agent-hook-plugin/hosts/zcode/openviking.integration.json+++ b/examples/agent-hook-plugin/hosts/zcode/openviking.integration.json@@ -1,7 +1,7 @@{"schemaVersion": 1,"id": "openviking-memory",- "version": "0.5.6",+ "version": "0.5.7","clients": ["zcode"],diff --git a/examples/agent-hook-plugin/plugin.json b/examples/agent-hook-plugin/plugin.jsonindex b50180e1c..422989d34 100644--- a/examples/agent-hook-plugin/plugin.json+++ b/examples/agent-hook-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "agent-hook-plugin",- "version": "0.5.6",+ "version": "0.5.7","description": "Long-term semantic memory for Cursor, TRAE, TRAE CN, ZCode and Kimi Code — powered by OpenViking. Auto-recall relevant memories and capture the conversation as it happens.","author": {"name": "OpenViking",diff --git a/examples/agent-hook-plugin/scripts/ov-memory-doctor.mjs b/examples/agent-hook-plugin/scripts/ov-memory-doctor.mjsindex d7a15f46e..dfa6d2767 100644--- a/examples/agent-hook-plugin/scripts/ov-memory-doctor.mjs+++ b/examples/agent-hook-plugin/scripts/ov-memory-doctor.mjs@@ -118,7 +118,7 @@ function checkInstall(report) {}const missing = REQUIRED_PLUGIN_FILES.filter((rel) => !existsPath(join(PLUGIN_ROOT, rel)));- if (missing.length) report.fail("plugin files missing", missing.join(", "), `curl -fsSL https://openviking.net/install | bash -s -- --harness ${CLIENT}`);+ if (missing.length) report.fail("plugin files missing", missing.join(", "), `curl -fsSL https://openviking.ai/install | bash -s -- --harness ${CLIENT}`);else report.ok("plugin files present (hook entry, URI guard, MCP proxy, host adapters)");// The runtime is not vendored: it sits beside the integration, assembled fromdiff --git a/examples/claude-code-memory-plugin/.claude-plugin/plugin.json b/examples/claude-code-memory-plugin/.claude-plugin/plugin.jsonindex c47ddcd21..ecbce1401 100644--- a/examples/claude-code-memory-plugin/.claude-plugin/plugin.json+++ b/examples/claude-code-memory-plugin/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "openviking-memory",- "version": "0.6.7",+ "version": "0.6.8","description": "Long-term semantic memory for Claude Code, powered by OpenViking. Auto-recall relevant memories at session start and capture important information during conversations.","author": {"name": "OpenViking",diff --git a/examples/claude-code-memory-plugin/README_CN.md b/examples/claude-code-memory-plugin/README_CN.mdindex d90a86b47..ed9dcd2fc 100644--- a/examples/claude-code-memory-plugin/README_CN.md+++ b/examples/claude-code-memory-plugin/README_CN.md@@ -9,7 +9,7 @@### 一行安装(推荐)```bash-curl -fsSL https://openviking.net/install | bash -s -- --harness claude+curl -fsSL https://openviking.ai/install | bash -s -- --harness claude# AI agent 如不确定是否执行,可先阅读脚本头部,其中写明了它会做什么、如何核实。```diff --git a/examples/claude-code-memory-plugin/package.json b/examples/claude-code-memory-plugin/package.jsonindex 52c7e6793..b57971f41 100644--- a/examples/claude-code-memory-plugin/package.json+++ b/examples/claude-code-memory-plugin/package.json@@ -1,6 +1,6 @@{"name": "claude-code-openviking-memory",- "version": "0.6.7",+ "version": "0.6.8","description": "OpenViking memory plugin for Claude Code — semantic long-term memory","type": "module","scripts": {diff --git a/examples/claude-code-memory-plugin/scripts/ov-memory-doctor.mjs b/examples/claude-code-memory-plugin/scripts/ov-memory-doctor.mjsindex b07a95115..5f5ec809a 100644--- a/examples/claude-code-memory-plugin/scripts/ov-memory-doctor.mjs+++ b/examples/claude-code-memory-plugin/scripts/ov-memory-doctor.mjs@@ -100,7 +100,7 @@ function checkInstall(report, { cliOnPath }) {const entries = Array.isArray(plugins[PLUGIN_ID]) ? plugins[PLUGIN_ID] : (plugins[PLUGIN_ID] ? [plugins[PLUGIN_ID]] : []);if (!entries.length) {report.fail(`${PLUGIN_ID} is not registered in installed_plugins.json`, ids.length ? `found instead: ${ids.join(", ")}` : "",- "curl -fsSL https://openviking.net/install | bash -s -- --harness claude");+ "curl -fsSL https://openviking.ai/install | bash -s -- --harness claude");} else {const entry = entries[0];installPath = entry.installPath || "";@@ -129,7 +129,7 @@ function checkInstall(report, { cliOnPath }) {const entry = known.data[MARKETPLACE];if (!entry) {report.fail(`marketplace '${MARKETPLACE}' is not registered`, `known: ${Object.keys(known.data).join(", ") || "(none)"}`,- "re-run the installer: curl -fsSL https://openviking.net/install | bash -s -- --harness claude");+ "re-run the installer: curl -fsSL https://openviking.ai/install | bash -s -- --harness claude");} else {const source = entry.source || {};const location = entry.installLocation || source.path || "";diff --git a/examples/claude-code-memory-plugin/skills/ov-memory-doctor/SKILL.md b/examples/claude-code-memory-plugin/skills/ov-memory-doctor/SKILL.mdindex 329d418e7..140de38f2 100644--- a/examples/claude-code-memory-plugin/skills/ov-memory-doctor/SKILL.md+++ b/examples/claude-code-memory-plugin/skills/ov-memory-doctor/SKILL.md@@ -75,7 +75,7 @@ Work top-down; fix the first ✗ and rerun before chasing the next.|---|---|---|| `plugin disabled — every hook exits immediately` | No parseable config, `OPENVIKING_MEMORY_ENABLED=0`, or `claude_code.enabled: false` in ov.conf | Fix the reason it names. Fresh machine: create `~/.openviking/ovcli.conf` with `url` + `api_key` (`chmod 600`). || `ovcli.conf cannot be parsed` | Trailing comma/comment; the plugin treats the file as absent | Fix the JSON. This is the most common "installed but nothing happens". |-| `not registered in installed_plugins.json` / `claude plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.net/install \| bash -s -- --harness claude`). |+| `not registered in installed_plugins.json` / `claude plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.ai/install \| bash -s -- --harness claude`). || `plugin is disabled in ~/.claude/settings.json` | Installed but `enabledPlugins` is false/missing | `claude plugin enable openviking-memory@openviking`, restart Claude Code. || `marketplace 'openviking' … missing directory` / registered as a file | The checkout/archive moved, or a file-type marketplace (fails `marketplace update` with EISDIR) | `claude plugin marketplace remove openviking` then re-run the installer. || `no skills/ directory in this plugin copy` / registered version behind the repo | Stale version-keyed cache; `claude plugin update` is a no-op when the version string did not change | `claude plugin marketplace update openviking && claude plugin uninstall openviking-memory@openviking && claude plugin install openviking-memory@openviking`. |diff --git a/examples/codex-memory-plugin/.codex-plugin/plugin.json b/examples/codex-memory-plugin/.codex-plugin/plugin.jsonindex c1d82dfe1..3b6a6daa4 100644--- a/examples/codex-memory-plugin/.codex-plugin/plugin.json+++ b/examples/codex-memory-plugin/.codex-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "openviking-memory",- "version": "0.10.8",+ "version": "0.10.9","description": "Long-term semantic memory for Codex, powered by OpenViking. Recall on UserPromptSubmit, incremental add_message on Stop (per turn), commit on SessionEnd (Codex >= 0.145) and on PreCompact, with an idle/ended sweep on SessionStart as the fallback for signals, crashes and older Codex builds. Includes a local stdio MCP proxy that reads OpenViking credentials from env/ovcli.conf.","author": {"name": "OpenViking",diff --git a/examples/codex-memory-plugin/scripts/ov-memory-doctor.mjs b/examples/codex-memory-plugin/scripts/ov-memory-doctor.mjsindex 8bf2fe07f..5cb778fff 100644--- a/examples/codex-memory-plugin/scripts/ov-memory-doctor.mjs+++ b/examples/codex-memory-plugin/scripts/ov-memory-doctor.mjs@@ -200,7 +200,7 @@ function checkInstall(report, { cliOnPath }) {const mine = rows.filter((r) => r?.pluginId === PLUGIN_ID);const others = rows.filter((r) => r?.pluginId !== PLUGIN_ID && r?.name === PLUGIN_NAME && r?.installed);if (!mine.length) report.fail(`codex plugin list does not show ${PLUGIN_ID}`, others.length ? `found: ${others.map((r) => r.pluginId).join(", ")}` : "",- "curl -fsSL https://openviking.net/install | bash -s -- --harness codex");+ "curl -fsSL https://openviking.ai/install | bash -s -- --harness codex");else {listed = mine[0];const path = listed.source?.path || "";diff --git a/examples/codex-memory-plugin/skills/ov-memory-doctor/SKILL.md b/examples/codex-memory-plugin/skills/ov-memory-doctor/SKILL.mdindex 1a1a99e7b..1e1ca5623 100644--- a/examples/codex-memory-plugin/skills/ov-memory-doctor/SKILL.md+++ b/examples/codex-memory-plugin/skills/ov-memory-doctor/SKILL.md@@ -78,7 +78,7 @@ Work top-down; fix the first ✗ and rerun before chasing the next.| Doctor finding | Meaning | Action ||---|---|---|| `ovcli.conf cannot be parsed` / `no usable config` | Trailing comma/comment; the plugin treats the file as absent and uses the localhost default | Fix the JSON. Fresh machine: create `~/.openviking/ovcli.conf` with `url` + `api_key`, `chmod 600`. |-| `codex plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.net/install \| bash -s -- --harness codex`). |+| `codex plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.ai/install \| bash -s -- --harness codex`). || `hooks disabled in [features]` / `hooks feature is disabled in Codex` | The applicable hooks feature is disabled | Set `hooks = true` under `[features]` in `~/.codex/config.toml` (or `plugin_hooks = true` for older Codex), restart Codex. || `[features] hooks enabled by default` | The live CLI reports hooks enabled; legacy `plugin_hooks` has no effect | Continue with the remaining checks. || `[features] hooks is not set` (info) | The CLI probe could not determine the modern feature state and no legacy flag decides it | Verify with `codex features list`; an unset key alone does not prove hooks are disabled. |diff --git a/examples/memory-plugin-shared/bootstrap.sh b/examples/memory-plugin-shared/bootstrap.shindex 883375d3e..cd31c9737 100755--- a/examples/memory-plugin-shared/bootstrap.sh+++ b/examples/memory-plugin-shared/bootstrap.sh@@ -15,7 +15,7 @@# it prints the same list and proceeds.## Install without prompts:-# curl -fsSL https://openviking.net/install | bash -s -- --yes --url <server-url> --api-key <key>+# curl -fsSL https://openviking.ai/install | bash -s -- --yes --url <server-url> --api-key <key># The server URL and API key come from the user; leave both out for a local# server at http://127.0.0.1:1933. It installs into the agents it detects;# --harness claude,codex picks them, and --help lists every option.@@ -29,7 +29,7 @@# this file in the repository: examples/memory-plugin-shared/bootstrap.sh# the installer: examples/memory-plugin-shared/install.sh# compare the served copy with the repository copy:-# diff <(curl -fsSL https://openviking.net/install) \+# diff <(curl -fsSL https://openviking.ai/install) \# <(curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/examples/memory-plugin-shared/bootstrap.sh)# star count today: gh api repos/volcengine/OpenViking --jq .stargazers_count# documentation: https://docs.openviking.net or https://docs.openviking.aidiff --git a/examples/memory-plugin-shared/install.sh b/examples/memory-plugin-shared/install.shindex 0242fa472..fedfd8e7a 100644--- a/examples/memory-plugin-shared/install.sh+++ b/examples/memory-plugin-shared/install.sh@@ -15,9 +15,9 @@# settings nothing is written outside $HOME except temporary files.## Install without prompts:-# curl -fsSL https://openviking.net/install | bash -s -- --yes --url <server-url> --api-key <api-key>-# (https://openviking.net/install is a short script that downloads this one and-# runs it; https://openviking.ai/install serves the same.)+# curl -fsSL https://openviking.ai/install | bash -s -- --yes --url <server-url> --api-key <api-key>+# (https://openviking.ai/install is a short script that downloads this one and+# runs it; https://openviking.net/install serves the same.)# The server URL and API key come from the user; without them it uses an# existing ~/.openviking/ovcli.conf, then http://127.0.0.1:1933 without a key.# It installs into the agents it detects (claude,codex when it detects none);@@ -81,7 +81,7 @@# published copy of this script.## Uninstall: Cursor, TRAE, TRAE CN, ZCode and Kimi Code with-# curl -fsSL https://openviking.net/install | bash -s -- --uninstall --yes --harness <list>+# curl -fsSL https://openviking.ai/install | bash -s -- --uninstall --yes --harness <list># The other harnesses with the commands the install prints at the end, such as# claude plugin uninstall openviking-memory@openviking && claude plugin marketplace remove openviking#