openclaw - 💡(How to fix) Fix [Bug]: directory peers list --channel openclaw-weixin prompts to install an already-installed plugin on 2026.4.29 [2 comments, 3 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#75770Fetched 2026-05-02 05:30:27
View on GitHub
Comments
2
Participants
3
Timeline
3
Reactions
2
Author
Timeline (top)
commented ×2closed ×1

On 2026.4.29, openclaw directory peers list --channel openclaw-weixin interactively prompts to install the openclaw-weixin plugin even though the plugin is installed, enabled, and actively running (verified via plugins list and channels status). Choosing the default "Download from npm" option would overwrite the existing install at ~/.openclaw/extensions/openclaw-weixin/.

Root Cause

On 2026.4.29, openclaw directory peers list --channel openclaw-weixin interactively prompts to install the openclaw-weixin plugin even though the plugin is installed, enabled, and actively running (verified via plugins list and channels status). Choosing the default "Download from npm" option would overwrite the existing install at ~/.openclaw/extensions/openclaw-weixin/.

Fix Action

Fix / Workaround

Minor for runtime (channel keeps working); meaningful as a footgun — picking the default option in the prompt would clobber the local plugin install (including any local manifest patches users have applied while waiting for upstream fixes).

Code Example

Install openclaw-weixin plugin?
│  ● Download from npm (@tencent-weixin/openclaw-weixin)
│  ○ Use local plugin path
│  ○ Skip for now

---

{
  "installRecords": {
    "openclaw-weixin": {
      "source": "npm",
      "spec": "@tencent-weixin/openclaw-weixin",
      "installPath": "~/.openclaw/extensions/openclaw-weixin",
      "version": "2.3.1",
      "resolvedSpec": "@tencent-weixin/[email protected]",
      "shasum": "a8d6e34b832954d485d7f9a64ede5892735b7891"
    }
  }
}
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

On 2026.4.29, openclaw directory peers list --channel openclaw-weixin interactively prompts to install the openclaw-weixin plugin even though the plugin is installed, enabled, and actively running (verified via plugins list and channels status). Choosing the default "Download from npm" option would overwrite the existing install at ~/.openclaw/extensions/openclaw-weixin/.

Steps to reproduce

  1. Install @tencent-weixin/[email protected] on OpenClaw 2026.4.29 (install record present at ~/.openclaw/plugins/installs.json#installRecords.openclaw-weixin with installPath, version, integrity).
  2. Confirm openclaw plugins list shows the row @tencent-weixin/openclaw-weixin | openclaw-weixin | openclaw | enabled | global:openclaw-weixin/index.ts | 2.3.1.
  3. Confirm openclaw channels status shows openclaw-weixin <account>: enabled, configured, running.
  4. Run openclaw directory peers list --channel openclaw-weixin.

Expected behavior

Either query the channel's contact directory using the already-loaded plugin, or fail with a directory-empty/not-yet-supported message. The behavior should at minimum be consistent with plugins list and channels status, both of which agree the plugin is installed.

Actual behavior

Interactive prompt is shown:

◆  Install openclaw-weixin plugin?
│  ● Download from npm (@tencent-weixin/openclaw-weixin)
│  ○ Use local plugin path
│  ○ Skip for now

The directory command path's install-detection disagrees with the plugins command path's install-detection on the same install.

OpenClaw version

2026.4.29 (a448042)

Operating system

Ubuntu 24.04 (Linux 6.8.0)

Install method

npm global

Model

openai-codex/gpt-5.5 (not relevant to this defect)

Provider / routing chain

openclaw -> openai-codex (not relevant to this defect)

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

Install record (sanitized):

{
  "installRecords": {
    "openclaw-weixin": {
      "source": "npm",
      "spec": "@tencent-weixin/openclaw-weixin",
      "installPath": "~/.openclaw/extensions/openclaw-weixin",
      "version": "2.3.1",
      "resolvedSpec": "@tencent-weixin/[email protected]",
      "shasum": "a8d6e34b832954d485d7f9a64ede5892735b7891"
    }
  }
}

Impact and severity

Minor for runtime (channel keeps working); meaningful as a footgun — picking the default option in the prompt would clobber the local plugin install (including any local manifest patches users have applied while waiting for upstream fixes).

Additional information

NOT_ENOUGH_INFO on whether earlier 2026.4.x releases exhibit the same behavior (was not exercised on 2026.4.26 prior to upgrade).

extent analysis

TL;DR

The openclaw directory peers list --channel openclaw-weixin command incorrectly prompts to install the openclaw-weixin plugin despite it being already installed and enabled.

Guidance

  • Verify the install record in ~/.openclaw/plugins/installs.json to ensure it matches the expected plugin installation details.
  • Check the openclaw plugins list and openclaw channels status outputs to confirm the plugin is installed, enabled, and running.
  • Consider using the "Use local plugin path" option in the interactive prompt to avoid overwriting the existing plugin installation.
  • Investigate potential inconsistencies in install-detection between the directory and plugins command paths.

Example

No code snippet is provided as the issue seems to be related to the OpenClaw plugin management and detection.

Notes

The issue might be specific to the OpenClaw version 2026.4.29, and it is unclear if earlier versions exhibit the same behavior.

Recommendation

Apply workaround: Use the "Use local plugin path" option in the interactive prompt to avoid overwriting the existing plugin installation, until the root cause of the install-detection inconsistency is resolved.

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…

FAQ

Expected behavior

Either query the channel's contact directory using the already-loaded plugin, or fail with a directory-empty/not-yet-supported message. The behavior should at minimum be consistent with plugins list and channels status, both of which agree the plugin is installed.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING