程序员阿江(Relakkes)
814c02a786
Connecting Feishu meant creating a bot by hand on the open platform and pasting an App ID and App Secret back. Feishu also exposes an RFC 8628 device-authorization flow, so the desktop can now render a QR code, and confirming it in the app creates the bot and stores its credentials directly. `adapters/feishu/registration.ts` implements that protocol rather than importing `registerApp` from `@larksuiteoapi/node-sdk@1.73`: the repository pins 1.60 for the chat client, and the SDK runs the whole poll inside one un-cancellable promise where the desktop needs the stateless begin/poll pair the DingTalk registration already uses. The scan is create-only, so it can never rewrite the configuration of a bot the user already runs, and it pre-fills exactly the scopes, events and callbacks this adapter calls. International tenants finish on Lark's domain, which is now persisted and honoured by the client. WeCom, QQ and Slack join the same session model. WeCom and QQ bind by scanning; Slack has no scan flow, so it uses an app manifest that pre-fills the scopes and Socket Mode. All three run over long connections, so no public callback URL is needed, and all three accept private chats only — pairing authorizes one person, and answering in a group would extend that authorization to everyone else in the room. They are built on a new `adapters/common/chat-runtime.ts` instead of a fourth copy of the loop the five existing adapters each carry. A platform supplies a `ChatPort` — how to say something, how to open a streaming reply, optionally how to send an image — and the runtime owns pairing, command routing, session restore, permission bookkeeping and the translation of the server's stream. The existing five are deliberately left on their own copies; migrating them is a separate change with its own regression surface. Attachments are downloaded through a deferred loader that runs after the pairing gate and inside the per-chat queue. Resolving them eagerly would let an unpaired stranger make the adapter fetch bytes and write them under ~/.claude/im-downloads — on Slack with the bot token attached — and would let a slow attachment overtake a text message sent after it. The sidecar launcher's per-adapter branches become one table. It is declared above the mode dispatch on purpose: `runAdapters` is hoisted and runs at module top level, so a table declared below it is still in its temporal dead zone when the adapters mode reads it — which type checks, lints and unit tests all miss, and only the compiled binary reveals. Verified with the checks `check:impact` selects: adapters, server, desktop, electron, policy, chat-contract, agent-flow, docs, native (sidecar compile, packaging and an adapters-mode smoke against the real binary) and coverage. The scan flows themselves are not verified against live platforms — that needs real WeCom, QQ and Slack accounts and would create real bots. Claude-Session: https://claude.ai/code/session_01CCGoP316AK7wdQG3Ms6Uwq
5.5 KiB
title, nav_title, description, order
| title | nav_title | description | order |
|---|---|---|---|
| Feishu Integration | Feishu | Scan a QR code in Settings to create a Feishu bot, then drive Desktop sessions from a private chat with card-based approval. | 1 |
Feishu Integration
Best for teams already on Feishu: select Scan to Create in Settings, scan with Feishu, and the bot is created with its App ID and App Secret stored locally. Permission requests arrive as interactive cards you can tap, and common commands can be exposed as a bot menu. It handles private (p2p) chats only, and changing the bot menu means publishing a new version in the developer console.
Create the bot by scanning
- Open Settings → IM Adapters and select the Feishu tab.
- Select Scan to Create. A QR code appears.
- Scan it with Feishu. The confirmation page arrives pre-filled with the bot's name, description, and exactly the scopes, event subscriptions, and card callback this adapter calls — nothing extra is requested.
- On confirmation the App ID and App Secret are written to
~/.claude/adapters.jsonand the adapter restarts.
The code is valid for 10 minutes; generate a new one if it lapses. Once bound, the button becomes Scan Again and an Unbind Feishu bot button appears next to it.
Scanning only ever creates a new bot; it never binds an existing one, which would let this flow quietly rewrite the callback configuration of a bot you already run.
Leave Encrypt Key and Verification Token empty: messages travel over the WebSocket connection, which does not use them.
::: tip Creating one by hand also works If you would rather not scan, or want to reuse an existing bot, create one from the official OpenClaw template and paste its App ID and App Secret into the fields below the QR panel. Desktop also shows that entry point while no credentials are stored. :::
Configure the bot menu
This step is optional. With a menu, you can switch projects and start sessions by tapping instead of typing.
In the Feishu developer console, open your bot and go to its bot menu configuration. Add three entries, each with a label of your choice and one of these commands:
/projects— list recent projects and switch/new— start a new session/clear— clear the current context
Save the menu, then publish a new application version. Menu changes take effect only after publishing.
Entering credentials by hand
A bot created by scanning needs none of this — its credentials are already stored. This is only for the template flow or for reusing an existing bot:
- Open Settings → IM Adapters and select the Feishu tab.
- Paste the values into App ID and App Secret.
- Leave Encrypt Key and Verification Token empty; the long-connection mode does not need them.
- Enable Streaming Card Mode if you want long replies to update one card in place.
- Select Save.
Allowed Users can stay empty. When it is, only paired accounts are accepted, which is usually what you want.
Pair your account
At the top of the page, under Pairing, select Generate Code. The six-character code is written to local configuration immediately — no separate save.
Send any message to your new bot in Feishu, then send the code when prompted. Once pairing is confirmed you can talk to Claude Code directly.
Codes are valid for 60 minutes, work once, and are invalidated when a new one is generated.
Commands
Alongside the menu buttons, these work in the chat box at any time:
/helpor帮助/statusor状态/projectsor项目列表/newor新会话/clearor清空/stopor停止
Approval and reply behavior
Permission requests arrive as interactive cards. Selecting allow or deny returns the result to the pending Desktop session.
Normal replies use Feishu post messages. Streaming output prefers patching the same message, and long completed text is split to respect platform limits.
Development
Packaged Desktop starts the sidecar automatically. Run it by hand only when working from source:
cd adapters
bun install
bun run feishu
Optional overrides:
export FEISHU_APP_ID="cli_xxx"
export FEISHU_APP_SECRET="xxx"
export ADAPTER_SERVER_URL="ws://127.0.0.1:3456"
Troubleshooting
Scanning does nothing. The flow runs on accounts.feishu.cn; confirm your machine can reach it. International (Lark) tenants switch to accounts.larksuite.com automatically after confirmation — there is nothing to change by hand.
The code reports as expired. It is valid for 10 minutes; select Scan Again for a new one.
No messages arrive. Confirm the app is published — menu edits require a new version — and that the conversation is a private chat rather than a group.
Card buttons do nothing. The card action capability usually did not ship with the published version. Publish again from the developer console.
Still unauthorized. Check that the code is within its 60-minute window, that it is the current one, and that the account now appears under Paired Users in Desktop.
Session not restored after a restart. Verify that ~/.claude/adapter-sessions.json is writable and that the session still exists in Desktop.
Source
adapters/feishu/index.ts (runtime) and adapters/feishu/registration.ts (scan to create), plus pairing.ts, session-store.ts, ws-bridge.ts, and http-client.ts under adapters/common/.