Repository navigation
feat: add Feishu (Lark) WASM channel plugin - #1104
Closed
lowmiaq-gmail wants to merge 1 commit into
Closed
lowmiaq-gmail wants to merge 1 commit into
lowmiaq-gmail wants to merge 1 commit into
Conversation
Adds a new channel plugin for Feishu/Lark messaging platform, following the same WASM component model pattern as existing Telegram/Slack/Discord channels. Features: - Webhook-based event subscription (im.message.receive_v1) - URL verification challenge handling - P2P (DM) and group chat support with @mention triggering - Reply threading via root_id - Text, image, and file message type support - Attachment upload (images via /im/v1/images, files via /im/v1/files) - DM pairing flow (pairing/allowlist/open policies) - Owner restriction via owner_open_id - Event deduplication - Status notifications as text messages - Proactive messaging (broadcast) Auth: Uses OAuth2-style tenant_access_token with auto-refresh managed by the host runtime (app_id + app_secret → token exchange). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
github-actions
Bot
added
size: XL
zmanian
requested changes
Mar 13, 2026
zmanian
left a comment
zmanian
left a comment
Collaborator
There was a problem hiding this comment.
This is a competing implementation of #1110 (reidliu41's Feishu/Lark channel). Key differences:
- This PR is larger (+2090 vs +1084) with more features (attachments, deduplication) but is missing critical host-side integration: no registry manifest, no bundled channel entry, no setup.rs credential injection.
- Includes Cargo.lock (shouldn't be committed for WASM library crates).
- No real CI has run (fork PR -- classify/scope only).
- Commit author metadata looks unusual.
Recommend closing in favor of #1110, which has full host-side integration. Specific features from this PR (attachment handling, event deduplication) could be cherry-picked into #1110 as follow-ups.
Member
|
We merged #1110. Can you please do attachment handling, event deduplication as follow up separate PR? Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tenant_access_tokenwith host-managed auto-refresh viaapp_id+app_secretDetails
im.message.receive_v1eventsFiles
channels-src/feishu/Cargo.toml— crate configchannels-src/feishu/build.sh— WASM build scriptchannels-src/feishu/feishu.capabilities.json— capability declarationchannels-src/feishu/src/lib.rs— full channel implementation (~1500 lines)Test plan
cargo build --release --target wasm32-wasip2(0 warnings)🤖 Generated with Claude Code