Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Feishu channel not loading after upgrading to OpenClaw 2026.5.2 (openclaw-lark v2026.3.17) [2 comments, 2 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#77159•Fetched 2026-05-05 05:51:33
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
2
Author
lyh-github-97lyh-github-97
Participants
clawsweeper[bot]clawsweeper[bot]lyh-github-97lyh-github-97
Timeline (top)
commented ×2closed ×1mentioned ×1subscribed ×1

Root Cause

The openclaw-lark plugin manifest at ~/.openclaw/extensions/openclaw-lark/openclaw.plugin.json contains:

{
  "id": "openclaw-lark",
  "channels": ["feishu"],
  "skills": ["./skills"],
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  }
}

The manifest declares channels: ["feishu"] (declares it provides a feishu channel), but is missing the channelConfigs field required by OpenClaw 2026.5.2. Without channelConfigs, the OpenClaw gateway doesn't know what configuration fields the feishu channel requires, so channels.feishu in openclaw.json is ignored.

The actual configuration schema does exist in src/core/config-schema.js (Zod format with proper fields like dmPolicy, groupPolicy, allowFrom, etc.), but the manifest's configSchema is an empty object {} and does not reference it.

Fix Action

Fix / Workaround

Current Workaround

Code Example

channel plugin manifest declares feishu without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads (plugin=openclaw-lark)

---

{
  "id": "openclaw-lark",
  "channels": ["feishu"],
  "skills": ["./skills"],
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  }
}

---

channel plugin manifest declares feishu without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads (plugin=openclaw-lark, source=/Users/liyaohua/.openclaw/extensions/openclaw-lark/openclaw.plugin.json)
plugins.allow: plugin not found: feishu (stale config entry ignored; remove it from plugins config)
RAW_BUFFERClick to expand / collapse

Problem Description

After upgrading to OpenClaw 2026.5.2, the Feishu channel fails to load. The gateway log shows:

channel plugin manifest declares feishu without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads (plugin=openclaw-lark)

Environment

  • OpenClaw version: 2026.5.2 canary
  • openclaw-lark version: 2026.3.17
  • Channel: Feishu/Lark

Root Cause Analysis

The openclaw-lark plugin manifest at ~/.openclaw/extensions/openclaw-lark/openclaw.plugin.json contains:

{
  "id": "openclaw-lark",
  "channels": ["feishu"],
  "skills": ["./skills"],
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  }
}

The manifest declares channels: ["feishu"] (declares it provides a feishu channel), but is missing the channelConfigs field required by OpenClaw 2026.5.2. Without channelConfigs, the OpenClaw gateway doesn't know what configuration fields the feishu channel requires, so channels.feishu in openclaw.json is ignored.

The actual configuration schema does exist in src/core/config-schema.js (Zod format with proper fields like dmPolicy, groupPolicy, allowFrom, etc.), but the manifest's configSchema is an empty object {} and does not reference it.

Expected Behavior

The feishu channel should load and use the configuration from channels.feishu in openclaw.json.

Gateway Log (relevant excerpts)

channel plugin manifest declares feishu without channelConfigs metadata; add openclaw.plugin.json#channelConfigs so config schema and setup surfaces work before runtime loads (plugin=openclaw-lark, source=/Users/liyaohua/.openclaw/extensions/openclaw-lark/openclaw.plugin.json)
plugins.allow: plugin not found: feishu (stale config entry ignored; remove it from plugins config)

Current Workaround

None confirmed yet. Removing fields like dmPolicy, groupPolicy, allowFrom from channels.feishu clears config validation errors but does not enable the channel itself.

Question

Is the fix to add a properly formatted channelConfigs field to the openclaw-lark manifest? If so, what format should it use — JSON Schema inline, or a reference to the existing Zod schema in config-schema.js?

Reference: openclaw-lark plugin is at ~/.openclaw/extensions/openclaw-lark/

extent analysis

TL;DR

Add a channelConfigs field to the openclaw-lark plugin manifest, referencing the existing Zod schema in config-schema.js.

Guidance

  • Verify the config-schema.js file contains the correct configuration schema for the Feishu channel, including fields like dmPolicy, groupPolicy, and allowFrom.
  • Update the openclaw.plugin.json manifest to include a channelConfigs field, using a reference to the Zod schema in config-schema.js instead of an inline JSON Schema.
  • Ensure the channelConfigs field is properly formatted and references the correct schema, to enable the Feishu channel to load and use the configuration from channels.feishu in openclaw.json.
  • After updating the manifest, restart the OpenClaw gateway to apply the changes and verify the Feishu channel is loaded correctly.

Example

{
  "id": "openclaw-lark",
  "channels": ["feishu"],
  "skills": ["./skills"],
  "configSchema": {
    "type": "object",
    "additionalProperties": false,
    "properties": {}
  },
  "channelConfigs": {
    "feishu": "./config-schema.js"
  }
}

Note: The above example assumes the config-schema.js file exports the Zod schema as a default export.

Notes

The exact format of the channelConfigs field may depend on the specific requirements of OpenClaw 2026.5.2, so it's essential to consult the documentation or seek further guidance if the above example does not work as expected.

Recommendation

Apply the workaround by adding a channelConfigs field to the openclaw-lark plugin manifest, as this is the most likely fix for the issue. This approach allows the Feishu channel to load and use the correct configuration

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…
#LLM response#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

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

Back to top recommendations

TRENDING