openclaw - 💡(How to fix) Fix openclawwechat 插件安装被误拦截 [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#58660Fetched 2026-04-08 01:59:36
View on GitHub
Comments
1
Participants
1
Timeline
0
Reactions
0
Participants
RAW_BUFFERClick to expand / collapse

安装 openclawwechat 插件时,旧版本 openclaw-weixin 被误识别为需要更新,导致安装流程混乱。

问题描述

  1. 执行 Downloading openclawwechat… Extracting /tmp/openclaw-npm-pack-K5orSR/openclawwechat-1.3.2.tgz… Installing to /home/dpro/.openclaw/extensions/openclawwechat… openclawwechat already at 1.3.2. Restart the gateway to load plugins and hooks. 时,系统提示找不到 openclawwechat 安装记录
  2. 旧插件 (v1.0.3) 存在 SDK 兼容性问题:
  3. 执行 Resolving clawhub:openclawwechat… Downloading openclawwechat… Extracting /tmp/openclaw-npm-pack-mQliIp/openclawwechat-1.3.2.tgz… Downloading openclawwechat… Extracting /tmp/openclaw-hook-pack-WGgram/openclawwechat-1.3.2.tgz… 后,新插件安装成功,但旧插件目录仍残留,导致持续报错

建议

  • 插件安装时自动清理旧版本同名/类似名称的插件
  • 明确插件 ID 映射关系(openclaw-weixin → openclawwechat)
  • 提供插件迁移/升级指南

环境

  • OpenClaw: 2026.3.28
  • 旧插件:openclaw-weixin 1.0.3
  • 新插件:openclawwechat 1.3.2

extent analysis

TL;DR

Manually remove the old plugin directory to resolve the installation issue and prevent errors.

Guidance

  • Check the plugin installation directory (/home/dpro/.openclaw/extensions/) for any remaining old plugin files or directories, and remove them if necessary.
  • Verify the plugin ID mapping relationship between openclaw-weixin and openclawwechat to ensure smooth migration.
  • Consider creating a backup of the plugin directory before making any changes to prevent data loss.

Example

No code snippet is provided as it is not explicitly supported by the issue.

Notes

The issue seems to be related to the old plugin not being properly removed during the installation process, causing conflicts with the new plugin. Manually removing the old plugin directory should resolve the issue, but it is recommended to verify the plugin ID mapping relationship to prevent future issues.

Recommendation

Apply workaround: Manually remove the old plugin directory, as it is a straightforward solution to resolve the immediate issue. This will allow for a clean installation of the new plugin and prevent errors.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING