openclaw - 💡(How to fix) Fix Feishu: support native exec approval action cards for exec approvals [1 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#69860Fetched 2026-04-22 07:47:18
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants
RAW_BUFFERClick to expand / collapse

What problem does this solve?

OpenClaw Feishu/Lark already supports interactive cards, but exec approval prompts in Feishu DMs currently render as text-style approval cards/instructions instead of true actionable approval buttons.

In practice, the approval reaches Feishu, but the operator still sees a card that mainly contains text instructions rather than direct actions such as:

  • Allow once
  • Allow always
  • Deny

This makes Feishu operator workflows noticeably less efficient than Discord, even though Feishu already has card UI primitives that should be able to support the interaction model.

Why is this valuable?

Feishu is a strong operator/admin surface for private chat workflows. Native actionable exec approval buttons would:

  • reduce friction in daily approval flows
  • make Feishu a more complete operations surface
  • improve parity with Discord's existing exec approval UX
  • reduce confusion for users who assume inlineButtons / interactive cards imply clickable approval actions

What should happen?

Please add first-class Feishu/Lark support for native exec approval action cards.

Ideal behavior:

  • exec approval prompts in Feishu render as actionable cards/buttons, not just text instructions
  • support basic actions such as Allow once / Deny at minimum
  • optionally support richer controls similar to Discord channels.discord.execApprovals where feasible
  • approval cards update cleanly after approval/denial

Proposed solution (optional)

Possible implementation directions:

  1. add a Feishu-specific config surface such as channels.feishu.execApprovals
  2. map exec approval requests onto Feishu interactive card actions/callbacks
  3. reuse the existing approval backend and add Feishu-specific presentation + callback handling

Even a minimal first version would already be a meaningful improvement.

Evidence / links / screenshots

What I verified locally on OpenClaw 2026.4.20 (115f05d):

  • Feishu channel is enabled and supports interactive cards / inlineButtons
  • exec approval requests do reach Feishu
  • however, Feishu currently shows a text-style approval card/instruction rather than native actionable approval buttons
  • channels.discord.execApprovals exists in config schema
  • changelog explicitly mentions Discord exec approval prompts and channels.discord.execApprovals.target
  • Discord provider runtime reads discordCfg.execApprovals
  • channels.feishu.execApprovals does not exist in the current config schema
  • Feishu docs mention interactive cards / streaming cards, but not exec approval support

Additional information

Two additional asks:

  1. If full Feishu exec approval parity is not ready yet, documenting the current limitation explicitly in Feishu docs would help set expectations.
  2. If possible, keep the implementation backward-compatible with current Feishu config and approval flows.

extent analysis

TL;DR

Add Feishu-specific configuration and mapping to support native exec approval action cards.

Guidance

  • Investigate adding a channels.feishu.execApprovals config surface to enable native exec approval support.
  • Map exec approval requests onto Feishu interactive card actions/callbacks to render actionable cards/buttons.
  • Reuse the existing approval backend and add Feishu-specific presentation + callback handling for a minimal first version.
  • Verify that the Feishu channel is enabled and supports interactive cards/inlineButtons before implementing the solution.

Example

No code snippet is provided as the issue does not contain sufficient technical details for a concrete implementation.

Notes

The implementation should aim to be backward-compatible with current Feishu config and approval flows. Additionally, documenting the current limitation in Feishu docs would help set expectations if full parity is not ready yet.

Recommendation

Apply a workaround by adding a Feishu-specific configuration and mapping to support native exec approval action cards, as this would improve the efficiency of Feishu operator workflows and reduce friction in daily approval flows.

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

openclaw - 💡(How to fix) Fix Feishu: support native exec approval action cards for exec approvals [1 participants]