@openviking/opencode-plugin 2026.9.9 → 2026.9.21-1

package/INSTALL-ZH.md

@@ -49,6 +49,7 @@ curl http://localhost:1933/health
 在仓库根目录执行：
 
 ```bash
+node examples/memory-plugin-shared/sync.mjs
 mkdir -p ~/.config/opencode/plugins/openviking
 cp examples/opencode-plugin/wrappers/openviking.js ~/.config/opencode/plugins/openviking.js
 cp examples/opencode-plugin/index.mjs examples/opencode-plugin/package.json ~/.config/opencode/plugins/openviking/
@@ -56,6 +57,8 @@ cp -r examples/opencode-plugin/lib ~/.config/opencode/plugins/openviking/
 cp -r examples/opencode-plugin/servers ~/.config/opencode/plugins/openviking/
 ```
 
+`sync.mjs` 会生成 `lib/shared/`，插件和 MCP 代理都从这里 import 共享模块。这个目录不在 git 里，所以复制前要先运行；之后每次 `git pull` 也要重新运行再复制。
+
 安装后结构应类似：
 
 ```text
@@ -81,37 +84,44 @@ export { OpenVikingPlugin, default } from "./openviking/index.mjs"
 
 ## 配置
 
-创建用户级配置文件：
+行为旋钮写在共享的客户端配置文件里：
 
 ```bash
-~/.config/opencode/openviking-config.json
+~/.openviking/ovcli.conf
 ```
 
 示例配置：
 
 ```json
 {
-  "enabled": true,
-  "mcp": { "enabled": true },
-  "timeoutMs": 30000,
-  "repoContext": { "enabled": true, "cacheTtlMs": 60000 },
-  "autoRecall": {
-    "enabled": true,
-    "limit": 6,
-    "scoreThreshold": 0.35,
-    "maxContentChars": 500,
-    "preferAbstract": true,
-    "tokenBudget": 2000,
-    "minQueryLength": 3
-  },
-  "commitTokenThreshold": 20000,
-  "commitKeepRecentCount": 10,
-  "profileTokenBudget": 10000,
-  "resumeContextBudget": 32000
+  "url": "http://127.0.0.1:1933",
+  "api_key": "your-api-key-here",
+  "plugin": {
+    "recallLimit": 6,
+    "opencode": {
+      "enabled": true,
+      "mcpEnabled": true,
+      "timeoutMs": 30000,
+      "repoContext": true,
+      "repoContextCacheTtlMs": 60000,
+      "autoRecall": true,
+      "scoreThreshold": 0.35,
+      "recallMaxContentChars": 500,
+      "recallPreferAbstract": true,
+      "recallTokenBudget": 2000,
+      "minQueryLength": 3,
+      "commitTokenThreshold": 20000,
+      "commitKeepRecentCount": 10,
+      "profileTokenBudget": 10000,
+      "resumeContextBudget": 32000
+    }
+  }
 }
 ```
 
-`autoRecall.limit` 是遗留的配额缩放输入，不是最终结果上限。显式设置为
+`plugin` 里的键对所有 harness 生效；`plugin.opencode` 里的键只对本插件生效，并覆盖前者。解析顺序是 `OPENVIKING_*` 环境变量 → 工作区的 `.openviking/config.json`、`.openviking/config.local.json` 和本机 registry 条目 → `plugin.opencode` → `plugin` → 内置默认值。每个旋钮的类型、默认值、取值范围、环境变量名和兼容的旧拼写都声明在 [`examples/memory-plugin-shared/lib/config-schema.mjs`](../memory-plugin-shared/lib/config-schema.mjs)。
+
+`recallLimit` 是遗留的配额缩放输入，不是最终结果上限。显式设置为
 1 到 5 时，有效总配额仍为 6，因为六个 coding 分类会各保留一个检索槽位。
 
 推荐通过环境变量提供 API Key，而不是写入配置文件：
@@ -121,15 +131,15 @@ export OPENVIKING_API_KEY="your-api-key-here"
 ```
 
 API key 会从环境变量或 `~/.openviking/ovcli.conf` 读取，并由 hooks 和 MCP proxy 作为 `Authorization: Bearer ...` 发送。`account` 和 `user` 是 trusted mode
-身份头，会作为 `X-OpenViking-Account`、`X-OpenViking-User` 发送；使用
-user/admin API key 的 API_KEY mode 时应留空。
+身份头，会作为 `X-OpenViking-Account`、`X-OpenViking-User` 发送；`api_key`
+模式的服务端从 key 里取身份，插件在那里不发这两个头。
 `peerId` 会作为 `X-OpenViking-Actor-Peer` 用于数据面的 memory/resource 请求；捕获 session message 时仍写入 body `peer_id`。需要 peer 维度路由时请显式配置。
 
 `OPENVIKING_API_KEY`、`OPENVIKING_ACCOUNT`、`OPENVIKING_USER`、
 `OPENVIKING_PEER_ID`
-优先级高于 `openviking-config.json` 里的同名配置。
+优先级高于 `ovcli.conf` 里的同名配置。
 
-高级场景可以用 `OPENVIKING_PLUGIN_CONFIG` 指向其他配置文件路径。
+高级场景可以用 `OPENVIKING_CLI_CONFIG_FILE` 指向其他路径的 `ovcli.conf`。
 
 ### 仅 Hooks 模式
 
@@ -137,7 +147,9 @@ user/admin API key 的 API_KEY mode 时应留空。
 
 ```json
 {
-  "mcp": { "enabled": false }
+  "plugin": {
+    "opencode": { "mcpEnabled": false }
+  }
 }
 ```
 
@@ -197,6 +209,7 @@ curl http://localhost:1933/health
 - 探索目录结构用 `openviking_list`
 - 删除前必须先获得用户明确确认，再调用 `openviking_forget`
 - 如果 agent 误用 OpenCode 本地 `read`、`glob`、`grep` 工具访问 `viking://` URI，插件会阻止这次本地文件系统调用，并提示改用 MCP 工具。
+- `bash` 命令里带 `viking://` URI 时照常执行，插件会在输出末尾附一段提示，建议改用 MCP 工具；URI 本来就是命令参数时，agent 可以忽略这段提示。
 
 ## `openviking_add_resource` 本地文件
 
@@ -229,7 +242,7 @@ openviking_add_resource(path="file:///home/alice/project/notes.md", description=
 - `openviking-memory.log`
 - `openviking-session-state.json`
 
-可以通过配置里的 `runtime.dataDir` 修改这个目录。
+可以通过 `plugin.opencode` 里的 `dataDir` 修改这个目录。
 
 这些是本地运行时文件，不建议提交到版本库。
 
@@ -238,7 +251,8 @@ openviking_add_resource(path="file:///home/alice/project/notes.md", description=
 | 问题 | 排查方向 |
 |------|----------|
 | 插件没有加载 | package 安装检查 `~/.config/opencode/opencode.json` 是否包含 `@openviking/opencode-plugin`；源码安装检查 `~/.config/opencode/plugins/openviking.js` 是否存在 |
-| MCP tools 连到了错误的 server | 检查 `~/.openviking/ovcli.conf`，或用 `OPENVIKING_*` 环境变量 / `OPENVIKING_PLUGIN_CONFIG` 指向正确配置 |
+| 加载时报找不到 `lib/shared/*.mjs` | 源码复制前没有运行 `sync.mjs`。在仓库根目录运行 `node examples/memory-plugin-shared/sync.mjs` 后重新复制 `lib/` |
+| MCP tools 连到了错误的 server | 检查 `~/.openviking/ovcli.conf`，或用 `OPENVIKING_*` 环境变量 / `OPENVIKING_CLI_CONFIG_FILE` 指向正确配置 |
 | OpenViking 返回 401 / 403 | 检查 `OPENVIKING_API_KEY`；trusted-mode 部署还要检查 `OPENVIKING_ACCOUNT` 和 `OPENVIKING_USER` |
-| recall 为空 | 确认 OpenViking 中已有 memories/resources，并且 `autoRecall.enabled` 为 `true` |
+| recall 为空 | 确认 OpenViking 中已有 memories/resources，并且 `autoRecall` 为 `true` |
 | 本地 `openviking_add_resource` 失败 | 传入文件路径而不是目录；目前还不支持自动上传本地目录 |

package/INSTALL.md

@@ -49,6 +49,7 @@ Use this method for development, debugging, or PR testing. OpenCode's recommende
 Run the following commands from the repository root:
 
 ```bash
+node examples/memory-plugin-shared/sync.mjs
 mkdir -p ~/.config/opencode/plugins/openviking
 cp examples/opencode-plugin/wrappers/openviking.js ~/.config/opencode/plugins/openviking.js
 cp examples/opencode-plugin/index.mjs examples/opencode-plugin/package.json ~/.config/opencode/plugins/openviking/
@@ -56,6 +57,8 @@ cp -r examples/opencode-plugin/lib ~/.config/opencode/plugins/openviking/
 cp -r examples/opencode-plugin/servers ~/.config/opencode/plugins/openviking/
 ```
 
+`sync.mjs` generates `lib/shared/`, the shared modules the plugin and its MCP proxy import. That directory is not in git, so run it before copying, and again after every `git pull`.
+
 After installation, the layout should look like this:
 
 ```text
@@ -81,37 +84,44 @@ If you install through an npm package, you can also use `examples/opencode-plugi
 
 ## Configuration
 
-Create the user-level configuration file:
+Behaviour knobs live in the shared client configuration file:
 
 ```bash
-~/.config/opencode/openviking-config.json
+~/.openviking/ovcli.conf
 ```
 
 Example configuration:
 
 ```json
 {
-  "enabled": true,
-  "mcp": { "enabled": true },
-  "timeoutMs": 30000,
-  "repoContext": { "enabled": true, "cacheTtlMs": 60000 },
-  "autoRecall": {
-    "enabled": true,
-    "limit": 6,
-    "scoreThreshold": 0.35,
-    "maxContentChars": 500,
-    "preferAbstract": true,
-    "tokenBudget": 2000,
-    "minQueryLength": 3
-  },
-  "commitTokenThreshold": 20000,
-  "commitKeepRecentCount": 10,
-  "profileTokenBudget": 10000,
-  "resumeContextBudget": 32000
+  "url": "http://127.0.0.1:1933",
+  "api_key": "your-api-key-here",
+  "plugin": {
+    "recallLimit": 6,
+    "opencode": {
+      "enabled": true,
+      "mcpEnabled": true,
+      "timeoutMs": 30000,
+      "repoContext": true,
+      "repoContextCacheTtlMs": 60000,
+      "autoRecall": true,
+      "scoreThreshold": 0.35,
+      "recallMaxContentChars": 500,
+      "recallPreferAbstract": true,
+      "recallTokenBudget": 2000,
+      "minQueryLength": 3,
+      "commitTokenThreshold": 20000,
+      "commitKeepRecentCount": 10,
+      "profileTokenBudget": 10000,
+      "resumeContextBudget": 32000
+    }
+  }
 }
 ```
 
-`autoRecall.limit` is a legacy quota-scaling input, not a final result cap.
+Keys in `plugin` apply to every harness; keys in `plugin.opencode` apply to this one and override them. Resolution is `OPENVIKING_*` environment variables → the workspace's `.openviking/config.json`, `.openviking/config.local.json` and machine registry entry → `plugin.opencode` → `plugin` → built-in defaults. Every knob, with its type, default, range, environment variable and accepted older spellings, is declared in [`examples/memory-plugin-shared/lib/config-schema.mjs`](../memory-plugin-shared/lib/config-schema.mjs).
+
+`recallLimit` is a legacy quota-scaling input, not a final result cap.
 Explicit values from 1 through 5 produce an effective total quota of 6 because
 each coding category keeps one retrieval slot.
 
@@ -121,11 +131,11 @@ It is recommended to provide the API key through an environment variable instead
 export OPENVIKING_API_KEY="your-api-key-here"
 ```
 
-API keys are resolved from environment variables or `~/.openviking/ovcli.conf` and sent as `Authorization: Bearer ...` by both hooks and the MCP proxy. `account` and `user` are trusted-mode identity headers sent as `X-OpenViking-Account` and `X-OpenViking-User`; leave them empty when using API-key mode with user/admin API keys. `peerId` is sent as `X-OpenViking-Actor-Peer` on data-plane memory/resource requests; captured session messages store it as body `peer_id`.
+API keys are resolved from environment variables or `~/.openviking/ovcli.conf` and sent as `Authorization: Bearer ...` by both hooks and the MCP proxy. `account` and `user` are trusted-mode identity headers sent as `X-OpenViking-Account` and `X-OpenViking-User`; an `api_key` server reads both out of the key, so the plugin withholds them there. `peerId` is sent as `X-OpenViking-Actor-Peer` on data-plane memory/resource requests; captured session messages store it as body `peer_id`.
 
-`OPENVIKING_API_KEY`, `OPENVIKING_ACCOUNT`, `OPENVIKING_USER`, and `OPENVIKING_PEER_ID` take precedence over the corresponding values in `openviking-config.json`.
+`OPENVIKING_API_KEY`, `OPENVIKING_ACCOUNT`, `OPENVIKING_USER`, and `OPENVIKING_PEER_ID` take precedence over the corresponding values in `ovcli.conf`.
 
-For advanced setups, use `OPENVIKING_PLUGIN_CONFIG` to point to another configuration file path.
+For advanced setups, use `OPENVIKING_CLI_CONFIG_FILE` to point to an `ovcli.conf` at another path.
 
 ### Hook-only mode
 
@@ -134,7 +144,9 @@ keeping this plugin's lifecycle hooks active:
 
 ```json
 {
-  "mcp": { "enabled": false }
+  "plugin": {
+    "opencode": { "mcpEnabled": false }
+  }
 }
 ```
 
@@ -194,6 +206,7 @@ Usage guidance:
 - Use `openviking_list` to explore directory structure.
 - Before deleting anything, obtain explicit user confirmation first; then call `openviking_forget`.
 - If an agent tries to use OpenCode's local `read`, `glob`, or `grep` tools on a `viking://` URI, the plugin blocks that call and points it to the MCP tools.
+- A `bash` command that contains a `viking://` URI still runs; the plugin appends a notice pointing to the MCP tools to its output, which the agent can ignore when the URI is intentional.
 
 ## Local Files with `openviking_add_resource`
 
@@ -226,7 +239,7 @@ Possible files include:
 - `openviking-memory.log`
 - `openviking-session-state.json`
 
-You can change this directory with `runtime.dataDir` in the configuration.
+You can change this directory with `dataDir` in `plugin.opencode`.
 
 These are local runtime files and should not be committed to the repository.
 
@@ -235,7 +248,8 @@ These are local runtime files and should not be committed to the repository.
 | Issue | What to check |
 |-------|---------------|
 | Plugin does not load | For package installs, confirm `~/.config/opencode/opencode.json` contains `@openviking/opencode-plugin`; for source installs, confirm `~/.config/opencode/plugins/openviking.js` exists |
-| MCP tools call the wrong server | Check `~/.openviking/ovcli.conf`, or set `OPENVIKING_*` env vars / `OPENVIKING_PLUGIN_CONFIG` to the intended config path |
+| Load fails with a missing `lib/shared/*.mjs` module | The source copy was made without running `sync.mjs` first. Run `node examples/memory-plugin-shared/sync.mjs` from the repository root and copy `lib/` again |
+| MCP tools call the wrong server | Check `~/.openviking/ovcli.conf`, or set `OPENVIKING_*` env vars / `OPENVIKING_CLI_CONFIG_FILE` to the intended config path |
 | 401 / 403 from OpenViking | Verify `OPENVIKING_API_KEY`; for trusted-mode deployments, also verify `OPENVIKING_ACCOUNT` and `OPENVIKING_USER` |
-| Recall is empty | Confirm OpenViking has indexed memories/resources and `autoRecall.enabled` is `true` |
+| Recall is empty | Confirm OpenViking has indexed memories/resources and `autoRecall` is `true` |
 | Local `openviking_add_resource` fails | Pass a file path, not a directory; local directories are not uploaded automatically yet |

package/README.md

@@ -18,7 +18,7 @@ The plugin uses OpenCode hooks for lifecycle behavior and registers OpenViking's
 - Captures user and assistant text messages into OpenViking.
 - Commits sessions at lifecycle boundaries for memory extraction.
 - Automatically recalls relevant memories and injects them as hidden synthetic context for the current user message.
-- Blocks accidental local filesystem reads of `viking://` URIs and points the agent back to `openviking_read`, `openviking_glob`, or `openviking_search`.
+- Blocks accidental local filesystem reads of `viking://` URIs and points the agent back to `openviking_read`, `openviking_glob`, or `openviking_search`. Shell commands that carry a `viking://` URI still run, with a notice appended to their output.
 
 ## Files
 
@@ -83,6 +83,7 @@ npm view @openviking/opencode-plugin version
 For development or PR testing, copy the package into OpenCode's plugin directory with a top-level wrapper:
 
 ```bash
+node examples/memory-plugin-shared/sync.mjs
 mkdir -p ~/.config/opencode/plugins/openviking
 cp examples/opencode-plugin/wrappers/openviking.js ~/.config/opencode/plugins/openviking.js
 cp examples/opencode-plugin/index.mjs examples/opencode-plugin/package.json ~/.config/opencode/plugins/openviking/
@@ -90,6 +91,8 @@ cp -r examples/opencode-plugin/lib ~/.config/opencode/plugins/openviking/
 cp -r examples/opencode-plugin/servers ~/.config/opencode/plugins/openviking/
 ```
 
+`sync.mjs` generates `lib/shared/`, the shared modules the plugin and its MCP proxy import. That directory is not in git, so run it before copying, and again after every `git pull`.
+
 This creates a stable OpenCode plugin layout:
 
 ```text
@@ -113,39 +116,46 @@ Use the `.js` wrapper for source installs; OpenCode's local plugin scanner disco
 
 ## Configuration
 
-Create `~/.config/opencode/openviking-config.json`:
+Behaviour knobs live in `~/.openviking/ovcli.conf` beside the connection fields, in the shared `plugin` section or in the `plugin.opencode` override:
 
 ```json
 {
-  "enabled": true,
-  "mcp": { "enabled": true },
-  "timeoutMs": 30000,
-  "repoContext": { "enabled": true, "cacheTtlMs": 60000 },
-  "autoRecall": {
-    "enabled": true,
-    "limit": 6,
-    "scoreThreshold": 0.35,
-    "maxContentChars": 500,
-    "preferAbstract": true,
-    "tokenBudget": 2000,
-    "minQueryLength": 3
-  },
-  "commitTokenThreshold": 20000,
-  "commitKeepRecentCount": 10,
-  "profileTokenBudget": 10000,
-  "resumeContextBudget": 32000
+  "url": "http://127.0.0.1:1933",
+  "api_key": "your-api-key-here",
+  "plugin": {
+    "recallLimit": 6,
+    "opencode": {
+      "enabled": true,
+      "mcpEnabled": true,
+      "timeoutMs": 30000,
+      "repoContext": true,
+      "repoContextCacheTtlMs": 60000,
+      "autoRecall": true,
+      "scoreThreshold": 0.35,
+      "recallMaxContentChars": 500,
+      "recallPreferAbstract": true,
+      "recallTokenBudget": 2000,
+      "minQueryLength": 3,
+      "commitTokenThreshold": 20000,
+      "commitKeepRecentCount": 10,
+      "profileTokenBudget": 10000,
+      "resumeContextBudget": 32000
+    }
+  }
 }
 ```
 
-`autoRecall.limit` is a legacy quota-scaling input, not a final result cap.
+Keys in `plugin` apply to every harness; keys in `plugin.opencode` apply to this one and override them. Resolution is `OPENVIKING_*` environment variables → the workspace's `.openviking/config.json`, `.openviking/config.local.json` and machine registry entry → `plugin.opencode` → `plugin` → built-in defaults. Every knob, with its type, default, range, environment variable and accepted older spellings, is declared in [`examples/memory-plugin-shared/lib/config-schema.mjs`](../memory-plugin-shared/lib/config-schema.mjs).
+
+`recallLimit` is a legacy quota-scaling input, not a final result cap.
 Explicit values from 1 through 5 produce an effective total quota of 6 because
 each coding category keeps one retrieval slot. Use Context `quotas` directly
 when exact category ceilings are required.
 
 API keys are resolved from environment variables or `~/.openviking/ovcli.conf` and sent as `Authorization: Bearer ...` by both hooks and the MCP proxy. Recall goes through the server-side context face (`POST /api/v1/search/search` with `mode="context"`), falling back to the deprecated `/api/v1/search/recall` on older deployments. `account` and `user` are trusted-mode identity
-headers sent as `X-OpenViking-Account` and `X-OpenViking-User`; leave them empty
-when using API-key mode with user/admin API keys.
-By default the plugin derives a peer from the git identity of the project directory: the normalized `origin` URL, else the repository root path. 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`. `git@github.com:volcengine/OpenViking.git` becomes `github.com-volcengine-openviking`; the path fallback keeps the older naming rule where every non-letter-or-digit character becomes `-`, so `/Users/x/Dev/OpenViking` becomes `-Users-x-Dev-OpenViking`. One repository therefore keeps one peer across subdirectories, worktrees, clones and machines, while a fork's different origin keeps it separate. Derivation reads `.git` directly, so no `git` binary is needed. The plugin does not read workspace `.openviking/config.json` files, so a `peer.id` written there has no effect. Data-plane memory/resource requests send the effective peer as `X-OpenViking-Actor-Peer`; captured session messages store it as body `peer_id`. Configure `peerId` or `OPENVIKING_PEER_ID` to override the derived peer, or set `workspacePeer=false` / `OPENVIKING_WORKSPACE_PEER=0` to send no peer at all. Memories written under the older directory-derived peer stay reachable: the default broad recall sweeps every peer under the user, and `recallPeerScope="actor"` asks that previous peer separately.
+headers sent as `X-OpenViking-Account` and `X-OpenViking-User`; an `api_key`
+server reads both out of the key, so the plugin withholds them there.
+By default the plugin derives a peer from the git identity of the project directory: the normalized `origin` URL, else the repository root path. 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`. `git@github.com:volcengine/OpenViking.git` becomes `github.com-volcengine-openviking`; the path fallback keeps the older naming rule where every non-letter-or-digit character becomes `-`, so `/Users/x/Dev/OpenViking` becomes `-Users-x-Dev-OpenViking`. One repository therefore keeps one peer across subdirectories, worktrees, clones and machines, while a fork's different origin keeps it separate. Derivation reads `.git` directly, so no `git` binary is needed. The plugin reads the workspace's `.openviking/config.json`, so a `peer.id` or `peer.source` written there applies. Data-plane memory/resource requests send the effective peer as `X-OpenViking-Actor-Peer`; captured session messages store it as body `peer_id`. Configure `peerId` in the `plugin` section or `OPENVIKING_PEER_ID` to override the derived peer, or set `workspacePeer` to `false` / `OPENVIKING_WORKSPACE_PEER=0` to send no peer at all. Memories written under the older directory-derived peer stay reachable: the default broad recall sweeps every peer under the user, and `recallPeerScope="actor"` asks that previous peer separately.
 
 Recall defaults to the broad mode: global memory, the current workspace, and
 other workspace memories can all be recalled, with other workspaces penalized
@@ -157,13 +167,12 @@ with an explicit actor peer so one person's memories are not recalled into
 another person's session.
 
 `OPENVIKING_API_KEY`, `OPENVIKING_ACCOUNT`, `OPENVIKING_USER`,
-and `OPENVIKING_PEER_ID` take precedence over values in this file. The config
-file's `peerId` still applies whenever shared credentials (ovcli.conf or
-environment variables) do not carry a peer of their own, so an authenticated
-setup keeps writing peer-scoped data instead of dropping into the shared user
-tree.
+and `OPENVIKING_PEER_ID` take precedence over `ovcli.conf`. Below the
+environment, the `plugin` section's `peerId` takes precedence over
+`ovcli.conf`'s `actor_peer_id`: a peer written for this harness is the more
+specific answer, and this is the order every memory plugin follows.
 
-For advanced setups, `OPENVIKING_PLUGIN_CONFIG` can point to another config file path.
+`OPENVIKING_CLI_CONFIG_FILE` points the plugin at an `ovcli.conf` somewhere other than `~/.openviking/ovcli.conf`.
 
 ### Hook-only mode
 
@@ -172,7 +181,9 @@ skipping this plugin's bundled MCP registration:
 
 ```json
 {
-  "mcp": { "enabled": false }
+  "plugin": {
+    "opencode": { "mcpEnabled": false }
+  }
 }
 ```
 
@@ -181,7 +192,10 @@ It does not add or overwrite OpenCode's `mcp.openviking` entry.
 
 OpenCode's local `read`, `glob`, and `grep` tools cannot read `viking://` URIs.
 When the agent accidentally tries that, the plugin blocks the filesystem tool
-call and points it to the OpenViking MCP tools.
+call and points it to the OpenViking MCP tools. A `bash` command that contains a
+`viking://` URI is not blocked, because the URI is often data (an `ov` argument,
+an HTTP payload); the command runs and the plugin appends a notice naming the
+MCP tools to its output.
 
 ## MCP Tools
 
@@ -211,12 +225,12 @@ The plugin writes runtime files to `~/.config/opencode/openviking/` by default:
 - `openviking-memory.log`
 - `openviking-session-state.json`
 
-Set `runtime.dataDir` in config to override this directory.
+Set `dataDir` in `plugin.opencode` to override this directory.
 
 ## Automated npm releases
 
 Changes merged into upstream `main` under `examples/opencode-plugin/` trigger
-`.github/workflows/opencode-plugin-release.yml`. Releases use the same calendar
+`.github/workflows/plugin-npm-release.yml`. Releases use the same calendar
 version convention as the OpenClaw plugin: `YYYY.M.D`, then `YYYY.M.D-N` for
 subsequent releases on that date (Asia/Shanghai). No manual source version bump
 is required. The workflow changes the version only in the package being published;

package/index.mjs

@@ -5,9 +5,10 @@ import { createRepoContext } from "./lib/repo-context.mjs"
 import { createMemorySessionManager } from "./lib/memory-session.mjs"
 import { createMemoryRecall } from "./lib/memory-recall.mjs"
 import { createSessionInject } from "./lib/session-inject.mjs"
-import { createVikingUriGuard } from "./lib/viking-uri-guard.mjs"
+import { createVikingUriGuard, createVikingUriNotice } from "./lib/viking-uri-guard.mjs"
 import { injectOpenVikingMcpConfig } from "./lib/mcp-config.mjs"
 import { loadConfig, resolveDataDir } from "./lib/config.mjs"
+import { isRecallEnabled } from "./lib/shared/recall-core.mjs"
 import { initLogger, log, makeToast } from "./lib/utils.mjs"
 
 const pluginRoot = dirname(fileURLToPath(import.meta.url))
@@ -27,16 +28,10 @@ export async function OpenVikingPlugin({ client, directory }) {
   const recall = createMemoryRecall({ config, sessionManager })
   const sessionInject = createSessionInject({ config, sessionManager })
   const vikingUriGuard = createVikingUriGuard()
+  const vikingUriNotice = createVikingUriNotice()
 
   await sessionManager.init()
   const toast = makeToast(client)
-  if (config.legacyCredentialsUsed) {
-    log("WARN", "config", "Legacy OpenCode credential fields are still in use; run node scripts/setup.mjs to migrate to ovcli.conf", {
-      configPath: config.configPath,
-    })
-    await toast("OpenViking credentials in openviking-config.json are deprecated. Run node scripts/setup.mjs to migrate.", "warning")
-  }
-
   Promise.resolve().then(async () => {
     const ready = await initializeRuntime(config, client)
     if (ready) await repoContext.refreshRepos({ force: true })
@@ -63,6 +58,7 @@ export async function OpenVikingPlugin({ client, directory }) {
     },
 
     "tool.execute.before": vikingUriGuard,
+    "tool.execute.after": vikingUriNotice,
 
     "experimental.chat.system.transform": (_input, output) => {
       const prompt = repoContext.getRepoSystemPrompt()
@@ -72,7 +68,7 @@ export async function OpenVikingPlugin({ client, directory }) {
     "chat.message": async (input, output) => {
       try {
         await sessionInject.injectSessionContext(input, output)
-        if (!config.autoRecall?.enabled) return
+        if (!isRecallEnabled(config)) return
         await recall.injectRelevantMemories(input, output)
       } catch (error) {
         log("WARN", "recall", "Auto recall failed", { error: error?.message ?? String(error) })