[maintainer] feat: Feishu/Lark channel support by joshp123 · Pull Request #7313 · openclaw/openclaw

joshp123 · 2026-02-02T17:43:22Z

Human written summary:

The intent of this change is, as written by a human:

backport feishu support from github.com/jiulingyun/openclaw-cn

Changes

Port Feishu/Lark channel plugin from openclaw-cn fork
Feishu core: client, monitor, message, streaming-card, send, probe, accounts, config, pairing-store, access, format, bot, download
Domain config: channels.feishu.domain supports feishu (CN) and lark (global) endpoints
Outbound adapter + normalize helper for feishu:/lark: prefixes
Plugin extension: extensions/feishu/ (channel, onboarding, config-schema)
Docs: EN + zh-CN with screenshots
Test stability: increase Discord/Telegram unit timeouts for parallel runs
CHANGELOG: credit @jiulingyun (openclaw-cn)

Tests

pnpm lint
pnpm build
pnpm vitest run --config vitest.unit.config.ts src/telegram/bot.media.downloads-media-file-path-no-file-download.test.ts --maxWorkers 1
pnpm vitest run --config vitest.unit.config.ts src/discord/monitor.tool-result.accepts-guild-messages-mentionpatterns-match.test.ts --maxWorkers 1
pnpm test:all (fails in pnpm test:e2e: missing OPENCLAW_GATEWAY_TOKEN / gateway token mismatch; e2e failures include server.ios-client-id, gateway.multi, gateway server agent/chat/health/hooks/roles-allowlist/sessions-send, media-understanding.auto gemini, directive model list/help)

Risks

Lark global domain not verified against live tenant yet

Follow-ups

Add docs nav entry after channels group lands
Provide gateway auth token + gemini CLI if we want e2e green locally
Port CLI subcommands (openclaw feishu probe/send/accounts) if desired
Add src/feishu/strings.ts locale maps for i18n precursor

What: - clean up Feishu port for lint/type safety and error handling - allow buffers in Feishu media uploads and tighten config merging - increase Discord/Telegram unit test timeouts to reduce parallel flake Why: - backport Feishu support from openclaw-cn - keep local test runs stable under parallel load Tests: - pnpm lint - pnpm build - pnpm vitest run --config vitest.unit.config.ts src/telegram/bot.media.downloads-media-file-path-no-file-download.test.ts --maxWorkers 1 - pnpm vitest run --config vitest.unit.config.ts src/discord/monitor.tool-result.accepts-guild-messages-mentionpatterns-match.test.ts --maxWorkers 1 - pnpm test:all (fails in pnpm test:e2e: missing OPENCLAW_GATEWAY_TOKEN / gateway token mismatch; failing e2e tests include server.ios-client-id, gateway.multi, server.agent/chat/health/hooks/roles-allowlist/sessions-send, media-understanding.auto gemini, directive model list/help)

taiyi747 · 2026-02-03T11:06:25Z

Bug Report

1. Configuration & Command Errors
I encountered an error when using the CLI commands for Feishu (Lark):

Onboard: When running pnpm openclaw onboard, the first attempt was successful, but the second attempt failed.
Adding Channels: Subsequently, running pnpm openclaw channels add also triggers the same error.

Error Log:

ReferenceError: resolveDefaultFeishuAccountId is not defined
ELIFECYCLE Command failed with exit code 1.

10:32:57 [health] initial refresh failed: resolveDefaultFeishuAccountId is not defined

2. File Sending Issue (Private vs. Group Chat)
There is also an inconsistency when sending media files:

The bot cannot send files (images, videos, etc.) in Private Chats (DMs).
However, sending files works correctly in Group Chats.

3. Unresponsive /model Command
The bot does not respond when using the /model command to switch models. There is no feedback or confirmation message.

panda1105 · 2026-02-03T11:56:50Z

docs/channels/feishu.md

+1. You already ran `openclaw channels add` for Feishu
+2. The gateway is running (`openclaw gateway status`)
+
+In **Event Subscription**:


But for lark，I can not found Use long connection to receive events

https://open.feishu.cn/document/server-docs/event-subscription-guide/event-subscription-configure-/request-url-configuration-case?lang=en-US#14672524

Might this be what’s causing it?
->“Currently, long connection mode does not support store applications.”

Hey @AxiosLeo -- it's not this. Even when creating a custom app, ensuring you have logged App ID and App Secret to the binding wizard and restarting the gateway... this option never shows up on the Lark Developer Console for international users to select 'Use long connection'

Do the devs have a timeline for international support? Or is it better for us to build our own bridges?

jiulingyun · 2026-02-03T16:51:42Z

✅ Feishu China Domain Test Results

I've tested the Feishu integration with the China domain (feishu.cn) and all core features are working correctly:

Feature	Status
Message sending & receiving	✅ Pass
Streaming output (CardKit)	✅ Pass
Proactive image sending	✅ Pass
File sending (zip attachment)	✅ Pass
Pairing flow	✅ Pass

Test Screenshots

1. Pairing Flow & Basic Conversation

Pairing code generation works
Agent responds correctly after pairing approval

2. Proactive Screenshot Sending

Agent successfully captured screenshot using screencapture command
Image sent to Feishu chat via the media upload API

3. File Packaging & Sending

Agent zipped a folder (7.2MB) and sent it as attachment
File received correctly in Feishu client

All tests performed on openclaw-cn fork with Feishu self-built app using WebSocket persistent connection mode.

cc @jiulingyun (openclaw-cn maintainer)

jiulingyun · 2026-02-03T17:01:33Z

Clarification: The above tests were performed by directly fetching this PR branch (openclaw:feishu-support) and running locally, not on the openclaw-cn fork codebase.

git fetch upstream pull/7313/head:pr-7313-feishu
git switch pr-7313-feishu
pnpm install && pnpm build && pnpm check  # all passed

This confirms the PR branch itself works correctly for Feishu China domain.

joshp123 · 2026-02-03T22:28:11Z

Merged to main via fast-forward.

Commits:

2483f26 Channels: add Feishu/Lark support
0223416 Channels: finish Feishu/Lark integration

Tests:

pnpm build
pnpm check
pnpm test

Thanks @jiulingyun for the upstream work!

joshp123 · 2026-02-03T22:32:22Z

Thanks to everyone who tested and reported issues @taiyi747 and. @panda1105 — we appreciate the help! We will fix the bugs rolling forward - we will first get the channel live so more Chinese users can benefit, and then fix bugs after.

siwatanejo · 2026-02-04T01:05:00Z

@joshp123 good work! BTW there's also a PR adding WeChat support, can that be looked at?

joshp123 · 2026-02-04T01:40:27Z

@siwatanejo

@joshp123 good work! BTW there's also a PR adding WeChat support, can that be looked at?

Thanks! Yes, WeChat is on our radar. I have seen a couple of competing implementations, but also I am hearing conflicting stories - some people say that you will get instabanned for using it, others say that it's fine. And since I'm not Chinese or in mainland China, its hard for me to know for sure. So I'm hoping the community is able to converge on an answer here for me 😬 😅 Slightly chickening out but it is what it is. If you're not already on our discord, we have a threat in help-中文 for adding these things!

zouhuigang · 2026-02-04T03:03:06Z

(base) zouhuigang@zouhuigangdeMacBook-Air ~ % openclaw plugins install @openclaw/feishu
(node:54905) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

🦞 OpenClaw 2026.2.2-3 (9c5941b) — Your terminal just grew claws—type something and let the bot pinch the busywork.

Downloading @openclaw/feishu…
npm pack failed: npm notice Access token expired or revoked. Please try logging in again.
npm notice Access token expired or revoked. Please try logging in again.
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@openclaw%2ffeishu - Not found
npm error 404
npm error 404  '@openclaw/feishu@*' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/zouhuigang/.npm/_logs/2026-02-04T02_55_33_413Z-debug-0.log

jiulingyun · 2026-02-04T03:04:32Z

(base) zouhuigang@zouhuigangdeMacBook-Air ~ % openclaw plugins install @openclaw/feishu
(node:54905) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

🦞 OpenClaw 2026.2.2-3 (9c5941b) — Your terminal just grew claws—type something and let the bot pinch the busywork.

Downloading @openclaw/feishu…
npm pack failed: npm notice Access token expired or revoked. Please try logging in again.
npm notice Access token expired or revoked. Please try logging in again.
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@openclaw%2ffeishu - Not found
npm error 404
npm error 404  '@openclaw/feishu@*' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/zouhuigang/.npm/_logs/2026-02-04T02_55_33_413Z-debug-0.log

Select local installation

zouhuigang · 2026-02-04T03:25:33Z

(base) zouhuigang@zouhuigangdeMacBook-Air ~ % openclaw plugins install @openclaw/feishu
(node:54905) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

🦞 OpenClaw 2026.2.2-3 (9c5941b) — Your terminal just grew claws—type something and let the bot pinch the busywork.

Downloading @openclaw/feishu…
npm pack failed: npm notice Access token expired or revoked. Please try logging in again.
npm notice Access token expired or revoked. Please try logging in again.
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@openclaw%2ffeishu - Not found
npm error 404
npm error 404  '@openclaw/feishu@*' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/zouhuigang/.npm/_logs/2026-02-04T02_55_33_413Z-debug-0.log

Select local installation

openclaw channels add

谢谢，已经安装成功了。

tokyo2006 · 2026-02-04T06:32:12Z

got warning:

Config warnings:\n- plugins.entries.feishu: plugin feishu: duplicate plugin id detected; later plugin may be overridden (/home/moltbot/.npm-global/lib/node_modules/openclaw/extensions/feishu/index.ts)

because I installed @m1heng-clawd/feishu before. How can I fix this warning?

jaysenwu · 2026-02-04T07:10:48Z

能加一个敲键盘的动作吗？如果bot已经接收到消息，并开始工作

jiulingyun · 2026-02-04T07:36:40Z

能加一个敲键盘的动作吗？如果bot已经接收到消息，并开始工作

这个功能已经有了的，支持块级流式输出和卡片流式输出。

需要给飞书配置完整的权限，文档：https://clawd.org.cn/channels/feishu.html

zixindh · 2026-02-04T12:00:55Z

无法保存这个长链接的配置是怎么回事？一直报错。公开平台里其他的权限都已经打开了。

jiulingyun · 2026-02-04T12:02:58Z

无法保存这个长链接的配置是怎么回事？一直报错。公开平台里其他的权限都已经打开了。

流程不对，按流程来，看一下文档：https://clawd.org.cn/channels/feishu.html

zouhuigang · 2026-02-04T12:36:29Z

@jiulingyun /reset指令好像不生效。

jiulingyun · 2026-02-04T14:19:08Z

@jiulingyun /reset指令好像不生效。

用户命令将会在一个版本将会支持

no010 · 2026-02-05T01:50:51Z

如果之前的版本中安装了飞书插件，直接更新会不会有问题？

kongdd · 2026-02-05T03:53:01Z

这个PR跟https://github.com/m1heng/clawdbot-feishu是啥关系？
这个PR有点捣乱啊，开源社区力量分散了。
本来clawdbot-feishu用的好好的，而且别人的channel id已经注册了feishu。

你这个PR，抢占别人的channel id，直接导致大批clawdbot-feishu 用户无法使用。

m1heng/clawdbot-feishu#171, #8650

zouhuigang · 2026-02-05T05:25:34Z

飞书的消息展示不全，丢失了前面的内容。

完整的内容前面还有很多：

zouhuigang · 2026-02-05T05:26:00Z

@jiulingyun 大佬，消息展示不全。

soniclue · 2026-02-05T16:24:28Z

这个PR跟https://github.com/m1heng/clawdbot-feishu是啥关系？这个PR有点捣乱啊，开源社区力量分散了。本来clawdbot-feishu用的好好的，而且别人的channel id已经注册了feishu。

你这个PR，抢占别人的channel id，直接导致大批clawdbot-feishu 用户无法使用。

m1heng/clawdbot-feishu#171, #8650

+1. I had the same issue. Had to remove m1heng/clawdbot-feishu otherwise the conflict prevents gateway to start.
m1heng/clawdbot-feishu has much better features than the now built-in one.

joshp123 added the maintainer Maintainer-authored PR label Feb 2, 2026

openclaw-barnacle bot added the docs Improvements or additions to documentation label Feb 2, 2026

joshp123 force-pushed the feishu-support branch from 8dbd25d to d8a8897 Compare February 2, 2026 23:25

openclaw-barnacle bot added channel: discord Channel integration: discord channel: telegram Channel integration: telegram labels Feb 2, 2026

panda1105 reviewed Feb 3, 2026

View reviewed changes

joshp123 closed this Feb 3, 2026

Bermudarat mentioned this pull request Feb 9, 2026

fix(feishu): Remove incorrect oc_ prefix assumption in resolveFeishuSession #10407

Merged

5 tasks

Uh oh!

Conversation

joshp123 commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Human written summary:

Changes

Tests

Risks

Follow-ups

Uh oh!

taiyi747 commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bug Report

Uh oh!

panda1105 Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

AxiosLeo Feb 4, 2026

Choose a reason for hiding this comment

Uh oh!

xriswithers Feb 5, 2026

Choose a reason for hiding this comment

Uh oh!

jiulingyun commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Feishu China Domain Test Results

Test Screenshots

Uh oh!

jiulingyun commented Feb 3, 2026

Uh oh!

joshp123 commented Feb 3, 2026

Uh oh!

joshp123 commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

siwatanejo commented Feb 4, 2026

Uh oh!

joshp123 commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zouhuigang commented Feb 4, 2026

Uh oh!

jiulingyun commented Feb 4, 2026

Uh oh!

zouhuigang commented Feb 4, 2026

Uh oh!

tokyo2006 commented Feb 4, 2026

Uh oh!

jaysenwu commented Feb 4, 2026

Uh oh!

jiulingyun commented Feb 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zixindh commented Feb 4, 2026

Uh oh!

jiulingyun commented Feb 4, 2026

Uh oh!

zouhuigang commented Feb 4, 2026

Uh oh!

jiulingyun commented Feb 4, 2026

Uh oh!

no010 commented Feb 5, 2026

Uh oh!

kongdd commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

zouhuigang commented Feb 5, 2026

Uh oh!

zouhuigang commented Feb 5, 2026

Uh oh!

soniclue commented Feb 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

14 participants

joshp123 commented Feb 2, 2026 •

edited

Loading

taiyi747 commented Feb 3, 2026 •

edited

Loading

jiulingyun commented Feb 3, 2026 •

edited

Loading

joshp123 commented Feb 3, 2026 •

edited

Loading

joshp123 commented Feb 4, 2026 •

edited

Loading

jiulingyun commented Feb 4, 2026 •

edited

Loading

kongdd commented Feb 5, 2026 •

edited

Loading