This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

ax-feishu-bridge

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add ax-feishu-bridge

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• 通过扫码快速创建飞书/Lark 机器人，减少手动配置
• 支持私聊、群聊、群话题分别维护独立的 Pi 会话
• • open：群里和话题里可直接回复，不需要 @，还需手动在飞书开发者后台开启机器人“获取群组中所有消息”的权限
• • mention：只有 @ 机器人、命中关键词或回复机器人消息时才会回复（后两项可选开启）
• 支持图片、代码文件和文本文件等附件输入；图片识别取决于当前模型是否支持图片

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

What to do if Feishu bot doesn't reply after installation?

Check three things in order: 1) Whether configuration is complete (DSH will automatically enter terminal configuration wizard on next startup if no configuration is detected); 2) Whether the plugin loads with the host (autoStart is enabled by default in DSH, use /feishu status to check connection status); 3) Whether group strategy requires @ mentions for the bot (when strategy is mention, it only replies to @ or keyword hits).

Will Feishu plugins for both DSH and Pi conflict if installed simultaneously?

No interference. Configurations are stored separately at ~/.dsh/feishu/config.harness.json and ~/.pi/agent/feishu/config.pi.json; connection locks are distinguished by robot credentials (appId), multiple processes with the same appId will only keep one holder (others will be marked owned by another process); card callback ports are 3001 for Pi and 3002 for DSH, default offset.

Can the model 'see' images sent to the bot?

Yes, but with two prerequisites: 1) The currently selected model must support image input; 2) The Harness host must provide image attachment service - if not mounted, the plugin will register local storage to ~/.dsh/attachments (falls back to text-only on mount failure). Only supports png/jpg/webp/gif.

How to trigger in group chat without @?

When group strategy is set to open, group messages automatically trigger by default; when strategy is mention, only @ mentions reply, but can be combined: 1) Enable "Get all messages in group" or "Get messages sent by users and bots in group" permissions in Feishu developer后台; 2) Configure keyword trigger with /config groupKeywords 报警,告警; 3) Enable continued questioning on bot replies with /config groupAlsoOnReply true.

What items can be changed with /config

Limited to whitelist: group strategy (open/mention), group keywords, reply bot message trigger, whether to ignore other bots, emoji response on message, language, streaming response toggle and print/push interval. Connection-level config like App ID/Secret, card callback address, quote message expansion does not accept in-chat modification, requires editing config.json and restart.

How to uninstall or reset?

Run /feishu reset confirm in DSH to clear config and session mapping (keeps session history); use dsh plugin remove for complete uninstall. reset won't delete sessions on Feishu side or the bot itself.

Will long-running tasks be reported as failed?

No by default. promptNotifySec=180 means a "still processing" notice is sent via Feishu after 180 seconds, reply card stays "replying", delivered normally after completion. Only explicit promptTimeoutSec>0 will hard timeout and report failure.

Can this plugin only be used in DSH?

No. The same npm package (ax-feishu-bridge) is distributed as both Pi extension and DSH bundle plugin, with completely independent config, group strategy, and session isolation - they can coexist; the Windows configuration paragraph in README is only for Pi adapter (Pi needs Git Bash specified on Windows), DSH adapter doesn't need this step.

— source: plugin_wiki.faq_json

Compatibility

• DSH: 0.1.0-rc.6+
• Node: >=22.19.0

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule