feishu-workspace-bridge

One private Feishu group per DSH workspace, with real-time two-way message synchronization.

中文 · npm · Releases

Continue a DSH workspace task from Feishu after leaving your computer. The plugin uses Feishu's long connection mode, so it needs no public webhook and never polls or replays message history.

What it does

• Binds one Feishu custom app bot to DSH.
• Lazily creates one private Feishu group when a workspace first has a message to synchronize, then invites you automatically.
• Synchronizes the current DSH conversation and its Feishu group in both directions.

Workspace renames update the group name. Deleting a workspace dissolves its group. Messages sent while DSH is busy join the conversation queue in order, and the bot adds an OK reaction after accepting an inbound message.

Markdown is delivered as Feishu lark_md. Long messages are split safely. A durable delivery queue, exponential retry, stable idempotency IDs, and restart recovery protect both directions without importing historical messages.

Requirements

• Node.js 20 or newer
• DeepSeek Harness (DSH)
• A Feishu custom app with bot capability enabled

Install

dsh plugin --profile web add dsh-plugin-feishu-workspace
dsh web --no-open

Open Settings → Feishu Bot in DSH and enter:

• App ID
• App Secret
• Your Feishu Open ID (ou_...)

Choose Save and verify. The plugin verifies the bot, event subscription, and every required permission before replacing the current configuration.

Configure Feishu

1. Add the bot capability to your Feishu custom app.
2. In Events & Callbacks, select long connection mode and subscribe to im.message.receive_v1.
3. Grant the following application identity scopes and publish a new app version.

The plugin does not use custom group labels and does not require label review permissions.

Compatibility

DSH is currently a developer preview and upstream compatibility may change. If something breaks, open an issue with your DSH version and the error shown by the diagnostics page.

Security and diagnostics

• On macOS, App Secret is stored in Keychain rather than SQLite.
• Other systems use ~/.dsh/feishu-workspace-bridge.secrets.json with 0600 permissions.
• The settings page shows the long connection, bound groups, delivery status, retries, permission checks, and recent event times.
• Diagnostics never include App Secret, access tokens, or message bodies.
• The plugin consumes real-time events only and does not read historical chat messages.

Run the full checks locally with:

npm install
npm run check

See CONTRIBUTING.md before sending a pull request. Report security issues privately as described in SECURITY.md.

License

MIT © bandianliancha