lark-vc-agent

Run lark-cli vc +meeting-join --as bot --meeting-number followed by the 9-digit meeting number, adding --password if the meeting requires one. Record the returned meeting.id immediately, since event reads and leaving the meeting both need that long numeric ID.

Use lark-cli vc +meeting-events with the long numeric meeting_id, keeping the same identity (user or bot) that discovered the meeting. Pass --page-all to pull the full visible event stream and save the returned page_token for incremental polling.

lark-vc-agent handles in-meeting actions: bot join/leave, live event streams, and in-meeting messages. lark-vc handles post-meeting queries such as searching ended meetings, participant snapshots, minutes, transcripts, and recordings.

Error 10005 means the app bot never actually joined that meeting, or the meeting ended beyond the 5-minute grace window. Either re-read with the user identity that discovered the meeting_id, or have the bot join first with +meeting-join.

Yes, use lark-cli vc +meeting-message-send with --text for chat messages or --emoji-type for reactions, including VC feedback keys like VC_NoSound and VC_LooksGood. The sender identity must match how the meeting_id was discovered, and the sender must be in the meeting.

Do not use +meeting-events for ended meetings, participant snapshots, or historical search. For ended meetings use vc +detail and the lark-vc skill for minutes and transcripts, and use vc meeting get --with-participants for participant snapshots.