Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: feishu_doc 插件加载正常，但工具未暴露给 agent 调用 [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#59571•Fetched 2026-04-08 02:43:03
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
fengzoujun-coderfengzoujun-coder
Participants
fengzoujun-coderfengzoujun-coder
Timeline (top)
labeled ×2

飞书文档权限已开通、插件已加载、channels.feishu.tools.doc 已配置为 true，但 agent 无法调用 feishu_doc 工具。尝试通过飞书聊天发送 wiki 链接，agent 无法识别并读取文档内容。 环境： OpenClaw 版本：2026.4.1（npm 安装） 操作系统：macOS 飞书版本：Feishu (feishu.cn) Node 版本：v25.8.2 已排查的项： ✅ 飞书开放平台应用已开通 docx:document、drive:drive 等权限 ✅ 应用已发布 ✅ 飞书频道配置正常（消息收发正常） ✅ 插件加载正常（日志显示 feishu_doc、feishu_wiki、feishu_drive 等已注册） ✅ channels.feishu.tools.doc 已配置为 true ✅ npm 已更新到最新 ✅ Gateway 已重启多次 ❌ openclaw feishu_doc CLI 命令不存在（插件注册了工具但未暴露为 CLI 命令） ❌ Agent 无法通过聊天识别飞书 wiki 链接

Root Cause

飞书文档权限已开通、插件已加载、channels.feishu.tools.doc 已配置为 true，但 agent 无法调用 feishu_doc 工具。尝试通过飞书聊天发送 wiki 链接，agent 无法识别并读取文档内容。 环境： OpenClaw 版本：2026.4.1（npm 安装） 操作系统：macOS 飞书版本：Feishu (feishu.cn) Node 版本：v25.8.2 已排查的项： ✅ 飞书开放平台应用已开通 docx:document、drive:drive 等权限 ✅ 应用已发布 ✅ 飞书频道配置正常（消息收发正常） ✅ 插件加载正常（日志显示 feishu_doc、feishu_wiki、feishu_drive 等已注册） ✅ channels.feishu.tools.doc 已配置为 true ✅ npm 已更新到最新 ✅ Gateway 已重启多次 ❌ openclaw feishu_doc CLI 命令不存在（插件注册了工具但未暴露为 CLI 命令） ❌ Agent 无法通过聊天识别飞书 wiki 链接

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

飞书文档权限已开通、插件已加载、channels.feishu.tools.doc 已配置为 true，但 agent 无法调用 feishu_doc 工具。尝试通过飞书聊天发送 wiki 链接，agent 无法识别并读取文档内容。 环境： OpenClaw 版本：2026.4.1（npm 安装） 操作系统：macOS 飞书版本：Feishu (feishu.cn) Node 版本：v25.8.2 已排查的项： ✅ 飞书开放平台应用已开通 docx:document、drive:drive 等权限 ✅ 应用已发布 ✅ 飞书频道配置正常（消息收发正常） ✅ 插件加载正常（日志显示 feishu_doc、feishu_wiki、feishu_drive 等已注册） ✅ channels.feishu.tools.doc 已配置为 true ✅ npm 已更新到最新 ✅ Gateway 已重启多次 ❌ openclaw feishu_doc CLI 命令不存在（插件注册了工具但未暴露为 CLI 命令） ❌ Agent 无法通过聊天识别飞书 wiki 链接

Steps to reproduce

  1. 在飞书对话中发送飞书 wiki 链接
  2. Agent 不识别，无法读取文档内容
  3. 尝试通过 CLI 调用 openclaw feishu_doc read --doc <token> 报错 unknown command 额外信息： 同一企业的其他同事使用相同配置可以正常读取飞书文档，怀疑与 OpenClaw 实例配置或版本差异有关。 提交地址： GitHub Issues: Issues · openclaw/openclaw Discord: https://discord.com/invite/clawd 你可以直接复制上面的内容去提交。这是 OpenClaw 的 bug，不是你能手动解决的了。提交后等开发者回复就好 🙏

Expected behavior

no

Actual behavior

no

OpenClaw version

newest

Operating system

macOS15.4

Install method

No response

Model

minimax

Provider / routing chain

openclaw-minimax

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can be resolved by ensuring the feishu_doc tool is properly exposed as a CLI command in the OpenClaw instance.

Guidance

  • Verify that the feishu_doc tool is registered and configured correctly in the OpenClaw instance.
  • Check the OpenClaw documentation to see if there are any specific steps required to expose the feishu_doc tool as a CLI command.
  • Compare the configuration and version of the OpenClaw instance with the instances used by other colleagues who are able to read Feishu documents successfully.
  • Submit the issue to the OpenClaw developers on GitHub or Discord for further assistance, as the problem may be related to the OpenClaw instance configuration or version.

Notes

The issue seems to be specific to the OpenClaw instance configuration or version, and the problem is not with the Feishu setup or permissions. The fact that other colleagues can read Feishu documents successfully with the same configuration suggests that the issue is likely related to the OpenClaw instance.

Recommendation

Apply workaround: The user should submit the issue to the OpenClaw developers and wait for their response, as the problem may require changes to the OpenClaw instance configuration or version.

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…

FAQ

Expected behavior

no

#agent setup#task chaining#parallel task#integration issue#index setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING