clawd-feishu

Feishu/Lark (飞书) channel plugin for OpenClaw.

中文社区资料 - 配置教程、常见问题、使用技巧：Wiki

Contributing / 贡献指南: CONTRIBUTING.md

Issue Reporting / 问题反馈: Please check Discussions first for common solutions, then open a structured Issue Form if needed.
问题反馈前请先查看 Discussions 是否已有常见解答；如仍未解决，再提交结构化 Issue 模板。

Questions / 使用咨询: Use Question issue for troubleshooting; use Discussions for open-ended Q&A.
排查型咨询请提交 Question Issue；开放式交流请使用 Discussions。

English | 中文

openclaw plugins install @m1heng-clawd/feishu

# Option A (recommended): download latest package tarball
npm pack @m1heng-clawd/feishu
openclaw plugins install ./m1heng-clawd-feishu-<version>.tgz

# Option B (keep curl flow): resolve latest tarball URL, then download/install
TARBALL_URL="$(npm view @m1heng-clawd/feishu dist.tarball)"
curl -L -o feishu-latest.tgz "$TARBALL_URL"
openclaw plugins install ./feishu-latest.tgz

# Windows PowerShell (Option B)
$tarball = npm view @m1heng-clawd/feishu dist.tarball
curl.exe -L $tarball -o feishu-latest.tgz
openclaw plugins install .\feishu-latest.tgz

# Option C (no npm command): use URL template with latest version from npm Versions tab
# https://www.npmjs.com/package/@m1heng-clawd/feishu?activeTab=versions
curl -L -o feishu-latest.tgz https://registry.npmjs.org/@m1heng-clawd/feishu/-/feishu-<version>.tgz
openclaw plugins install ./feishu-latest.tgz

openclaw plugins update feishu

Check installed version:

openclaw plugins list | rg -i feishu

1. Create a self-built app on Feishu Open Platform
2. Get your App ID and App Secret from the Credentials page
3. Enable required permissions (see below)
4. Configure event subscriptions (see below) ⚠️ Important
5. Configure the plugin:

Read-only (minimum required):

Read-write (optional, for create/edit/delete operations):

Task scope names may vary slightly in Feishu console UI. If needed, search for Task / Tasklist / Comment / Attachment-related permissions and grant read/write accordingly.

Task comments require dedicated scopes:

1. Read comments: grant task:comment:read.
2. Create/update/delete comments: grant task:comment:write.

If these scopes are missing, comment APIs will return permission-denied errors.

Task attachments support upload/get/list/delete. Upload sources:

1. Local files on the OpenClaw/Node host (file_path)
2. Remote links (file_url, public or presigned)

For file_url, OpenClaw runtime media loader is used with safety checks and size limit (mediaMaxMb), then the downloaded file is uploaded via a temporary local file.

Important: Keep tasklist owner as the bot. Add users as members instead.

Tasklist access is granted based on owner + member roles. If you change the owner to a user and the bot is not a member, the bot may lose permission to read/edit/manage that tasklist (and subsequent operations will fail).

Important: A user can only view a task when they are included as an assignee.

Limitation: The bot can currently only create subtasks for tasks created by itself.

To avoid “task created but not visible” issues:

1. When creating a task, set the requesting user as an assignee.
2. If you need more flexible subtask organization/visibility, consider using tasklists.

Important: Bots don't have their own "My Space" (root folder). Bots can only access files/folders that have been shared with them.

To let the bot manage files:

1. Create a folder in your Feishu Drive
2. Right-click the folder → Share → search for your bot name
3. Grant appropriate permission (view/edit)

Without this step, feishu_drive operations like create_folder will fail because the bot has no root folder to create in.

Important: API permissions alone are not enough for wiki access. You must also add the bot to each wiki space.

1. Open the wiki space you want the bot to access
2. Click Settings (gear icon) → Members
3. Click Add Member → search for your bot name
4. Select appropriate permission level (view/edit)

Without this step, feishu_wiki will return empty results even with correct API permissions.

Reference: Wiki FAQ - How to add app to wiki

Important: Like other resources, the bot can only access bitables that have been shared with it.

To let the bot access a bitable:

1. Open the bitable you want the bot to access
2. Click Share button → search for your bot name
3. Grant appropriate permission (view/edit)

The feishu_bitable tools support both URL formats:

• /base/XXX?table=YYY - Standard bitable URL
• /wiki/XXX?table=YYY - Bitable embedded in wiki (auto-converts to app_token)

This is the most commonly missed configuration! If the bot can send messages but cannot receive them, check this section.

In the Feishu Open Platform console, go to Events & Callbacks:

1. Event configuration: Select the subscription mode matching your connectionMode:
   • Long connection — for connectionMode: "websocket" (recommended, no public URL needed)
   • Request URL — for connectionMode: "webhook" (requires a publicly accessible URL)
2. Add event subscriptions:

3. Ensure the event permissions are approved

openclaw config set channels.feishu.appId "cli_xxxxx"
openclaw config set channels.feishu.appSecret "your_app_secret"
openclaw config set channels.feishu.enabled true

channels:
  feishu:
    enabled: true
    appId: "cli_xxxxx"
    appSecret: "secret"
    # Domain: "feishu" (China), "lark" (International), or custom URL
    domain: "feishu"  # or "https://open.xxx.cn" for private deployment
    # Connection mode: "websocket" (recommended) or "webhook"
    connectionMode: "websocket"
    # DM policy: "pairing" | "open" | "allowlist"
    dmPolicy: "pairing"
    # DM allowlist (open_id/user_id). Include "*" when dmPolicy="open"
    allowFrom: []
    # Group policy: "open" | "allowlist" | "disabled"
    groupPolicy: "allowlist"
    # Require @mention in groups
    requireMention: true
    # Safety default for mention-free mode (`requireMention: false`):
    # only allow non-@ messages in groups with <= 1 bot.
    # Set true to also allow mention-free messages in multi-bot groups.
    allowMentionlessInMultiBotGroup: false
    # Group command mention bypass: "never" | "single_bot" | "always"
    # Default "single_bot": allow authorized command-only messages without @
    # only when the group has a single bot.
    groupCommandMentionBypass: "single_bot"
    # Max media size in MB (default: 30)
    mediaMaxMb: 30
    # Render mode for bot replies: "auto" | "raw" | "card"
    renderMode: "auto"

dmPolicy controls who can interact with the bot in direct messages (DM).
In multi-account mode, this is resolved per account (channels.feishu.accounts.<accountId>).

Notes:

• allowFrom accepts Feishu user IDs (open_id recommended, user_id also supported).
• If dmPolicy: "open", use allowFrom: ["*"]. This is required by top-level schema validation and keeps access behavior explicit.
• pairing and allowlist can both pre-authorize users with allowFrom.

Pairing flow (owner approval):

1. User sends any DM to the bot.
2. Bot replies with a pairing code (for example H9ZEHY8R).
3. Bot owner approves:

openclaw pairing approve feishu H9ZEHY8R

4. The user is added to the allow store and can chat immediately.

Example: open to everyone

channels:
  feishu:
    dmPolicy: "open"
    allowFrom: ["*"]

Example: controlled rollout (pairing + pre-approved users)

channels:
  feishu:
    dmPolicy: "pairing"
    allowFrom:
      - "ou_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Example: strict allowlist

channels:
  feishu:
    dmPolicy: "allowlist"
    allowFrom:
      - "ou_alice"
      - "ou_bob"

Example: account-level isolation

channels:
  feishu:
    accounts:
      lobster-1:
        dmPolicy: "open"
        allowFrom: ["*"]
      lobster-5:
        dmPolicy: "pairing"

Top-level channels.feishu.dmPolicy / channels.feishu.allowFrom are fallback defaults for accounts that do not override them.

dmPolicy only controls who can trigger the bot.
To actually read/write docs or files, you still need: (1) correct Feishu app scopes, and (2) sharing the target resources (Drive/Wiki/Bitable) with the bot.

When requireMention: true, Feishu can still allow authorized control commands (such as /new) without @bot.

Notes:

• Bypass only applies to authorized control commands in group chats.
• If any user is explicitly @-mentioned in the same message, bypass is disabled.
• In DMs, this setting does not apply.

When requireMention: false, non-@ group messages are handled with a safety default:

Important:

• im:message.group_msg is required for receiving non-@ group messages and this is a sensitive permission in Feishu.
• If this scope is not approved, Feishu usually only delivers @bot group messages (im:message.group_at_msg:readonly).

Two connection modes are available for receiving events from Feishu:

WebSocket mode (default, no extra config needed):

channels:
  feishu:
    connectionMode: "websocket"  # or just omit this line

In Feishu console: Events & Callbacks → select Long connection.

Webhook mode:

channels:
  feishu:
    connectionMode: "webhook"
    webhookPort: 3000               # HTTP server port (default: 3000)
    webhookPath: "/feishu/events"   # Event callback path (default: "/feishu/events")
    encryptKey: "your_encrypt_key"           # From Feishu console → Events & Callbacks → Encrypt Key
    verificationToken: "your_verify_token"   # From Feishu console → Events & Callbacks → Verification Token

In Feishu console: Events & Callbacks → select Request URL → set the URL to:

https://your-domain.com/feishu/events

Note: The Request URL must be HTTPS and publicly accessible. For local development, you can use tools like ngrok to create a tunnel: ngrok http 3000, then use the generated URL.

When enabled, each DM user automatically gets their own isolated agent instance with a dedicated workspace. This provides complete isolation including separate conversation history, memory (MEMORY.md), and workspace files.

channels:
  feishu:
    dmPolicy: "open"
    allowFrom: ["*"]
    dynamicAgentCreation:
      enabled: true
      # Template for workspace directory ({userId} = OpenID, {agentId} = generated agent ID)
      workspaceTemplate: "~/workspaces/feishu-{agentId}"
      # Template for agent config directory
      agentDirTemplate: "~/.openclaw/agents/{agentId}/agent"
      # Optional: limit total number of dynamic agents
      maxAgents: 100

session:
  # Also set dmScope for session isolation (conversation history)
  dmScope: "per-peer"

How it works:

1. When a new user sends a DM, the system creates a new agent entry in openclaw.json
2. A binding is created to route that user's DM to their dedicated agent
3. Workspace and agent directories are created automatically
4. Subsequent messages from that user go to their isolated agent

Difference from dmScope: "per-peer":

• dmScope: "per-peer" only isolates conversation history
• dynamicAgentCreation provides full isolation (workspace, memory, identity, tools)

• WebSocket and Webhook connection modes
• Direct messages and group chats
• Message replies and quoted message context
• Inbound media support: AI can see images, read files (PDF, Excel, etc.), and process rich text with embedded images
• Image and file uploads (outbound)
• Typing indicator (via emoji reactions)
• Pairing flow for DM approval
• User and group directory lookup
• Card render mode: Optional markdown rendering with syntax highlighting
• Document tools: Read, create, and write Feishu documents with markdown, including atomic create_and_write / import_document flows for reliable create+content write
• Wiki tools: Navigate knowledge bases, list spaces, get node details, search, create/move/rename nodes
• Drive tools: List folders, get file info, create folders, move/delete files
• Bitable tools: Manage bitable (多维表格) fields and records (read/create/update/delete), supports both /base/ and /wiki/ URLs
• Task tools: Create, get details, update, and delete tasks via Feishu Task v2 API
• @mention forwarding: When you @mention someone in your message, the bot's reply will automatically @mention them too
• Permission error notification: When the bot encounters a Feishu API permission error, it automatically notifies the user with the permission grant URL
• Dynamic agent creation: Each DM user can have their own isolated agent instance with dedicated workspace (optional)

When you want the bot to @mention someone in its reply, simply @mention them in your message:

• In DM: @张三 say hello → Bot replies with @张三 Hello!
• In Group: @bot @张三 say hello → Bot replies with @张三 Hello!

The bot automatically detects @mentions in your message and includes them in its reply. No extra permissions required beyond the standard messaging permissions.

Check the following:

1. Have you configured event subscriptions? (See Event Subscriptions section)
2. Does the event subscription mode match your connectionMode?
   • websocket → Long connection in Feishu console
   • webhook → Request URL in Feishu console (URL must be reachable)
3. Did you add the im.message.receive_v1 event?
4. Are the permissions approved?
5. For webhook mode: is your server running and the URL publicly accessible?

Check the following:

1. Is im:message.group_msg approved? (sensitive permission, required for non-@ group messages)
2. If the group has multiple bots, do you explicitly set allowMentionlessInMultiBotGroup: true?
3. Is requireMention: false configured on the effective account/group?

Ensure im:message:send_as_bot permission is approved.

Send /new command in the chat.

Feishu API has rate limits. Streaming updates can easily trigger throttling. We use complete-then-send approach for stability.

1. Ensure the app is published (at least to test version)
2. Search for the bot name in Feishu search box
3. Check if your account is in the app's availability scope

openclaw plugins install @m1heng-clawd/feishu

# 方案 A（推荐）：下载最新插件 tarball
npm pack @m1heng-clawd/feishu
openclaw plugins install ./m1heng-clawd-feishu-<version>.tgz

# 方案 B（保留 curl 路径）：先解析最新 tarball 地址，再下载安装
TARBALL_URL="$(npm view @m1heng-clawd/feishu dist.tarball)"
curl -L -o feishu-latest.tgz "$TARBALL_URL"
openclaw plugins install ./feishu-latest.tgz

# Windows PowerShell（方案 B）
$tarball = npm view @m1heng-clawd/feishu dist.tarball
curl.exe -L $tarball -o feishu-latest.tgz
openclaw plugins install .\feishu-latest.tgz

# 方案 C（无 npm 命令）：先在 npm Versions 页查到最新版本号，再套用 URL 模板
# https://www.npmjs.com/package/@m1heng-clawd/feishu?activeTab=versions
curl -L -o feishu-latest.tgz https://registry.npmjs.org/@m1heng-clawd/feishu/-/feishu-<version>.tgz
openclaw plugins install ./feishu-latest.tgz

openclaw plugins update feishu

查看已安装版本：

openclaw plugins list | rg -i feishu

1. 在 飞书开放平台 创建自建应用
2. 在凭证页面获取 App ID 和 App Secret
3. 开启所需权限（见下方）
4. 配置事件订阅（见下方）⚠️ 重要
5. 配置插件：

只读权限（最低要求）：

读写权限（可选，用于创建/编辑/删除操作）：

飞书控制台中任务权限的显示名称可能略有差异，必要时可按关键字 task / tasklist / comment / attachment 搜索并授予对应读写权限。

任务评论需要单独授权：

1. 读取评论：授予 task:comment:read。
2. 创建/更新/删除评论：授予 task:comment:write。

缺少上述权限时，评论相关接口会返回权限不足错误。

任务附件支持上传/获取/列表/删除。上传来源：

1. OpenClaw/Node 所在机器的本地文件路径（file_path）
2. 可直接下载的远程链接（file_url，公开/预签名 URL）

file_url 上传路径会使用 OpenClaw 运行时的媒体下载安全校验与大小限制（mediaMaxMb），随后经临时本地文件上传到任务附件。

重要： 创建/修改任务清单时，请保持清单所有者为机器人本身，只把用户作为协作人添加。

任务清单权限基于“所有者 + 协作成员角色”授予。如果把清单所有者改成用户、且机器人不在协作成员中，机器人可能会失去对该清单的读取/编辑/管理权限，导致后续对清单的操作失败。

重要： 只有当任务责任人包含用户时，用户才能查看到该任务。

限制： 机器人目前只能给自己创建出来的任务创建子任务。

为避免“任务创建了但用户看不到”的问题：

1. 创建任务时，请把发起用户设为任务负责人（assignee）。
2. 如需更灵活的子任务创建/组织/可见性管理，建议使用任务清单（tasklists）。

重要： 机器人没有自己的"我的空间"（根目录）。机器人只能访问被分享给它的文件/文件夹。

要让机器人管理文件：

1. 在你的飞书云空间创建一个文件夹
2. 右键文件夹 → 分享 → 搜索机器人名称
3. 授予相应权限（查看/编辑）

如果不做这一步，feishu_drive 的 create_folder 等操作会失败，因为机器人没有根目录可以创建文件夹。

重要： 仅有 API 权限不够，还需要将机器人添加到知识库空间。

1. 打开需要机器人访问的知识库空间
2. 点击 设置（齿轮图标）→ 成员管理
3. 点击 添加成员 → 搜索机器人名称
4. 选择权限级别（查看/编辑）

如果不做这一步，即使 API 权限正确，feishu_wiki 也会返回空结果。

参考文档：知识库常见问题 - 如何将应用添加为知识库成员

重要： 与其他资源一样，机器人只能访问被分享给它的多维表格。

要让机器人访问多维表格：

1. 打开需要机器人访问的多维表格
2. 点击 分享 按钮 → 搜索机器人名称
3. 授予相应权限（查看/编辑）

feishu_bitable 工具支持两种 URL 格式：

• /base/XXX?table=YYY - 标准多维表格链接
• /wiki/XXX?table=YYY - 嵌入在知识库中的多维表格（自动转换为 app_token）

这是最容易遗漏的配置！ 如果机器人能发消息但收不到消息，请检查此项。

在飞书开放平台的应用后台，进入 事件与回调 页面：

1. 事件配置方式：根据你的 connectionMode 选择对应的订阅方式：
   • 使用长连接接收事件 — 对应 connectionMode: "websocket"（推荐，无需公网地址）
   • 使用请求地址接收事件 — 对应 connectionMode: "webhook"（需要公网可访问的 URL）
2. 添加事件订阅，勾选以下事件：

3. 确保事件订阅的权限已申请并通过审核

openclaw config set channels.feishu.appId "cli_xxxxx"
openclaw config set channels.feishu.appSecret "your_app_secret"
openclaw config set channels.feishu.enabled true

channels:
  feishu:
    enabled: true
    appId: "cli_xxxxx"
    appSecret: "secret"
    # 域名: "feishu" (国内)、"lark" (国际) 或自定义 URL
    domain: "feishu"  # 私有化部署可用 "https://open.xxx.cn"
    # 连接模式: "websocket" (推荐) 或 "webhook"
    connectionMode: "websocket"
    # 私聊策略: "pairing" | "open" | "allowlist"
    dmPolicy: "pairing"
    # 私聊白名单（open_id/user_id）；当 dmPolicy="open" 时请包含 "*"
    allowFrom: []
    # 群聊策略: "open" | "allowlist" | "disabled"
    groupPolicy: "allowlist"
    # 群聊是否需要 @机器人
    requireMention: true
    # 免 @ 安全默认策略（requireMention=false 时）：
    # 仅在群内机器人数量 <= 1 时处理未 @ 的群消息。
    # 设为 true 可在多 bot 群也放开免 @（需自行承担重复触发风险）。
    allowMentionlessInMultiBotGroup: false
    # 群聊命令绕过 @ 策略: "never" | "single_bot" | "always"
    # 默认 "single_bot"：仅当群内机器人数量 <= 1 时，允许已授权命令免 @
    groupCommandMentionBypass: "single_bot"
    # 媒体文件最大大小 (MB, 默认 30)
    mediaMaxMb: 30
    # 回复渲染模式: "auto" | "raw" | "card"
    renderMode: "auto"

dmPolicy 控制的是“谁可以在私聊里触发机器人”。
在多账号模式下，它按账号生效（channels.feishu.accounts.<accountId>）。

说明：

• allowFrom 支持飞书用户 ID（推荐 open_id，也支持 user_id）。
• 当 dmPolicy: "open" 时，建议固定写 allowFrom: ["*"]，语义最清晰，也满足顶层配置校验要求。
• pairing 和 allowlist 都可以先通过 allowFrom 预授权部分用户。

配对审批流程（pairing）：

1. 用户先给机器人发一条私聊消息。
2. 机器人返回配对码（例如 H9ZEHY8R）。
3. 管理员执行审批命令：

openclaw pairing approve feishu H9ZEHY8R

4. 审批后该用户立即可用。

示例：全部放开

channels:
  feishu:
    dmPolicy: "open"
    allowFrom: ["*"]

示例：灰度放开（pairing + 预授权）

channels:
  feishu:
    dmPolicy: "pairing"
    allowFrom:
      - "ou_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

示例：严格白名单

channels:
  feishu:
    dmPolicy: "allowlist"
    allowFrom:
      - "ou_alice"
      - "ou_bob"

示例：按账号隔离配置

channels:
  feishu:
    accounts:
      lobster-1:
        dmPolicy: "open"
        allowFrom: ["*"]
      lobster-5:
        dmPolicy: "pairing"

channels.feishu.dmPolicy / channels.feishu.allowFrom 是“默认值”；账号下未覆盖时才会继承。

dmPolicy 只控制“是否允许触发机器人”。
真正执行文档/云盘/知识库/多维表格操作，还需要两层权限：1）应用 API 权限（scopes）；2）把目标资源分享给机器人。

当 requireMention: true 时，Feishu 仍可让“已授权控制命令（如 /new）”在不 @bot 的情况下通过。

说明：

• 仅对群聊中的“已授权控制命令”生效。
• 同一条消息里如果显式 @ 了任意用户，则不会触发命令免 @。
• 私聊场景不受该配置影响。

当 requireMention: false 时，插件对“未 @ 的群消息”采用安全默认策略：

重要说明：

• 要接收未 @ 的群消息，必须申请并通过 im:message.group_msg，且该权限是飞书敏感权限。
• 若未通过该权限，飞书通常只会推送 @bot 群消息（im:message.group_at_msg:readonly）。

支持两种从飞书接收事件的连接模式：

WebSocket 模式（默认，无需额外配置）：

channels:
  feishu:
    connectionMode: "websocket"  # 或直接省略此行

飞书控制台：事件与回调 → 选择 使用长连接接收事件。

Webhook 模式：

channels:
  feishu:
    connectionMode: "webhook"
    webhookPort: 3000               # HTTP 服务端口（默认: 3000）
    webhookPath: "/feishu/events"   # 事件回调路径（默认: "/feishu/events"）
    encryptKey: "your_encrypt_key"           # 飞书控制台 → 事件与回调 → Encrypt Key
    verificationToken: "your_verify_token"   # 飞书控制台 → 事件与回调 → Verification Token

飞书控制台：事件与回调 → 选择 使用请求地址接收事件 → 填入请求地址：

https://your-domain.com/feishu/events

提示： 请求地址必须是 HTTPS 且公网可访问。本地开发时，可使用 ngrok 等工具创建隧道：ngrok http 3000，然后使用生成的地址。

启用后，每个私聊用户会自动获得独立的 agent 实例和专属 workspace。这提供完整的隔离，包括独立的对话历史、记忆（MEMORY.md）和工作区文件。

channels:
  feishu:
    dmPolicy: "open"
    allowFrom: ["*"]
    dynamicAgentCreation:
      enabled: true
      # workspace 目录模板 ({userId} = OpenID, {agentId} = 生成的 agent ID)
      workspaceTemplate: "~/workspaces/feishu-{agentId}"
      # agent 配置目录模板
      agentDirTemplate: "~/.openclaw/agents/{agentId}/agent"
      # 可选：限制动态 agent 总数
      maxAgents: 100

session:
  # 同时设置 dmScope 以隔离对话历史
  dmScope: "per-peer"

工作原理：

1. 当新用户发送私聊时，系统在 openclaw.json 中创建新的 agent 条目
2. 创建 binding 将该用户的私聊路由到专属 agent
3. 自动创建 workspace 和 agent 目录
4. 该用户后续的消息都会路由到其隔离的 agent

与 dmScope: "per-peer" 的区别：

• dmScope: "per-peer" 仅隔离对话历史
• dynamicAgentCreation 提供完整隔离（workspace、记忆、身份、工具）

• WebSocket 和 Webhook 连接模式
• 私聊和群聊
• 消息回复和引用上下文
• 入站媒体支持：AI 可以看到图片、读取文件（PDF、Excel 等）、处理富文本中的嵌入图片
• 图片和文件上传（出站）
• 输入指示器（通过表情回复实现）
• 私聊配对审批流程
• 用户和群组目录查询
• 卡片渲染模式：支持语法高亮的 Markdown 渲染
• 文档工具：读取、创建、用 Markdown 写入飞书文档（表格因 API 限制不支持）
• 知识库工具：浏览知识库、列出空间、获取节点详情、搜索、创建/移动/重命名节点
• 云空间工具：列出文件夹、获取文件信息、创建文件夹、移动/删除文件
• 多维表格工具：支持多维表格字段与记录的读取/创建/更新/删除，支持 /base/ 和 /wiki/ 两种链接格式
• 任务工具：基于 Task v2 API 支持任务创建、获取详情、更新和删除
• @ 转发功能：在消息中 @ 某人，机器人的回复会自动 @ 该用户
• 权限错误提示：当机器人遇到飞书 API 权限错误时，会自动通知用户并提供权限授权链接
• 动态 Agent 创建：每个私聊用户可拥有独立的 agent 实例和专属 workspace（可选）

如果你希望机器人的回复中 @ 某人，只需在你的消息中 @ 他们：

• 私聊：@张三 跟他问好 → 机器人回复 @张三 你好！
• 群聊：@机器人 @张三 跟他问好 → 机器人回复 @张三 你好！

机器人会自动检测消息中的 @ 并在回复时带上。无需额外权限。

检查以下配置：

1. 是否配置了 事件订阅？（见上方事件订阅章节）
2. 事件订阅方式是否与 connectionMode 匹配？
   • websocket → 飞书控制台选择 使用长连接接收事件
   • webhook → 飞书控制台选择 使用请求地址接收事件（URL 必须可访问）
3. 是否添加了 im.message.receive_v1 事件？
4. 相关权限是否已申请并审核通过？
5. 如果使用 webhook 模式：服务是否正在运行？URL 是否公网可访问？

请重点检查：

1. 是否已申请并审核通过 im:message.group_msg（敏感权限，接收未 @ 群消息必需）
2. 群里若有多个 bot，是否显式设置了 allowMentionlessInMultiBotGroup: true
3. requireMention: false 是否配置在当前生效的账号/群配置上

确保已申请 im:message:send_as_bot 权限，并且权限已审核通过。

在聊天中发送 /new 命令即可开启新对话。

飞书 API 有请求频率限制，流式更新消息很容易触发限流。当前采用完整回复后一次性发送的方式，以保证稳定性。

1. 确保应用已发布（至少发布到测试版本）
2. 在飞书搜索框中搜索机器人名称
3. 检查应用可用范围是否包含你的账号

MIT