Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix config patch rejects openclaw-lark plugin extension fields (replyMode, footer) [1 pull requests, 1 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#77887•Fetched 2026-05-06 06:19:44
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Author
Simon2256928Simon2256928
Participants
clawsweeper[bot]clawsweeper[bot]Simon2256928Simon2256928
Timeline (top)
commented ×1cross-referenced ×1mentioned ×1subscribed ×1

openclaw config patch and openclaw config apply reject valid openclaw-lark plugin configuration fields with additionalProperties: false validation errors:

config schema validation failed.
- channels.feishu: invalid config: must NOT have additional properties: "replyMode"
- channels.feishu: invalid config: must NOT have additional properties: "footer"

However, both replyMode and footer are valid configuration fields defined in the openclaw-lark plugin's own Zod schema (src/core/config-schema.js). The plugin correctly reads and uses these fields at runtime.

Error Message

openclaw config patch should accept plugin extension fields in channel config, or at minimum warn instead of rejecting.

Root Cause

The built-in channels.feishu JSON schema (config.schema.lookup channels.feishu) has additionalProperties: false, which rejects any fields not in the built-in schema. But when a plugin like openclaw-lark extends the channel configuration with its own fields, those extension fields should be accepted.

Fix Action

Workaround

Manually editing openclaw.json with python3/jq bypasses the CLI validation, and the fields work correctly at runtime.

PR fix notes

PR #77914: fix(config): skip root-level additionalProperties errors from bundled channel validation for plugin extension fields

Description (problem / solution / changelog)

Problem

Closes #77887.

When a user has both the feishu channel enabled and the openclaw-lark plugin installed, running openclaw config patch fails with:

invalid config: must NOT have additional properties: "replyMode"
invalid config: must NOT have additional properties: "footer"

The bundled feishu schema uses additionalProperties: false for type-safety on known fields, but openclaw-lark legitimately extends the root channel config object with its own fields (replyMode, footer). The collectRawBundledChannelConfigIssues function validates against the static bundled schema and cannot know about plugin-registered extensions.

Fix

In collectRawBundledChannelConfigIssues (src/config/validation.ts), skip AJV errors where:

  • error.additionalProperty is set (it's an additionalProperties violation), AND
  • error.path === "<root>" (the violation is at the channel config root, not nested)

Nested additionalProperties errors at deeper paths (e.g. inside sub-objects like tts or connection) are still surfaced. This preserves type-safety for known sub-schemas while allowing plugin-owned root-level extensions.

Tests

Added two tests to validation.channel-metadata.test.ts:

  1. Feishu config with required fields + plugin extension fields (replyMode, footer) → ok: true
  2. Feishu config with genuinely invalid type (enabled: "not-a-boolean") → ok: false with path channels.feishu

Scope

  • src/config/validation.ts — 8 lines added (guard + comment)
  • src/config/validation.channel-metadata.test.ts — 2 new tests in new describe block

🤖 Generated with Claude Code

Changed files

  • src/config/validation.channel-metadata.test.ts (modified, +50/-0)
  • src/config/validation.ts (modified, +8/-0)

Code Example

config schema validation failed.
- channels.feishu: invalid config: must NOT have additional properties: "replyMode"
- channels.feishu: invalid config: must NOT have additional properties: "footer"
RAW_BUFFERClick to expand / collapse

Bug: openclaw config patch rejects openclaw-lark plugin extension fields (replyMode, footer)

Description

openclaw config patch and openclaw config apply reject valid openclaw-lark plugin configuration fields with additionalProperties: false validation errors:

config schema validation failed.
- channels.feishu: invalid config: must NOT have additional properties: "replyMode"
- channels.feishu: invalid config: must NOT have additional properties: "footer"

However, both replyMode and footer are valid configuration fields defined in the openclaw-lark plugin's own Zod schema (src/core/config-schema.js). The plugin correctly reads and uses these fields at runtime.

Root cause

The built-in channels.feishu JSON schema (config.schema.lookup channels.feishu) has additionalProperties: false, which rejects any fields not in the built-in schema. But when a plugin like openclaw-lark extends the channel configuration with its own fields, those extension fields should be accepted.

Environment

  • OpenClaw: 2026.5.4 (325df3e)
  • Plugin: openclaw-lark 2026.4.10
  • Node: v24.15.0
  • OS: Ubuntu 26.04

Workaround

Manually editing openclaw.json with python3/jq bypasses the CLI validation, and the fields work correctly at runtime.

Expected behavior

openclaw config patch should accept plugin extension fields in channel config, or at minimum warn instead of rejecting.

extent analysis

TL;DR

Update the built-in channels.feishu JSON schema to allow additional properties or modify the validation to accept plugin extension fields.

Guidance

  • Review the config.schema.lookup channels.feishu to understand the current schema constraints and identify the need to update additionalProperties to true or define the extension fields explicitly.
  • Consider modifying the validation logic in openclaw config patch to differentiate between built-in and plugin-provided fields, allowing the latter to bypass the additionalProperties: false check.
  • Investigate if the openclaw-lark plugin's Zod schema can be integrated or referenced by the built-in schema to automatically include the extension fields.
  • Verify that manually editing openclaw.json with the desired fields works as expected at runtime to confirm the issue is solely with the validation.

Example

No code snippet is provided as the issue revolves around schema validation and configuration rather than code implementation.

Notes

The solution may require updates to the OpenClaw core or the openclaw-lark plugin, depending on where the validation logic resides and how schemas are managed. The exact approach will depend on the internal workings of OpenClaw and its plugins.

Recommendation

Apply a workaround by manually editing openclaw.json until a permanent fix is implemented in the OpenClaw core or the openclaw-lark plugin, as this allows the extension fields to be used despite the validation error.

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

openclaw config patch should accept plugin extension fields in channel config, or at minimum warn instead of rejecting.

#memory optimization#batch processing#GPU compatibility#latency issue#model 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