Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix plugins.allow auto-injects channel ID "feishu" when using openclaw-lark, causing spurious warning [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#77259•Fetched 2026-05-05 05:50:35
View on GitHub
Comments
2
Participants
3
Timeline
5
Reactions
2
Author
whuzhang753whuzhang753
Participants
clawsweeper[bot]clawsweeper[bot]vincentkocvincentkocwhuzhang753whuzhang753
Timeline (top)
commented ×2closed ×1mentioned ×1subscribed ×1

Root Cause

The built-in channel schema defines a channel with pluginId: "feishu" and channelId: "feishu". When the user has channels.feishu configured, Gateway resolves the channel's pluginId and adds it to plugins.allow. However, the actual installed plugin ID is openclaw-lark, not feishu.

The external plugin catalog also defines @openclaw/feishu (id: feishu), but when the user installs the third-party openclaw-lark instead, the auto-injected "feishu" has no matching plugin.

Fix Action

Workaround

Manually removing "feishu" from plugins.allow does not help — Gateway re-injects it on every restart.

RAW_BUFFERClick to expand / collapse

Bug Description

When using @larksuite/openclaw-lark as the Feishu/Lark channel plugin, Gateway auto-injects "feishu" into plugins.allow on startup. Since there is no installed plugin with ID "feishu" (only openclaw-lark), this triggers a persistent config warning:

plugins.allow: plugin not found: feishu (stale config entry ignored; remove it from plugins config)

Environment

  • OpenClaw: 2026.5.3-1
  • OS: Linux 6.6.87.2-microsoft-standard-WSL2 (x64)
  • Plugin: @larksuite/openclaw-lark v2026.4.8
  • Channel config key: channels.feishu

Root Cause

The built-in channel schema defines a channel with pluginId: "feishu" and channelId: "feishu". When the user has channels.feishu configured, Gateway resolves the channel's pluginId and adds it to plugins.allow. However, the actual installed plugin ID is openclaw-lark, not feishu.

The external plugin catalog also defines @openclaw/feishu (id: feishu), but when the user installs the third-party openclaw-lark instead, the auto-injected "feishu" has no matching plugin.

Steps to Reproduce

  1. Install openclaw-lark (not @openclaw/feishu)
  2. Configure channels.feishu
  3. Start Gateway
  4. Observe warning: plugin not found: feishu

Expected Behavior

Either:

  • Gateway should map the channel to the correct plugin ID (openclaw-lark) for plugins.allow injection, OR
  • The warning should recognize that the channel ID is satisfied by a different plugin and suppress the warning

Workaround

Manually removing "feishu" from plugins.allow does not help — Gateway re-injects it on every restart.

extent analysis

TL;DR

Update the channel configuration to use the correct plugin ID openclaw-lark instead of relying on the auto-injected feishu ID.

Guidance

  • Verify that the @larksuite/openclaw-lark plugin is correctly installed and configured.
  • Check the channel configuration to ensure that it is using the correct plugin ID openclaw-lark for the Feishu/Lark channel.
  • Consider updating the Gateway configuration to map the feishu channel to the openclaw-lark plugin ID to prevent auto-injection of the incorrect ID.
  • Review the external plugin catalog to ensure that the @openclaw/feishu plugin is not being used, as it may be causing conflicts with the openclaw-lark plugin.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue is specific to the @larksuite/openclaw-lark plugin and the Feishu/Lark channel configuration. The workaround provided in the issue does not work, so a more permanent solution is needed.

Recommendation

Apply a workaround by updating the channel configuration to use the correct plugin ID openclaw-lark instead of relying on the auto-injected feishu ID, as the root cause of the issue is the mismatch between the channel's plugin ID and the actual installed plugin ID.

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…
#index setup#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix plugins.allow auto-injects channel ID "feishu" when using openclaw-lark, causing spurious warning [2 comments, 3 participants]