[Tracking]: OpenClaw 插件使用问题汇总 / OpenClaw Plugin Usage Issues Tracker #969
Description
背景 / Background
社区最近陆续提交了多条与 OpenClaw 插件安装、加载、注册、auto-capture、memory extraction、contextEngine 集成 相关的问题。为了避免讨论分散，这里建立一个统一的 tracking issue，集中汇总当前已知问题、去重关系和后续跟踪入口。
The community has reported multiple issues related to OpenClaw plugin installation, loading, registration, auto-capture, memory extraction, and contextEngine integration. This tracking issue consolidates the known problems, deduplicates overlapping reports, and provides a single place to follow progress.
范围说明 / Scope
这个 issue 只跟踪 OpenClaw 插件使用层面的问题。
This issue tracks OpenClaw plugin usage problems only.
以下内容 不在本帖重复统计：
- Token 消耗、API 调用成本、Embedding 成本/分块策略：统一在
#744跟踪
The following are explicitly out of scope here:
- Token consumption, API cost, embedding cost/chunking strategy: tracked in
#744
补充说明：下表中的“当前状态 / Current Status”按 2026-03-25 的 issue 状态更新。
Note: the “Current Status” column below reflects issue state as of March 25, 2026.
分类一：安装、加载与版本兼容 / Category 1: Installation, Loading, and Version Compatibility
| Issue | 标题 / Title | 核心问题 / Core Problem | 当前状态 / Current Status |
|---|---|---|---|
| #945 | v0.2.10 plugin failed to load: Cannot find module './session-transcript-repair.js' | 插件安装后无法加载，模块路径解析失败 / Plugin installs but fails to load due to module resolution error | OPEN |
| #968 | Does the openclaw plugin no longer exist? Has it been replaced by skill? | 插件入口和产品形态是否变更不清晰 / Plugin entrypoint and product status are unclear | OPEN |
| #964 | gateway can't start because of openviking failure: health check timeout at http://127.0.0.1:1933 | 本地模式 health check 超时，导致 gateway 无法启动 / Local-mode health check timeout prevents gateway startup | OPEN |
| #935 | OpenClaw 2026.3.23-2 config reload skipped: plugins.slots: Unrecognized key: "contextEngine" | OpenClaw 版本兼容性问题，导致 contextEngine 配置失效 / Compatibility issue causing contextEngine config rejection |
CLOSED |
分类二：插件注册与生命周期 / Category 2: Registration and Lifecycle
| Issue | 标题 / Title | 核心问题 / Core Problem | 当前状态 / Current Status |
|---|---|---|---|
| #948 | openviking plugin registers repeatedly every minute | 插件重复注册，影响网关稳定性 / Plugin re-registers repeatedly, affecting gateway stability | OPEN |
| #680 | 启动openclaw插件后，就会一直 debug cron: timer armed，无法使用。 | 插件启动异常，用户无法正常使用 / Plugin startup/lifecycle failure blocks normal usage | OPEN |
| #512 | openclaw plugin installation overwrites existing plugin list configuration | 安装过程覆盖现有插件配置 / Installation overwrites existing plugin config | CLOSED |
分类三：记忆提取与 Auto-Capture / Category 3: Memory Extraction and Auto-Capture
| Issue | 标题 / Title | 核心问题 / Core Problem | 当前状态 / Current Status |
|---|---|---|---|
| #898 | OpenClaw plugin auto-capture may mis-capture <relevant-memories> injected context and intermittently fail with AbortError |
recall 注入内容污染 capture 输入，且伴随 AbortError / Injected recall context pollutes capture input and may trigger AbortError | OPEN |
| #811 | Embedding 队列错误导致 auto-capture 返回 0 memories | embedding 队列异常导致新记忆无法写入 / Embedding queue failures cause auto-capture to extract/store 0 memories | OPEN |
| #630 | OpenClaw + OpenViking Memory Extraction Issue (0 Memories Returned) | 跨服务器部署下提取返回 0 memories / Cross-server deployment returns 0 memories | OPEN |
| #455 | Openclaw插件工具调用始终返回 extract returned 0 memories. | 工具调用路径下记忆提取失败 / Memory extraction fails in tool-call path | OPEN |
| #911 | auto-capture completed but extract returned 0 memories / Access denied for viking://agent/.../memories | auto-capture 完成但检索/提取失败，可能涉及权限或 agent scope / Capture completes but retrieval/extraction fails, possibly due to permission or agent scope | OPEN |
分类四：ContextEngine 集成与压缩行为 / Category 4: ContextEngine Integration and Compaction Behavior
| Issue | 标题 / Title | 核心问题 / Core Problem | 当前状态 / Current Status |
|---|---|---|---|
| #833 | 安装启用openviking以后 传统的/compact命令就无法使用了吗？那我想要压缩上下文怎么办？ | 使用 OpenViking 作为 contextEngine 时，/compact 不可用 / /compact becomes unavailable when OpenViking is used as contextEngine |
OPEN |
| #901 | /compact command unavailable when using OpenViking as contextEngine | 与 #833 同类，已去重关闭 / Same problem as #833, already closed as duplicate |
CLOSED (duplicate of #833) |
| #698 | 当前 OpenClaw memory slot 设计下，OpenViking Plugin 和 memory-core 应该如何共存？ | plugin slot / contextEngine / memory slot 共存策略不清晰 / Coexistence strategy across plugin slots is unclear | CLOSED |
分类五：集成指引与使用认知 / Category 5: Integration Guidance and UX Clarity
| Issue | 标题 / Title | 核心问题 / Core Problem | 当前状态 / Current Status |
|---|---|---|---|
| #551 | openclaw无法集成openviking是吗？ | 集成入口和报错含义不清晰 / Integration path and error meaning are unclear | OPEN |
| #676 | How can I reproduce the OpenClaw Memory Plugin experiment? | 缺少插件实验/接入复现文档 / Missing reproduction and integration documentation | OPEN |
当前处理建议 / Proposed Tracking Use
-
与 安装/加载/注册 相关的新问题，请优先在这里补充环境和复现信息
-
与 auto-capture / memory extraction / contextEngine 集成 相关的新问题，请优先链接到对应子 issue；如果是同类现象但根因未明，也可以先在这里汇总
-
与 token/cost 相关的问题，请不要重复发在这里，统一转到
#744 -
For new installation/loading/registration problems, please add environment details and reproduction steps here first.
-
For auto-capture / memory extraction / contextEngine integration problems, prefer linking the relevant child issue; if the symptom matches but the root cause is unclear, this tracker can be used first.
-
For token/cost problems, please use
#744instead of duplicating them here.
备注 / Notes
这个 tracking issue 的目标是统一入口，不替代具体 bug issue。修复仍然会在对应子 issue / PR 中推进。
This tracker is intended as a single entrypoint and does not replace individual bug issues. Fixes should still be driven in the corresponding child issues / PRs.