feat(feishu): sync community contributions from clawdbot-feishu by doodlewind · Pull Request #12662 · openclaw/openclaw

doodlewind · 2026-02-09T13:14:09Z

Summary

Sync community contributions from the independent feishu plugin repo (clawdbot-feishu 0171c12..ee8312a):

Message deduplication: Prevents duplicate message processing on WebSocket reconnect/retry, with configurable cache size and throttled cleanup
Webhook connection mode: Adds HTTP webhook support for Lark International which does not support WebSocket event subscription
Topic session isolation: Per-thread/topic session isolation inside group chats, using chatId:topic:rootId as peer ID
Dynamic agent creation: Auto-create agents for DM users based on configurable templates
Card schema 2.0: Upgrade interactive card format for proper markdown rendering

Closes

Closes Feishu WebSocket duplicate messages #11720 — Feishu WebSocket duplicate messages
Closes [Bug] Feishu messages duplicated (retry mechanism lacks deduplication)` #11762 — Feishu messages duplicated (retry mechanism lacks deduplication)
Closes Feishu WebSocket Message Replay After Service Restart #9502 — Feishu WebSocket Message Replay After Service Restart
Closes [Bug]: 飞书重复发送信息 #10557 — 飞书重复发送信息
Closes [Feature]: Feishu: support per-thread/topic session isolation inside a single group #11344 — [Feature] Feishu: support per-thread/topic session isolation
Closes Feishu Plugin: Message Redelivery + Timezone Handling Error (Ghost Message Replay) #10803 — Feishu Plugin: Message Redelivery + Ghost Message Replay
Closes [Feature]: Add HTTP Webhook Support for Lark Channel #12464 — [Feature] Add HTTP Webhook Support for Lark Channel
Closes Lark vs. Feishu: Inconsistent Permission Scopes and Lack of Long-Connection Event Subscription Support in Lark (Feishu Channel Unavailable) #9057 — Lark: Lack of Long-Connection Event Subscription Support

Test plan

Verify WebSocket mode still works with dedup enabled
Test webhook mode with Lark International app
Test topic session isolation in group chats with multiple threads
Verify DM dynamic agent creation with dynamicAgentCreation.enabled: true
Confirm card rendering with schema 2.0 format

🤖 Generated with Claude Code

Greptile Overview

Greptile Summary

This PR syncs Feishu plugin changes from an upstream community repo, adding (1) in-memory message deduplication to reduce duplicate handling on reconnect/redelivery, (2) a webhook-based connection mode (HTTP server + Lark adapter) for environments without WS subscriptions, (3) optional topic/thread session isolation in group chats via a derived peer id, (4) dynamic DM agent creation by writing new agents/bindings into the config file, and (5) interactive card schema 2.0 formatting for improved markdown rendering.

Key touch points are extensions/feishu/src/bot.ts (inbound parsing/routing/dedup + dynamic agent creation), extensions/feishu/src/monitor.ts (WS vs webhook listener), and extensions/feishu/src/config-schema.ts/types.ts (new config knobs).

Confidence Score: 3/5

This PR is close but has a few functional issues that can break DM routing/dynamic agent creation and multi-account webhook startup.
Core changes are reasonable, but there are clear inconsistencies in routing peer kinds (dm vs direct), dynamic-agent config writes not being applied to dispatch, and a deterministic port-collision failure mode for multi-account webhook setups that will prevent monitoring from starting.
extensions/feishu/src/bot.ts, extensions/feishu/src/dynamic-agent.ts, extensions/feishu/src/monitor.ts

_{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!}

Sync community contributions from the independent feishu plugin repo (clawdbot-feishu 0171c12..ee8312a): - Card format upgrade to schema 2.0 for proper markdown rendering - Message dedup mechanism to prevent duplicate processing on WS reconnect - Dynamic agent creation for DM users - Topic-based session isolation for group chats - Webhook connection mode support for Lark Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

greptile-apps

_{2 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-09T13:16:20Z

extensions/feishu/src/bot.ts

+    let route = core.channel.routing.resolveAgentRoute({
      cfg,
      channel: "feishu",
      accountId: account.accountId,
      peer: {
        kind: isGroup ? "group" : "direct",
-        id: isGroup ? ctx.chatId : ctx.senderOpenId,
+        id: peerId,
      },
    });


Inconsistent peer kind

resolveAgentRoute is first called with peer.kind set to "direct" for DMs, but if dynamic agent creation triggers you re-resolve using peer.kind: "dm" (and dynamic-agent.ts also creates bindings with peer.kind: "dm"). If the routing/binding system only recognizes "direct" (as used elsewhere in the codebase) this will prevent the new binding from ever matching, leaving DMs stuck on the default route.

This should use the same peer kind consistently (typically "direct") for both binding creation and route resolution.

Also appears in: extensions/feishu/src/dynamic-agent.ts:29-33, 67-71, 109-112.

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/feishu/src/bot.ts Line: 688:696 Comment: **Inconsistent peer kind** `resolveAgentRoute` is first called with `peer.kind` set to `"direct"` for DMs, but if dynamic agent creation triggers you re-resolve using `peer.kind: "dm"` (and `dynamic-agent.ts` also creates bindings with `peer.kind: "dm"`). If the routing/binding system only recognizes `"direct"` (as used elsewhere in the codebase) this will prevent the new binding from ever matching, leaving DMs stuck on the default route. This should use the same peer kind consistently (typically `"direct"`) for both binding creation and route resolution. Also appears in: `extensions/feishu/src/dynamic-agent.ts:29-33, 67-71, 109-112`. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-09T13:16:21Z

extensions/feishu/src/monitor.ts

+  const port = account.config.webhookPort ?? 3000;
+  const path = account.config.webhookPath ?? "/feishu/events";
+
+  log(`feishu[${accountId}]: starting Webhook server on port ${port}, path ${path}...`);
+
+  const server = http.createServer();
+  server.on("request", Lark.adaptDefault(path, eventDispatcher, { autoChallenge: true }));


Port collision across accounts

In webhook mode, monitorWebhook defaults to webhookPort ?? 3000 for every account. If multiple Feishu accounts are enabled with connectionMode: "webhook" and don’t explicitly set distinct ports, the second server will fail to listen() (EADDRINUSE) and monitoring for that account will never start.

Consider requiring an explicit port in webhook mode, or deriving unique defaults per account / running a single shared server with per-account routing.

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/feishu/src/monitor.ts Line: 194:200 Comment: **Port collision across accounts** In webhook mode, `monitorWebhook` defaults to `webhookPort ?? 3000` for every account. If multiple Feishu accounts are enabled with `connectionMode: "webhook"` and don’t explicitly set distinct ports, the second server will fail to `listen()` (EADDRINUSE) and monitoring for that account will never start. Consider requiring an explicit port in webhook mode, or deriving unique defaults per account / running a single shared server with per-account routing. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-09T13:16:22Z

extensions/feishu/src/bot.ts

+    let effectiveCfg = cfg;
+    if (!isGroup && route.matchedBy === "default") {
+      const dynamicCfg = feishuCfg?.dynamicAgentCreation as DynamicAgentCreationConfig | undefined;
+      if (dynamicCfg?.enabled) {
+        const runtime = getFeishuRuntime();
+        const result = await maybeCreateDynamicAgent({
+          cfg,
+          runtime,


Config writes ignored

maybeCreateDynamicAgent writes the updated config file via runtime.config.writeConfigFile(updatedCfg), but handleFeishuMessage continues dispatching using the original cfg (e.g. dispatchReplyFromConfig({ ctx, cfg, ... })). Since routing and agent selection are config-driven, the newly-created agent/binding may not take effect for the current message (and possibly subsequent messages depending on how cfg is sourced).

If dynamic agent creation is intended to apply immediately, the dispatch path should use effectiveCfg (or otherwise reload config after the write) consistently for routing + dispatch.

Also appears in: extensions/feishu/src/bot.ts:712-726 where effectiveCfg is set but not used later.

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/feishu/src/bot.ts Line: 700:707 Comment: **Config writes ignored** `maybeCreateDynamicAgent` writes the updated config file via `runtime.config.writeConfigFile(updatedCfg)`, but `handleFeishuMessage` continues dispatching using the original `cfg` (e.g. `dispatchReplyFromConfig({ ctx, cfg, ... })`). Since routing and agent selection are config-driven, the newly-created agent/binding may not take effect for the current message (and possibly subsequent messages depending on how `cfg` is sourced). If dynamic agent creation is intended to apply immediately, the dispatch path should use `effectiveCfg` (or otherwise reload config after the write) consistently for routing + dispatch. Also appears in: `extensions/feishu/src/bot.ts:712-726` where `effectiveCfg` is set but not used later. How can I resolve this? If you propose a fix, please make it concise.

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

…claw#12662)

openclaw-barnacle bot added the channel: feishu Channel integration: feishu label Feb 9, 2026

greptile-apps bot reviewed Feb 9, 2026

View reviewed changes

cpojer merged commit 5c2cb6c into openclaw:main Feb 10, 2026
25 checks passed

trevorgordon981 pushed a commit to trevorgordon981/openclaw that referenced this pull request Feb 10, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

b1da95f

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

trevorgordon981 pushed a commit to trevorgordon981/openclaw that referenced this pull request Feb 10, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

2adb591

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

lucasmpramos pushed a commit to butley/openclaw that referenced this pull request Feb 10, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

b811626

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Hansen1018 pushed a commit to Hansen1018/openclaw that referenced this pull request Feb 10, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

fe31baf

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

graydawnc mentioned this pull request Feb 12, 2026

目前和官方插件的更新是如何同步的？ m1heng/clawdbot-feishu#219

Closed

skyhawk14 pushed a commit to skyhawk14/openclaw that referenced this pull request Feb 13, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

7caba62

…claw#12662) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

graydawnc mentioned this pull request Feb 14, 2026

feat(feishu): sync community plugin updates from clawdbot-feishu v0.1.10 #16337

Closed

zooqueen pushed a commit to hanzoai/bot that referenced this pull request Mar 6, 2026

feat(feishu): sync community contributions from clawdbot-feishu (open…

56e9f09

…claw#12662)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(feishu): sync community contributions from clawdbot-feishu#12662

feat(feishu): sync community contributions from clawdbot-feishu#12662
cpojer merged 1 commit intoopenclaw:mainfrom
doodlewind:feat/feishu-sync-upstream

doodlewind commented Feb 9, 2026 •

edited by greptile-apps bot

Loading

Uh oh!

greptile-apps bot left a comment

Uh oh!

greptile-apps bot Feb 9, 2026

Uh oh!

greptile-apps bot Feb 9, 2026

Uh oh!

greptile-apps bot Feb 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

doodlewind commented Feb 9, 2026 • edited by greptile-apps bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Closes

Test plan

Greptile Overview

Greptile Summary

Confidence Score: 3/5

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

doodlewind commented Feb 9, 2026 •

edited by greptile-apps bot

Loading