lark-channel

Lark/Feishu Channel SDK for Rust.

This repository is an early community scaffold for a Rust SDK that mirrors the role of the official Channel SDK family:

channel-sdk-go
channel-sdk-java
channel-sdk-python
channel-sdk-node

The first target is to support agent/bot bridges such as lark-coding-agent-bridge-rs: inbound events, normalized messages, streaming replies, media downloads, and interactive card callbacks.

Status

Experimental. The crate currently contains the public module skeleton, shared data types, and an early OpenAPI foundation for app and tenant access-token management.

Planned Modules

config: app id/secret, Feishu/Lark domain selection, SDK source metadata
event: normalized inbound events
message: normalized messages and outbound content
card: interactive card primitives
media: resource descriptors and download/upload helpers
client: async client trait for transport implementations
openapi: access-token cache, low-level OpenAPI response handling, and default reqwest transport

Crate Name

The repository is named channel-sdk-rust to match LarkSuite's official SDK naming style. The published Rust crate is lark-channel, and the Rust library target is lark_channel, so users can import it as:

lark-channel = "0.1"

use lark_channel::{ChannelConfig, Domain};

Examples

Examples live in examples.

The token example verifies the current OpenAPI foundation by requesting app and tenant access tokens:

export LARK_APP_ID=cli_xxx
export LARK_APP_SECRET=xxx
cargo run --example tokens

The example reads credentials from environment variables. Applications using this SDK may load those values from their own configuration system, secret manager, or local .env workflow before constructing ChannelConfig.

Roadmap

See docs/roadmap.md for the development plan.

The next milestones are: