From a59ba10c8cf89646433bc03cc034d9e540e2d097 Mon Sep 17 00:00:00 2001 From: r266-tech Date: Wed, 13 May 2026 16:19:43 +0800 Subject: [PATCH 1/4] docs(bot): document ov_server.api_key_type field (#1994) --- bot/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bot/README.md b/bot/README.md index c20b42642..6d8a91350 100644 --- a/bot/README.md +++ b/bot/README.md @@ -173,6 +173,8 @@ All configurations are under the `bot` field in `ov.conf`, with default values f - If you don't use the locally started OpenViking Server, you can configure the url and the corresponding root user's API Key here - root_api_key: In a multi-tenant scenario, the API KEY must have root privileges; otherwise, the bot cannot automatically register multiple OpenViking users, which is used to implement memory isolation. - account_id: Defaults to default, which is the account ID of OpenViking. All users under an OpenViking account share resources. + - api_key_type: Optional `root` or `user`. Defaults to `root` (legacy fanout behavior: the bot uses the root key for all OpenViking calls and registers per-user accounts itself). Set to `user` to opt into the user-key flow: the bot bootstraps each user via the root key, then switches to that user's API key for subsequent calls. + - exp_write_tools: Optional list of tool names that trigger experience-memory injection before the call (self-evolving agent memory loop, see `agent` config). Defaults to `["write_file", "edit_file"]`. - `channels`: Message platform configuration, see [Message Platform Configuration](bot/docs/CHANNEL.md) for details ```json From c355510f57ff428b7e2ea31049a2c22c144dd828 Mon Sep 17 00:00:00 2001 From: r266-tech Date: Wed, 13 May 2026 16:19:52 +0800 Subject: [PATCH 2/4] docs(bot): document ov_server.api_key_type and exp_write_tools (#1994 + #2007) --- bot/README_CN.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bot/README_CN.md b/bot/README_CN.md index 47ac40a51..3f32981ae 100644 --- a/bot/README_CN.md +++ b/bot/README_CN.md @@ -176,6 +176,8 @@ bot将连接远程的OpenViking服务器，使用前需启动Openviking Server - 若不使用本地启动的OpenViking Server，可在此配置url和对应的root user的API Key - root_api_key: 多租户场景API KEY必须有root权限，否则bot无法自动注册多个OpenViking用户，用于实现memory的隔离 - account_id: 默认default，ov的账号ID，OpenViking account下所有user共享resources + - api_key_type: 可选 `root` 或 `user`，默认 `root`（旧 fanout 行为：bot 使用 root key 调用 OpenViking，并自动注册多用户）。设置为 `user` 切换到 user-key 流程：bot 仍用 root key 引导每个用户，但后续调用使用该用户的 API Key。 + - exp_write_tools: 可选，触发经验记忆注入的工具名列表（自演化 agent memory 循环，详见 `agent` 配置）。默认 `["write_file", "edit_file"]`。 - channels：消息平台配置，详见 [消息平台配置](bot/docs/CHANNEL.md) ```json From 62d3ce2a758d8bc24b5a240d9a9c9abf90bbfed2 Mon Sep 17 00:00:00 2001 From: r266-tech Date: Wed, 13 May 2026 16:21:42 +0800 Subject: [PATCH 3/4] docs(bot): tighten api_key_type wording + flag exp_write_tools gate (codex feedback) --- bot/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bot/README.md b/bot/README.md index 6d8a91350..b3305d2d4 100644 --- a/bot/README.md +++ b/bot/README.md @@ -173,8 +173,8 @@ All configurations are under the `bot` field in `ov.conf`, with default values f - If you don't use the locally started OpenViking Server, you can configure the url and the corresponding root user's API Key here - root_api_key: In a multi-tenant scenario, the API KEY must have root privileges; otherwise, the bot cannot automatically register multiple OpenViking users, which is used to implement memory isolation. - account_id: Defaults to default, which is the account ID of OpenViking. All users under an OpenViking account share resources. - - api_key_type: Optional `root` or `user`. Defaults to `root` (legacy fanout behavior: the bot uses the root key for all OpenViking calls and registers per-user accounts itself). Set to `user` to opt into the user-key flow: the bot bootstraps each user via the root key, then switches to that user's API key for subsequent calls. - - exp_write_tools: Optional list of tool names that trigger experience-memory injection before the call (self-evolving agent memory loop, see `agent` config). Defaults to `["write_file", "edit_file"]`. + - api_key_type: Optional `root` or `user`, default `root`. `root` keeps the original root-key fanout behavior; `user` switches the bot to the user-key flow for OpenViking client calls. See #1994 for the full client flow. + - exp_write_tools: Optional list of tool names that trigger experience-memory injection before the call (self-evolving agent memory loop, see #2007). Defaults to `["write_file", "edit_file"]`. Injection only fires when the OpenViking server has `memory.agent_memory_enabled` set; otherwise this list is harmless. - `channels`: Message platform configuration, see [Message Platform Configuration](bot/docs/CHANNEL.md) for details ```json From 404edcb2030865adc252bf48407454fc196a78a2 Mon Sep 17 00:00:00 2001 From: r266-tech Date: Wed, 13 May 2026 16:21:44 +0800 Subject: [PATCH 4/4] docs(bot): tighten api_key_type wording + flag exp_write_tools gate (codex feedback) --- bot/README_CN.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bot/README_CN.md b/bot/README_CN.md index 3f32981ae..704aead24 100644 --- a/bot/README_CN.md +++ b/bot/README_CN.md @@ -176,8 +176,8 @@ bot将连接远程的OpenViking服务器，使用前需启动Openviking Server - 若不使用本地启动的OpenViking Server，可在此配置url和对应的root user的API Key - root_api_key: 多租户场景API KEY必须有root权限，否则bot无法自动注册多个OpenViking用户，用于实现memory的隔离 - account_id: 默认default，ov的账号ID，OpenViking account下所有user共享resources - - api_key_type: 可选 `root` 或 `user`，默认 `root`（旧 fanout 行为：bot 使用 root key 调用 OpenViking，并自动注册多用户）。设置为 `user` 切换到 user-key 流程：bot 仍用 root key 引导每个用户，但后续调用使用该用户的 API Key。 - - exp_write_tools: 可选，触发经验记忆注入的工具名列表（自演化 agent memory 循环，详见 `agent` 配置）。默认 `["write_file", "edit_file"]`。 + - api_key_type: 可选 `root` 或 `user`，默认 `root`。`root` 保留原有的 root-key fanout 行为；`user` 切换 bot 走 user-key 流程调用 OpenViking 客户端。完整客户端流程详见 #1994。 + - exp_write_tools: 可选，触发经验记忆注入的工具名列表（自演化 agent memory 循环，详见 #2007）。默认 `["write_file", "edit_file"]`。注入仅在 OpenViking server 启用 `memory.agent_memory_enabled` 时生效，否则此列表无作用。 - channels：消息平台配置，详见 [消息平台配置](bot/docs/CHANNEL.md) ```json