openclaw - 💡(How to fix) Fix [Feature Request] Support configuring group messages to default to Feishu card format

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…

Code Example

{
  "channels": {
    "feishu": {
      "groupMessageFormat": "card", // or "text" (default)
      "groupPolicy": "open"
    }
  }
}
RAW_BUFFERClick to expand / collapse

Feature Request: 群消息默认发飞书卡片

Problem

Currently, Feishu group messages sent by OpenClaw use plain text format. Users want the ability to configure all group messages to use Feishu Interactive Card format by default.

Use Case

Park management agent needs to send daily briefings (招商简报, 物业工单, etc.) to multiple group chats. Currently requires explicit --msg-type interactive on every message. Users want this to be the default behavior for group chats.

Proposed Solution

Add a config option to channels.feishu:

{
  "channels": {
    "feishu": {
      "groupMessageFormat": "card", // or "text" (default)
      "groupPolicy": "open"
    }
  }
}

When groupMessageFormat: "card" is set, all group messages would automatically use the Feishu Interactive Card format instead of plain text.

Alternatives Considered

  1. Per-group configuration: Allow different format per chat_id
  2. Streaming card mode: Already supported via streaming: true, but still requires explicit card format
  3. Message-type specific: Cards for reports vs text for casual replies

Additional Context

  • Feishu streaming cards are already supported (streaming: true)
  • Interactive card sending requires --msg-type interactive and full card JSON payload
  • This would be a user-facing config option

Requested by: 王卓 (park-agent use case, 上海金蝶软件园)

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