codewhale/integrations/feishu-bridge/README.md

Feishu / Lark Bridge

This bridge lets a Feishu or Lark chat control a local codewhale serve --http runtime from a phone. It uses the official Lark/Feishu Node SDK long-connection mode, so the first version does not need a public webhook URL.

Security model:

• codewhale serve --http stays bound to 127.0.0.1.
• /v1/* runtime calls use DEEPSEEK_RUNTIME_TOKEN.
• Feishu/Lark chats must be allowlisted unless DEEPSEEK_ALLOW_UNLISTED=true is set for first pairing.
• Direct messages are the intended MVP control surface. Group chat control is disabled unless FEISHU_ALLOW_GROUPS=true.
• Tool approvals are text commands: /allow <approval_id> or /deny <approval_id>.

Setup

cd /opt/codewhale/bridge
npm install --omit=dev
cp .env.example /etc/deepseek/feishu-bridge.env
sudoedit /etc/deepseek/feishu-bridge.env
node src/index.mjs

Validate the env files before starting the service:

npm run validate:config -- \
  --env /etc/deepseek/feishu-bridge.env \
  --runtime-env /etc/deepseek/runtime.env \
  --workspace-root /opt/whalebro \
  --check-filesystem

For a Tencent Lighthouse deployment, use:

sudo systemctl enable --now codewhale-runtime codewhale-feishu-bridge
sudo journalctl -u codewhale-feishu-bridge -f

Commands

• /status
• /threads
• /new
• /resume <thread_id>
• /interrupt
• /compact
• /allow <approval_id> [remember]
• /deny <approval_id>

Anything else is sent as a prompt. If group control is explicitly enabled, messages must start with /ds by default, for example:

/ds check git status and tell me what is dirty