General 28,867 installs

Lark Events

by larksuite/cli

Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM…

Skill content

Stream Lark/Feishu events as NDJSON with bounded runs and subprocess-safe exit contracts.

- Consume real-time events (IM messages, reactions, chat changes, VC meetings, Minutes) via lark-cli event consume <EventKey>, with optional jq filtering and --max-events / --timeout bounds

- Emits a stderr ready marker before stdout, supports stdin EOF for graceful shutdown, and reports exit reason (limit/timeout/signal/error) for reliable orchestration

- One EventKey per process; use lark-cli event list and lark-cli event schema to discover keys and inspect output schemas before consuming

- Requires lark-cli binary and Lark authentication configured via lark-shared skill; avoid kill -9 on processes with PreConsume hooks to prevent server-side subscription leaks

Lark Events

Prerequisite: Read ../lark-shared/SKILL.md first for authentication, --as user/bot switching, Permission denied handling, and safety rules.

Core commands

Command
Purpose

lark-cli event list [--json]
List all subscribable EventKeys

lark-cli event schema <EventKey> [--json]
Show an EventKey's params and output schema

lark-cli event consume <EventKey> [flags]
Blocking consume; events → stdout NDJSON

lark-cli event status [--json] [--fail-on-orphan]
Inspect the local bus daemon status

lark-cli event stop [--all] [--force]
Stop the bus daemon

Common flags